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
Ideally yes. This is me and Mrs. Warp Core and I wouldn’t change it for the world.
However…
Well, let me put it this way. Ever have a best friend that, after spending a lot of time around, you find out that you actually can’t stand more than a few hours at time? That is absolutely a possibility here. Only now their stuff is in your house (or vice-versa), and/or they’re on the same lease.
$0.02: It may not always be advisable, but absolutely benchmark the practical aspects of your romance long before tying the knot. Long-term co-habitation is not the only route here. Consider other ways to rack up large blocks of time: getaway vacations, long weekends, or even just “play house” for a few days at a time. You’d be amazed at what horrible, terrible, filthy, obnoxious habits your partner has when “at home.” The reality is that everyone is a bit (more) of a mess in private, and the only real question you have to answer is: “what am I willing to put up with?”
I was in the “gifted/advanced” track too. Teachers saw this one of two ways. Half of them got the memo: you got extra interesting stuff to noodle through because we’re all under-stimulated in a typical class. The others decided to just double your homework load and call it a day. At least the teachers in the first group had some interesting takes on brain teasers and reading material.
And on that note: I must have thought about Flowers for Algernon every week since I read it. Since the 90’s. I’m tired, boss.
Sometimes teachers field stories like this to foster critical thought and encourage insightful book reports. It’s stimulating material even with a flawed premise, and that’s the point.
My teachers always seemed to be the type that had these stories in the curriculum, but weren’t the type to follow up with the thinky-thinky bits. This had rather predictable results.
Top of mind for this subject: Flowers for Algernon.
Of Mice and Men might qualify, but weighs in at 100 pages. I’m not sure what the threshold is for “short.”
On my own time in High-school, I read: I Have no Mouth and I Must Scream.
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.
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.
margarine is absolutely fine
It’s hydrogenated cooking oil; trans-fats. It is absolutely not good to eat regularly.
Apparently that’s no longer true. Thanks fellow lemmings for setting the record straight.
That said, I do appreciate it for it’s long shelf life and availability when better foods are expensive or unavailable.
To me, aspartame tastes plastic-y and reminds me of how hot asphalt smells. It has more of a chemical taste than a sweet one. Toothpaste gets a pass only because of all the mint that masks it.
Sucralose (Splenda) can taste rather like aspirin in the right concentration. Again, it’s “sweet” in a way but isn’t quite right.
This man is a menace and must be stopped.
Eh, I’m used to it.
This is fine.
Good fences make good neighbors.
Corollary: server-side commit hooks make good teammates.
Oh. That’s good.
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: