Yes, but “Proto Indo-European” doesn’t exactly roll off the tongue. /s
Yes, but “Proto Indo-European” doesn’t exactly roll off the tongue. /s
Food that contains nutrition, galactagogues, and folk-remedy ingredients to help with (human) milk production. Arguably, they’re just food.
I know this person and, honestly, it’s a thing of majesty. These discs have presence, heft, and are valuable. They’re collectors items on some level - every last one of them. So what if we’re watching “Jaws” or “Aliens” for the 400th time. We’re having a real, visceral experience here.
Put any distro in front of me and provided I don’t need to master it, I’m good. Ubuntu is fine. Debian is fine. RedHat is fine. Fedora is fine. I even have a tiny low-end system that is using Bohdi. Whatever. We’re all using mostly the same kernel anyway.
90% of what I do is in a container anyway so it almost doesn’t matter; half the time that means Alpine, but not really. That includes both consuming products from upstream as well as software development. I also practically live in the terminal, so I couldn’t care less what GUI subsystem is in play, even while I’m using it.
The only time I’ve encountered people that care a little too much about what distro is being used, is right after having transitioned to Linux; the sheer liberating potential of the thing can make you lose your head.
I’ve come across a lot of professional bias about Linux distros, but that’s usually due to real-world experience with tough or bad projects. Some times, decisions are made that make a given distro the villain or even the hero of the story. In the end, you’ll hear a lot of praise and hate, but context absolutely matters.
There’s also the very natural tendency to seek external validation for your actions/decisions. But some people just can’t self-actualize in a way that’s healthy. Sprinkle a little personal insecurity into the mix and presto: “someone is getting on great with that other Linux I don’t use, so Imma get big mad.”
Wood smoked salmon: ✅😀
Tobacco smoked salmon: ❌🤮
Honestly, Sony really sees itself as a premium(ish) brand that puts a heavy emphasis on novelty with a bit of sophistication thrown in. They also see Nintendo as a kid’s toy company. So, the expense (and some of the scarcity) is entirely the point.
peoplecustomers always just cut it off 5 words in for some reason…
Fixed that for ya. ;)
Great jebus. It looks like something Ginger Billy would build. There’s no way that’s street legal, nevermind the lack of license plate.
Mom, I want a cybertruck.
Honey, we have a cybertruck home.
Cybertruck at home:
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.
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.
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.
Java itself is kind of blissful in how restricted and straightforward it is.
Java programs, however, tend to be very large and sprawling code-bases built on even bigger mountains of shared libraries. This is a product of the language’s simplicity, the design decisions present in the standard library, and how the Java community chooses to solve problems as a group (e.g. “dependency injection”). This presents a big learning challenge to people encountering Java projects on the job: there’s a huge amount of stuff to take in. Were Java a spoken language it would be as if everyone talked in a highly formal and elaborate prose all the time.
People tend to conflate these two learning tasks (language vs practice), lumping it all together as “Java is complicated.”
$0.02: Java is the only technology stack where I have encountered a logging plugin designed to filter out common libraries in stack traces. The call depth on J2EE architecture is so incredibly deep at times, this is almost essential to make sense of errors in any reasonable amount of time. JavaScript, Python, PHP, Go, Rust, ASP, C++, C#, every other language and framework I have used professionally has had a much shallower call stack by comparison. IMO, this is a direct consequence of the sheer volume of code present in professional Java solutions, and the complexity that Java engineers must learn to handle.
Some articles showing the knock-on effects of this phenomenon: