Published: 22.02.2018 05:44

Example of software development myths

«Example of software development myths» in pictures.

The 15 most popular myths in software development - JAXenter

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.

Seven more myths of formal methods: Dispelling industrial prejudices

The loner stereotype can deter talented people from the industry — not just women, but anyone who thinks that sounds like an unattractive job description. It can also result in dysfunctional teams and poorly performing products. Empathy, after all, is crucial to understanding consumers’ desires, and its absence leads to product mistakes.

Some Myths in Software Development

While a talent development program would indeed have greater returns if you begin training new hires the moment they start working for the company, there’s nothing to suggest that it won’t benefit existing employees of any skill level and seniority.

Software security is about building security into your software as it is being developed. That means arming developers with tools and training, reviewing software architecture for flaws, checking code for bugs, and performing some real security testing before release, among other things.

Yet, though hard data and credible studies are still hard to come by, the theme of the “software crisis” continues to dominate the literature there is widespread agreement that bugs, poorly thought out software, frequent security breaches and huge budget overruns aren’t just a fact of life, but areas where improvement would be both possible and welcome.

Our last myth is about scale, and it's a very widespread myth that needs more active debunking. Today's application portfolios are often quite large -- thousands of apps -- and getting started back in the day meant identifying those apps that carried the most risk and focusing all of the attention on them.

There is even a trope of “programming, motherfucker” – which aims to delegitimize people who think talking (and writing, and thinking) about software development is at least as important as actually cutting code. If you’ve followed me this far, you’ll easily see this for what it is – a force field erected to protect myth from critique.

Then there is tech’s other side, acknowledged reluctantly, if at all: the fact that IT professions have a large gender skew that they’re actually actively putting off people from marginalized groups, not just failing to interest them.

As we discussed earlier, idle time is anathema to managers. They tend to exploit any downtime by starting a new project. Even if the task cannot be completed because people have to return to another project, managers reason that anything accomplished on the new project is work that won’t have to be done later. Such thinking leads companies to start more projects than they can vigorously pursue, diluting resources.

The Upshot provides news, analysis and graphics about politics, policy and everyday life. Follow us on Facebook and Twitter. Sign up for our newsletter.