Hype driven development
2 likes1,674 views
Hype driven development focuses on the latest trends and frameworks while solid software engineering prioritizes conferences, blogs, documentation, test-driven development, problem solving, and having a strong technical background. While hype can have value, the author believes solid engineering practices are more important for building software the right way. Certain popular figures and approaches may receive disproportionate attention without proven results for solving real problems.
Hype driven development
- 1. Hype Driven Development vs. Solid software engineering
- 2. Hype
- 6. With ideas spreading? Whats wrong?
- 8. Hype Driven vs Solid Engineering ● Conferences ● Blogs ● Stack overflow ● Loudest guy ● Framework talkers ● Fancy pairing interviews ● Need driven ● Trade-offs (Well informed) ● Good TDD ● Spikes ● Documentation ● Strong background ● Problem solving recruiting
- 9. That is, while there is value in the items on the left, I value the items on the right more. Disclaimer
- 11. ● NoSQL ● DDD, DCI, Hexagon Architectures ● Microservices ● DHH - TDD is DEAD ● Js MVC frameworks (and Wars) ● React.js Examples of Hypes in Rails/Web community
- 12. Who is that guy?
- 13. Is he real authority? ● Is this solving specific problem or is a silver bullet? ● Is it problem that we have? ● Proven track record? Doing very hard things? Or is he a web/mobile developer?
- 17. ● Author of multiple engineering books ● Founder at ThoughtWorks ● Build a web framework ● some (popular yet simple) web apps.
- 18. DHH did some great things and I don’t mean to underrate his achievements, I just prefer to listen to Fowler when it comes to software engineering and organising teams. Disclaimer
- 19. Great ideas ● Takes time to get popular ● Are not obvious to understand ● Require time & background to comprehend ● Are never silver bullets ● Don’t require emotional language to promote