←back to thread

116 points benterix | 2 comments | | HN request time: 0.438s | source
Show context
ChrisMarshallNY ◴[] No.45161923[source]
A classic. I was just getting started, when he wrote that, and that kind of thinking informed a lot of my personal context, throughout my career.

I feel as if a lot of multipliers have happened that he didn't anticipate, but I also feel as if the culture of software engineering has kind of decomposed, since his day.

We seem to be getting a lot of fairly badly-done work out the door, very quickly, these days.

replies(2): >>45162030 #>>45165361 #
convolvatron ◴[] No.45162030[source]
I think we only got to this point because of a near-complete erosion of personal responsibility

  - agile and devops both conspire to treat developers as replaceable standins

  - we're not even really expected to hang around and see the consequences of our decisions

  - on arriving in a new organization, we're presented with a heap of trash we're asked to just sort of keep it running, certainly not to fix it

  - 'industry standard best practices' win over a well designed bespoke solution every time, developers are just expected to write a little glue at most

  - managers aren't expected to know anything about the domain at all, but to track people to make sure they did what they said they were going to 

  - speed to feature is the only metric. instability can be papered over with bodies

  - we pretty much stopped systemic testing a couple decades ago 
so given that we've been on autopilot to a vibe-coding wonderland for quite some time, I guess we shouldn't be surprised that we've reached the promised land.
replies(3): >>45162592 #>>45162852 #>>45163186 #
1. readthenotes1 ◴[] No.45162852[source]
"agile and devops both conspire to treat developers as replaceable standins "

There is a lot of irony in that since the first plank of the agile manifesto is to put individuals in interactions first.

And I noticed you put the development process/structure first over the people who want to treat people as fungible.

replies(1): >>45163579 #
2. ChrisMarshallNY ◴[] No.45163579[source]
Well, to be fair, there's what I call "pure" Agile (as in the Manifesto), and then "real-world Agile" (what has the name, but doesn't really seem to follow the Manifesto).

I always liked the Manifesto, but it's really rather vague, and we engineers don't do "vague" so well, which leaves a lot of room for interpretation.

And authors.

And consultants.

And conference speakers.

Those are the ones that form what is eventually implemented. I'm not really sure any of the original signatories ever rolled up their sleeves, and worked to realize their vision.

It's my experience, that this is where the wheels start to come off the grand ideas.

That's one thing that I have to hand to Grady Booch. He came up with the idea, wrote it down, and then started to actually make tools to make it happen. Not sure if they really launched, but he did work to make his ideas into reality.