I am in the privileged position of knowing that, despite what some may tell you, there is in fact such a thing as "too much garlic".
One of the first dishes I made for a family potluck as an adult was a broccoli salad thing. I followed a recipe. But I thought "clove" meant "head". 6 servings of salad with an entire, *large* head of garlic, minced. It was literally painful to eat due to the astringency.
You see it a lot in software. When your aim is to get done and move on to the next thing, like you're playing speed chess, it's very difficult to build knowledge and expertise. Moving fast narrows your experience of the work. You gain less from having done it.
Organizations encourage this almost by default, but to their own detriment, and that of the employees. It's very efficient in the short term, but the long term costs are huge.
The world is full of companies that are getting tons of work done, but learning almost nothing. And they try to chain their employees to the same fate, all in service of the next quarterly goal.
My advice to you is to, whenever you can manage it, not let them rush you. Take time to gain the full individual benefit of having done the work. Dig deeper, push further, find out why, experiment, learn things that are not immediately useful. These things make your labor powerful.
@inthehands I keep seeing people say the Atlantic is going down the toilet, but I'm not sure what kind of thing is being referred to. I still find them to be generally far better than NYT or WaPo. But maybe that's a low bar now?
We have to make sure Trump does not get a second term. But that does not end the clear & present threat to Democracy.
A large swath of the Republican apparatus has proven that they are not only willing to let a strongman push them around, but they are actually proactively complicit. "Project 2025" is, explicitly, a roadmap to autocracy and it is being pursued actively right now. A willing president is just the capstone.
I'm disgusted by the milquetoast "analysis" that mainstream media has been sliding in since Trump hit the scene.
WaPo: "Alito's Account of Upside-down Flag Doesn't Add Up"
AYFKM? This "analysis" isn't worth the price of the electrons it lit up on my screen.
We don't need analysis here. The SCOTUS conservatives have abandoned all pretense of impartiality, openly champion motivated reasoning, & proudly proclaim their allegiance. The Rule of Law is dead in America. That's the fucking headline.
I was today years old when it occurred to me upon reading the phrase "with kid gloves" for the 1000th time in my life, that "kid" is the word for a juvenile goat.
And I thought maybe "with kid gloves" doesn't mean some kind of gentle glove for dealing with children, but rather a fine and supple leather made from the skin of juvenile goats, which might give the wearer dexterity and sensitivity not achieved with other kinds of work gloves.
Programmers could probably lean some things about building resilient systems from people who design processes that are not implemented in computer software, and from the people who are part of those processes when put into practice.
Slack is crucial for scaling and for organizational health in general.
People with slack have headspace and time to improve things, to think ahead, to sweep out the corners, to prepare for what's coming next. And they will see these needs before management does.
"Running lean" eliminates slack. This only works for a while, and only if you have a flat org of highly self-actualized people who you give autonomy. And you'll still burn people out eventually.
If you take away both slack and autonomy, (I.e. "running lean" but with a stratified org) you get the worst of both worlds.
Laborers are expected to spend every billable moment working on work defined and prioritized by someone else. They are unable to use their intimate knowledge of the work to improve how things work, to prepare for what's next, to keep things tidy and safe, because none of this has "value" for management.
This is an org that will grind itself to powder before it succeeds.
Eliminating slack is almost inherently anti-autonomy, though. It is management saying they think they know everything that needs to be done, and especially what doesn't.
Except they don't and can't know this. And they don't want to make all of the decisions that they are preventing others from making, either. So everyone is busy, and yet critical work doesn't get done.
Workers all know this, and either burn out or check out.
Microsoft Recall on your work PC, keeping a stockpile of screenshots. LLMs used to "understand" your work activity by rifling through the screenshots. Your manager getting a report generated from that information, and using it measure your productivity and performance, accuse you of time theft, etc.
People and organizations tend to drift toward waterfallish project management due to low-trust or high-risk situations.
(Oh, and trust and risk are mutually, inversely reinforcing. Low trust ➡ higher risk. High risk ➡ lower trust.)
It's not particularly good at addressing these challenges, but it seems to offer assurances, and that's what people want. They want documented commitment. They want to know they can lay blame. It makes them feel better.
I think I finally have some words for my feelings regarding the "none of us knows what we're doing, we're all just trying to suck less" perspective.
Saying specifically that thing is "nice" but not "kind." It is achieving good feelings and psychological safety by way of deception.
I remain hopeful that we can be welcoming to beginners and avoid gatekeeping, while still acknowledging that there *is* actually a lot of accumulated knowledge and wisdom that is beneficial to learn.
I've basically given up on trying to police people's usage of the words "tech debt", but one hill I will die on is that we ought to replace it with "maintenance" whenever appropriate. Which is often.
"Maintenance work" is something most executives seem to understand, because it's not unique to software. ("Care and feeding" covers additional ground but seems less generally intuitive, IME.)
I still occasionally see people grouse about async/await and how it is "viral" in code.
I get it. This was my initial reaction too. But then I recognized that this is not a unique phenomenon. It's a pattern that happens a lot in software. It's not a flaw. What you are seeing is a kind of modality presenting itself.
Hobbit tendencies. Indoor enthusiast. Books and games.Software architecture. System design. Tidy first. Slow is smooth and smooth is fast.Humane management. Sustainable business.Democracy. People before property. Freedom from religion. We're all in this together.