Amazing Talk! I seem to be alone in the war against over engineering, over complicated code, over use of patterns, and dogmatism that plagues companies. I read John's book and loved it, I recommend it to everyone. I'll keep fighting for simplicity and pragmatism and this talk is going to be with me for some time. As other commenters say, it would be great to have a part 2 or to refactor the talk to focus a lot more (or with greater detail) on giving plenty of examples where code could be radically simplified.
This talk offers perspectives that should be taught in first semester Uni. Possibly, they might be lost on the new learners, though. They are that deep and relevant... :)
Producing simple, readable and maintainable code is not a skill you are taught, it is picked up after years of battling through large, complex and over-engineered systems using modern "best practices".
Possibly? Certainly. Not that it's a problem, this talk is nothing more than something people who already 'get it' can nod to. Nothing really practical to be gained
Thanks for all but I would have taken more examples of code about the things you recommend doing. Something like : on the left what I consider a bad design and on the right here what I would have done for each point you are mentioning.
Interesting how the speaker propose “code that is easy to understand without domain knowledge” as a good rule in complete opposite direction of what domain driven development “movement” preaches, but at the same time arguing the analogy with writing a good book
Talks like this are really a breath of fresh air.
This is not just software and design... this is philosophy.
The role time plays in the relevance of ideas and implementations is often ignored. So good to see David point this out several times in this talk.
Amazing Talk! I seem to be alone in the war against over engineering, over complicated code, over use of patterns, and dogmatism that plagues companies.
I read John's book and loved it, I recommend it to everyone.
I'll keep fighting for simplicity and pragmatism and this talk is going to be with me for some time.
As other commenters say, it would be great to have a part 2 or to refactor the talk to focus a lot more (or with greater detail) on giving plenty of examples where code could be radically simplified.
This talk offers perspectives that should be taught in first semester Uni. Possibly, they might be lost on the new learners, though. They are that deep and relevant... :)
Producing simple, readable and maintainable code is not a skill you are taught, it is picked up after years of battling through large, complex and over-engineered systems using modern "best practices".
Possibly? Certainly. Not that it's a problem, this talk is nothing more than something people who already 'get it' can nod to. Nothing really practical to be gained
I see we see things the same way, David!
Thanks for all but I would have taken more examples of code about the things you recommend doing. Something like : on the left what I consider a bad design and on the right here what I would have done for each point you are mentioning.
Interesting how the speaker propose “code that is easy to understand without domain knowledge” as a good rule in complete opposite direction of what domain driven development “movement” preaches, but at the same time arguing the analogy with writing a good book
Great talk!! 💯
yeah sorry this is too wish washy for me and won't add anything I can implement to my daily work.
waste of time