It is not how I interpreted it. What I heard was salesman pitching an expensive product as a bargain.
Even though frameworks have lots of drawbacks, I think it solves one problem really well, it gives you, the team, a direction.
Doing Event souring & CQRS correctly takes years of experience, this can be concluded by reading articles like this one or watching any of video by Greg Young.
In a sense the origin of this article stems from the notion that no framework is needed. I think that is a setup for disaster by selling developers the idea that this is easy, when it isn't.
In my experience frameworks have often learned me how not do things. Frameworks are condensed experiences that you don't need to learn yourself, someone else has already done the mistakes for you. This is a huge time saver & gives you, the developer, experience at a lower cost.
With that experience going frameworkless can then be achieved if necessary.
However my interpretation of it can be exaggerated due to the fact it was a short statement without much context.
Even though frameworks have lots of drawbacks, I think it solves one problem really well, it gives you, the team, a direction.
Doing Event souring & CQRS correctly takes years of experience, this can be concluded by reading articles like this one or watching any of video by Greg Young.
In a sense the origin of this article stems from the notion that no framework is needed. I think that is a setup for disaster by selling developers the idea that this is easy, when it isn't.
In my experience frameworks have often learned me how not do things. Frameworks are condensed experiences that you don't need to learn yourself, someone else has already done the mistakes for you. This is a huge time saver & gives you, the developer, experience at a lower cost.
With that experience going frameworkless can then be achieved if necessary.
However my interpretation of it can be exaggerated due to the fact it was a short statement without much context.