dennisschroeder / thoughts-on Goto Github PK

1. The basic point, that complexity is a massive problem, makes sense to me.
2. The industry examples are interesting
3. Fred Brooks is mostly known for The Mythical Man Month.
4. Swap the order of accidental and essential complexity.
5. Ironically, "Hexagonal Architecture" also adds complexity. I have found that good software teams sometimes remove parts of it, particularly the interfaces and splitting into modules, to reduce cost of change. So, yeah, there is some value and some YAGNI in these architectural solutions, in my opinion.
6. Of course I like the bit about "Maximise the amount of work not done" and "Lean Experimentation" the most :). The tricky thing is how to get people to actually do this stuff. I'm still working on that. I came up with the name "push towards production" the other day for what I try to to. Last week I started a project which wants to first deliver value to users after 1 year. I want to influence (push) them to offer some small part of the system to the users much sooner.
7. I like the conclusion. This sums up the message pretty well.

All in all it makes sense, the hard part is in influencing people around you to understand the danger their product is in, and to change their thinking. That's why I tell people that I work as a psychologist :). Let me know if you have any tips for this.