The Hidden Infrastructure Of Production

Remember when you just wanted to play games? Now you're basically a sysadmin for your own gaming rig. You used to mock those PC nerds obsessing over thermal paste and case fans while you were casually enjoying GTA San Andreas on your PS2. Fast forward to your 30s and you've got MSI Afterburner running 24/7, three monitoring apps tracking your temps, and you're genuinely excited about optimizing your RAM timings. You spend more time tweaking settings than actually playing. Your Steam library has 300 games but you're too busy stress-testing your CPU overclock to launch any of them. The programming angle? We do the same thing with our dev environments. "I'll just quickly set up my IDE" turns into a 4-hour rabbit hole of configuring linters, optimizing build times, and monitoring memory usage. The setup becomes the hobby.

First dev: "I'll just hardcode every single number from 1 to infinity with its even/odd status. Efficiency!" Second dev: "Why use simple modulo math when you can just outsource your basic arithmetic to a GPT model? That's 500KB of code and a $10 API bill to determine if a number is divisible by 2." The evolution of problem-solving in 2023: from hilariously inefficient to absurdly overcomplicated. Because nothing says "modern software engineering" like turning a one-line function into an enterprise-grade AI solution with cloud dependencies. Next week: "IsPositive() function now requires stable internet connection and cryptocurrency wallet."

The eternal battle between PMs and developers, captured in its natural habitat. When a PM says "make it more intuitive," they actually mean "add more validation steps." Meanwhile, the developer looking at their masterpiece of UI design where the "confirm email" field literally asks "Yes that is my Email" instead of having users type their email twice. Somewhere, a UX designer just felt a disturbance in the force and doesn't know why.

The programming paradigm hierarchy in its natural habitat! Data-oriented folks stand tall and proud at the top of the food chain. Object-oriented programmers cling desperately to the middle ground, while those return-oriented programmers... well, they're basically just lurking in the shadows waiting to exploit buffer overflows and hijack execution flow. The secret fourth paradigm not pictured: functional programmers who are too busy explaining monads to fit in the frame.

Content How I Feel Complete the sentences to show how you feel about bugs. Bugs make me feel ) When I see o bug. I say nothing Complete the picture to show an expression you might make when you see a bug.

Content 10:22 81 Products Q Log in Sign up 18 Are you sure the view gets populated by the container? I would suggest you to provide a callback for the RequestNavigate method, so you'll be able to track what happens with your view thru the NavigationResult regionManager.RequestNavigate "Window?" new Uri("View2", UriKind.Relative), (NavigationResult nr) var error nr.Error; var result nr. Result; put a breakpoint here and ch ) . Share Improve this answer Follow edited May 11, 2011 at 13:26 answered Mav 11. 2011 at 13:18 Shimmy Weitzhandler 103k 122 425 633 7 After 7 vears, and I'm thinking let's upvote this answer. Was simble and helped me tackle the issue easily, then I figure I'm the one who answered it... - Shimmy Weitzhandler Mar 4, 2018 at 11:08 Add a comment I have seen that if I imblement ConfirmNavigateRequest and do not call stackoverflow.com