I think they are now more important than ever as there is more code being pushed out than one can read to see if it is robust as the agents claim.
I think they are now more important than ever as there is more code being pushed out than one can read to see if it is robust as the agents claim.
3 comments
In fact, I see this as an opportunity to build anew and better. When you're no longer constrained by legacy baggage and constraints, you can collapse layers and introduce new ones that better fit what you're creating.
I'm doing that in the project I'm working on at work. Being able to redefine how serialization/deserialization fundamentally works and interacts with domain objects is giving us unbelievable expressiveness, not by the amount of code written (in fact, it's heavily factorized across layers that were historically separate), but by exploring new designs paradigms.
Don't just read these books. Write some new ones.
For stand-alone bits of code where I don’t really care about the implementation, I will let an agent go wild. But for production code in the legacy code base, not a chance I’m doing that.