The 15 most popular myths in software development
What myths in software development have you fallen for? Or perhaps you don’t believe them to be myths at all? We examine some cracking examples of superstitious thinking when it comes to developers and design.
The software development field is full of myths, superstitions and false assumptions. If you ask developers for the most effective way to do something, you’ll probably get more than you bargained for. Some opinions are, although proven wrong, more widespread than others.
To find out which myths are most prevalent amongst developers, Lee Semel, a business owner, software developer and UI designer, has asked the question on Quora.com. Here’s a quick rundown of the hit list – and try not to chuckle.
15. Design is nothing more than a surface distraction. The more important parts are found under the hood, and are worth paying attention to. What use is a beautiful application without appreciating the groundwork?
14. Agreeing on specifications means agreeing on features, regardless whether specifications are fuzzy and subject to different interpretations.
13. Software development always works best when there’s more than one path to your destination. Developers should have as much freedom as possible – ideally they should be able to do what they want.
12. A customer always knows exactly what they want. They’re also able to articulate this desire so that everyone understands it. After all, its their project, so they’re the expert – not the developer.
11. Designers care only about the design of an application and are unable or unwilling to learn how to code. They need to be protected from real code.
10. If you can’t deal or interact with people, then consider a career in software development!
9. The more developers working in a team, the more efficient it’ll be. You can dismantle even the most demanding tasks into small parts, which can then be completed by non-professionals.
8. The best technical solution always wins.
7. In the software field, it’s all about what you see at first glance, meaning that the design of software is paramount. Understanding what powers it underneath is too hard.
6. If you’ve released your application or website, then all your work is done. Developers no longer need to deal with any issues.
5. The Waterfall method can actually work in software development. It makes sense – a project can accurately and effectively be planned and specified before work even begins. The individual steps of the project should always be addressed in succession, too. No exceptions.
3. The best software developers are the ones who are good at math. They’re the ones learning programming in their spare time while they’re actively engaged in theoretical mathematics. Lovers of logical puzzles produce the best code.
2. Marketing doesn’t really matter for developers and is best left to the “suits”.
1. If you’re running into problems with your current practices or framework, it’ll always be another language, technology or process that reveals itself as the “silver bullet”. But never the stuff you’re currently using. You should try changing your strategy as often as possible – at least once a week.
What do you make of this list? Do these points perhaps hold some truth? Let us know in the comments below.