Yeah. I’m starting to think the misspelling is not deliberate, but ironic - it’s one thing to have guns and a written warning saying you will use them. It’s another to loudly convey that you’re this dumb and also have guns.
- 0 Posts
- 194 Comments
Joined 10 months ago
Cake day: November 13th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
0·7 days agoIt’s worse than that. They think that toeing the line and refusing to deviate is the strong position to take here. Always has been.
0·8 days agoThank you!
I firmly believe this is how we wound up with tabs as a feature in the first place.
Thank you! I want to ::sniff:: thank my coach, the whole team ::sniff::, and especially my mom for helping make this happen! ::sniff:: Love you mom!
Here’s a version for my fellow gluten-free peeps:
0·10 days agoI 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.
0·15 days agoHonestly, 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 truly “printf debugging” like this is truly your best bet.
To truly 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.
- C++14 was alright, but still wasn’t everything you need. The language has improved a lot since, so take this with a grain of salt. We had to use Boost to really make the most of things and avoid stupid memory management problems through use of smart (ref-counted) pointers. The overhead was worth it.
- C++ relies heavily on idioms for good code quality that can only be learned from a book and/or the community. “RAII” is a good example here. The language itself is simply too flexible and low-level to force that kind of behavior on you. To make matters worse, idiomatic practices wind up adding substantial weight to manual code review, since there’s no other way to enforce them or check for their absence.
- I wound up writing a post-processor to make sense of template errors since it had a habit of completely exploding any template use to the fullest possible expression expansion; it was like typedefs didn’t exist. My tool replaced common patterns with expressions that more closely resembled our sourcecode1. This helped a lot with understanding what was actually going wrong. At the same time, it was ridiculous that was even necessary.
- A team style guide is a hard must with C++. The language spec is so mindbogglingly huge that no two “C++ programmers” possess the same experience with the language. Yes, their skillsets will overlap, but the non-overlapping areas can be quite large and have profound ramifications on coding preferences. This is why my team got into serious disagreements with style and approach without one: there was no tie-breaker to end disagreement. We eventually adopted one after a lot of lost effort and hurt feelings.
- Coding C++ is less like having a conversation with the target CPU and more like a conversation with the compiler. Templates,
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. - At some point you will need
valgrindor 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. - C++ assumes that CPU performance and memory management are your biggest problems. You absolutely have to be aware of stack allocation, heap allocation, copies, copy-free, references, pointers, and v-tables, which are needed to navigate the nuances of code generation and how it impacts run-time and memory.
- Multithreading in C++14 was made approachable through Boost and some primitives built on top of pthreads. Deadlocks and races were a programmer problem; the language has nothing to help you here. My recommendation: take a page from Go’s book. Use a really good threadsafe mutable queue, copy (no references/pointers) everything into it, and use it for moving mutable state between threads until performance benchmarks tell you to do otherwise.
- Test-driven design and DevOps best-practice is needed to make any C++ project of scale manageable. I cannot stress this enough. Use every automated quality gate you can to catch errors before live/integration testing, as using valgrind and other in-situ tools can be painful (if not impossible).
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.
“this is as far as you can go if you don’t want to get involved in management”
Yes. That exactly. This typically comes with a nice perk: Principals are supposed to have the same clout as lower-level managers. Which is to say they usually report to Directors or even the CTO in some organizations.
Another one is “Independent Contributor” which is similar but, as the name would suggest, is very self sufficient and does not work on (or for) a team. They’re basically one-man engineering shops and are expected to perform well everywhere in the company’s tech and talent stacks. As a result, ICs are very rare.
The other pivot point is The Pragmatic Programmer, which is totally understandable.
That book does a good job of grounding the reader through examples and parables from everywhere else but IT. By the end, you realize that good software engineering makes the best of general problem-solving skills, rather than some magical skillset peculiar to computing. You wind up reaching a place where you can begin to solve nearly any problem through use of the same principles. So @codex here, perhaps effortlessly, went on to management instead.
Same. Let’s rock.
Printed on the bomb:
| In case of accidental detonation: have a nice day. Thanks for reading.
I’ve tried to enjoy IPAs, really. I’m not discounting the role of interesting terpenes and flavonoids here, but the raw in-your-face excessive bitterness of IPA-level hops pushes all that great stuff so far from the stage of my experience, that it’s all left waiting in the lobby to get seated. For me, it’s like someone mixed LaCroix, light beer, and a drop of dish soap in a glass. Every time.
Thanks, I hate it.
But seriously, I just held a credit card for a solid minute. This is sobering. Bio-accumulation is a bitch.
Yup. This goes back to the Southern strategy which was brought to the fore by the Nixon campaign (although it was in play since before then). From that era we also get this chilling warning from Barry Goldwater:
Mark my word, if and when these preachers get control of the [Republican] party, and they’re sure trying to do so, it’s going to be a terrible damn problem. Frankly, these people frighten me. Politics and governing demand compromise. But these Christians believe they are acting in the name of God, so they can’t and won’t compromise. I know, I’ve tried to deal with them.
Common language used to dismiss bad decisions like this:
- We need to track and meet our metrics for the quarter
- Engagement for $FEATURE is down, so we have to take measures to get people to take notice
- It’s opt-in/opt-out, so it’s the right thing to do
- It’s only a one time thing and then the system remembers1 what the user selected
- Only new users are affected - our power users will put up with it
- It’s just a minor inconvenience, really
- It’s just a website
1 - Oh, did you turn off cookies or clear your cache? Sorry about that.
While I think Orwell’s “newspeak” was contrived, it did illustrate the point in strong relief as something unfamiliar… at least at first. But I don’t think he was predicting the future. Instead, I think he was warning the reader of what dangers are already with us.
Honestly, I think this has always been a thing. The spoken word is often inexact as a form of communication efficiency; if the other party has the same ideas in their head as you, pronouns, idioms, recalling past events, are all powerful ways to compress dialogue. However, that same inexactness leaves the door open for doublespeak, dogwhistles, and suggestion in place of fact. Language as a means of control is just in how you use it; the underlying mechanisms were always there.