Greg Young discusses eight lines of very common code finding in them massive numbers of dependencies and difficulties, looking for ways to get rid of them.
Greg Young is an independent consultant and entrepreneur. He is always involved with many concurrent projects, currently these include building out a distributed event store and mighty moose (a continuous test runner). For periods of years Greg has been known to stop living anywhere and just travel. Twitter: @gregyoung
Software is changing the world; QCon aims to empower software development by facilitating the spread of knowledge and innovation in the enterprise software development community; to achieve this, QCon is organized as a practitioner-driven conference designed for people influencing innovation in their teams: team leads, architects, project managers, engineering directors.
Apt to this talk - an interesting comparison of OO and Functional code bases
OO design practices lead to unnecessary bloat in the number of types and the dependencies between them.
Don't decouple when you don't need decoupling
As a consequence, I really have no idea what this guy is on about despite being curious and interested.
Greg, as usually, is very bold in his statements, but he has reasonable arguments to back them up.
Where in the EventStore source code is the wiring-up done?
I only just found this now - awesome show! You mentioned that to see an example of the 200 lines of dependency wiring code, we should look in the EventStore source. I've been looking at it on GitHub, but am struggling to find the actual startup code. Whereabouts is it?
Re: Where in the EventStore source code is the wiring-up done?
Not Introducing Frameworks Should be Your First Thought!