I feel like this is just a lower-stakes version of “RedBull & vodka.” If that’s true, @[email protected], then this is a recipe for a bad hangover.
Good point.
Calling in sick:
Calling in, sick:
It’s also worth noting that the launch PS3 also had a whole PS2 inside of it, which partially explains the inflated price point. I say partially since I’m prrety sure that a PS2 slim cost a lot less than $330 in 2006 dollars; they could have just bundled both consoles or offered a rebate on a PS2 purchase and called it a day.
I just want to echo your sentiment with something I’ve been saying here for a while now:
Do not confuse information technology use for computer literacy.
Looking for bread tumors?
Honestly, this is why I tell developers that work with/for me to build in logging, day one. Not only will you always have clarity in every environment, but you won’t run into cases where adding logging later makes races/deadlocks “go away mysteriously.” A lot of the time, attaching a debugger to stuff in production isn’t going to fly, so “printf debugging” like this is truly your best bet.
To do this right, look into logging modules/libraries that support filtering, lazy evaluation, contexts, and JSON output for perfect SEIM compatibility (enterprise stuff like Splunk or ELK).
Heisenbugs are the worst. My condolences for being tasked with diagnosing one.
Last time I did anything on the job with C++ was about 8 years ago. Here’s what I learned. It may still be relevant.
const
, constexpr
, inline
, volatile
, are all about steering the compiler to generate the code you want. As a consequence, you spend a lot more of your time troubleshooting code generation and compilation errors than with other languages.valgrind
or at least a really good IDE that’s dialed in for your process and target platform. Letting the rest of the team get away without these tools will negatively impact the team’s ability to fix serious problems.1 - I borrowed this idea from working on J2EE apps, of all places, where stack traces get so huge/deep that there are plugins designed to filter out method calls (sometimes, entire libraries) that are just noise. The idea of post-processing errors just kind of stuck after that - it’s just more data, after all.
Yup. Nobody else gets those cookies.
Yeah, I know that the super-flat planar look was the intent, but there’s a reason why you don’t see much in the real world that resembles the cybertruck. It turns out that the non-planar features of typical car panels are there to add rigidity. Flat sheet metal wants to bend, twist, wave, and even flap in the wind. So there are probably internal supports or struts welded to the panel backsides, in order to keep them flat. Problem is, that process tries to distort the panels due to heat from manufacturing.
And since they opted for stainless, this adds additional problems. In this case: you can’t hide imperfections with bondo and paint. The panels have to be perfect, every time. It requires tolerances that belong on a sports car, not a pickup.
Pretty sure you just triggered every developer and/or person who had to sit through a product meeting.
NGL, I was feeling very uncomfortable myself by the end of typing said list. Is it hot in here? I need to lie down.
Common language used to dismiss bad decisions like this:
1 - Oh, did you turn off cookies or clear your cache? Sorry about that.
Oh no, I have to press up
200+ times if we’re counting all the detritus and failure in my command history.
There is an advantage to this approach though: fewer errors. You’re plucking a known working command from a list instead of manually typing a (possibly) broken version of it. Worse yet is when it’s a command where typematic mistakes cause unintended side effects like data loss. So, mashing up
100 times can be pretty smart, especially if you’re not a great typist.
Upvoted for the dancing and singing emoticon. Nice art.
I actually tried to use marketplace a few weeks ago. It was an unmitigated disaster. People either didn’t respond, had stale posts for items, or couldn’t get their act together to have a conversation (even with 12 hours between messages) about how to get shit out of their house. I have never yearned for old-fashioned yard sales so much.
Hamburger Shounens.
This explains everything. Most importantly: why the MCU kinda petered out after the Infinity Gauntlet arc. The power scaling was just off the charts1 in the end, with no more headroom for power growth. This usually kills Shounen-style stories.
1 - Along with the budget.
Oh, we’re on the same page there. I’m complaining about that too. Things are shifting from “make the environment easier for some people” to “painstakingly chisel out an expert mode like you’re escaping from Shawshank.” and I do not like it.