Comment by fragmede
8 days ago
That is fascinating. thank you for digging out that quote. Maybe I should get into book writing.
> with few business rules. Staff is not composed of advanced object modelers.
That seems dismissive of the people who live day-in-day-out with the problem at hand. In my experience, most people are actually advanced data modelers, but they spend their energy on that on people instead of machines. Makes them less gullible than me but worse at computers, so it's a wash.
> Rich capabilities were never requested. >
When you have to deal with someone else, especially from a different department or outside team, that you don't trust, revealing your rich inner data model of the situation at hand is not only not to your benefit, but often to your detriment. Especially with a history of IT projects not landing or going wrong. You're not getting those rich requests because you (well, the quoted author) isn't being trusted.
The advice is good, but dated. What do vibecoders who hit the wall need? Teaching people that wanna learn SQl has gotten a lotta people rich. Lemme talk to a thousand of the people vibecoding appa and lemme write their book. (After reading that book from 2003.)
I suspect that vibe coders who hit a wall need the same thing that programmers from 2003 who hit a wall needed. Talk to the business people, get an understanding of their domain and the problem at hand, and model that as a series of anthropomorphic objects that encode the business rules in the language that the domain experts already used (tweaked by the need for disambiguation and clarity). Back in the day, this was software design, a distinct skill (and often job!) from computer programming.
I'd love to read your book, if you write it. Anybody who's talked to a thousand people trying to solve the same problems will have an amazing perspective and a lot to teach.