聊搜 - 文章聚合搜索

Thursday, September 19, 2024 Sarah Huckabee Sanders forced us to think of her as a mom. I don't think that works out very well in her favor, probably best not to go there. # Driving on a mountain road # I was driving on a mountain road yesterday to pick up a pizza in a nearby town. I drive it fairly regularly, and I have a car that handles well so I drive at the speed limit or a little above. # Still, what often happens on this road is some asshole tailgates, getting so close that if I hit the brakes suddenly they would have no time to react, and would slam into the rear of my car. And you do sometimes have to hit the brakes because animals appear on the road, deer, turkeys are common. Sometimes even bears. # I've never hit an animal, but I have come close. # There's no way to pass on this road. # I've been in the other driver's place when a tourist is driving 30 in a 45 mph zone, and what do you do? Keep your distance

APEX Background Page Processing - The Definitive Gude Sep 19, 2024 · 12 min read Introduction Most enterprise applications have workloads that need to be run in the background. This is often a more efficient use of system resources and also allows users to continue working with your App while the processing takes place. APEX provides two options for background processing: APEX Automations and Background Page Processes . This post focuses on Background Page Processes introduced in APEX 23.1 and aims to give you everything you need to know to get started with this important feature. Advantages Performing long-running processes in the background has the following advantages: More efficient use of the ORDS connection pool . More efficient use of database resources. Move long-running code to run in a different resource consumer group to limit the amount of CPU it can use. Avoid gateway timeout errors when the page process runs for too long. Provide a better user experien

Hey! ​ If you've ever been writing tests and thought, "is this really the best approach?", had lots of back and forth with co-workers over testing strategy (should it be a "pyramid" or a "trophy", or...), or spent more time writing tests than the actual feature — I've got good news: I'm doing an in-depth workshop series where you'll learn best practices in frontend testing: The factors that determine the testing shape and strategy you should be using Why lots of mocks might be a sign that your code should be refactored How to use MSW to fake the network instead of writing mocks Why writing your component tests like unit tests is costing you time, and making your tests hard to maintain Maximizing ROI by prioritizing the right test cases — and avoiding redundant tests Banish brittleness, and write tests that don't constantly break Plus many other topics! It's fully remote and completely exercised-based, so