Hype Driven Development – DaftCode Blog英文学习资料 .pdfVIP

Marek Kirejczyk Follow vp of engineering @ daftcode.pl, owner @ , founder @ Nov 23, 2016 · 9 min read Hype Driven Development oftware development teams often make decisions about software S architecture or technological stack based on inaccurate opinions, social media, and in general on what is considered to be “hot”, rather than solid research and any serious consideration of expected impact on their proj ects. I call this trend Hype Driven Development, perceive it harmful and advocate for a more professional approach I call “Solid Software Engineering”. Learn more about how it works and find out what you can do instead. New technology — new hope New technology — new hope Have you seen it A team picking newest, hottest technology to apply in the proj ect. Someone reads a blog post, it’s trending on Twitter and we j ust came back from a conference where there was a great talk about it. Soon after, the team starts using this new shiny technology (or software architecture design paradigm), but instead of going faster (as promised) and building a better product they get into trouble. They slow down, get demotivated, have problems delivering next working version to production. Some teams even keep fixing bugs instead of delivering new features. They need ‘j ust a few more days’ to sort it all out. Hype Driven Development Hype Driven Development (HDD) has many flavors and touches your proj ect in many different ways: • Reddit driven development — when a team or individual decide on technology/architecture/design based on what popular blogger wrote or what is hot on reddit, hackernews, blogs twitter, facebook, GitHub or other social media. • Conference driven development — watch carefully what happens after people are back from the conference. People get inspired. And that’s a two-edged sword. Starting to use newe