People might think software development is similar to building a house from a plan, which is a linear process. But how do "nerdy code crunchers" really work?
Read the full blog post and bonus myths at http://bit.ly/2ayoklM
Unlocking the Power of ChatGPT and AI in Testing - A Real-World Look, present...
10 Myths in Software Development to Debunk Now
1. 10 MYTHS IN SOFTWARE DEVELOPMENT
TO DEBUNK NOW
MYTH
REALITY
V E R S U S
2. Building software is a predictable
process, like building a house
MYTH REALITY
Feature creep, external
market, technology change
Adding more people will
speed production up
It takes time for people
added later to a project to
truly become productive
Uncertainty factors:
3. It's all about coding, maths,
and logic
MYTH REALITY
It can be an art, especially at
high-level softwqare
architecture
There's a silver bullet
software development
methodology
You always have to balance
the triangle: time, money
and functionality
4. Certificates (badges) prove
high quality
MYTH REALITY
- Real project examples are better
indicators.
- Certificates may be easy
to acquire.
- Time spent on getting
certified may be unjustified.
Adding or changing features
at any point is no big deal
- Changes may not benefit
end-users.
- Changes may affect whole
architecture.
- Cost of changes may
outweigh benefits.
5. MYTH REALITY
You should strive to get the
most superior technology
There's a risk of over-serving
your customers
Releasing the software product
means that the project has come
to an end
Consider updates as
technology, the business
and users evolve
6. MYTH REALITY
Using common KPIs will
result in better performance
Using the wrong KPIs to
motivate programmers can
hurt over the long run,
resulting in unhealthy
internal competition
Software can be bug-free
Unless you have the scale
and budget of NASA, there
will be at least some bugs in
your software
63%
7. T H A N K S F O R R E A D I N G
C R E A T E D B Y
Read more at: blog.enabled.com.au/myths-software-development