Do Really All Projects Fail Because of Code?
Join the DZone community and get the full member experience.Join For Free
today i’ve read two interesting posts: the cost of code by @unclebobmartin and code as a cause of project failure by @docondev . they discuss various arguments to prove that all projects fail because of code. the main argument is that if code is free and light-fast to change, project can’t fail. ok. but this case is rather extreme and obviously impossible. we don’t live in a world with hyper-space jumps, teleportation and free medicine (unfortunately). in real life code costs a lot and it will be true in the next decades for sure, so this argumentation proves nothing. in ideal world there is no such thing as code . in ideal world you have a solution in seconds without computers, software and other complicated things. so i don’t buy this idea. code is not the main reason for projects failure in reality.
code is not free. code is expensive. we do not sell source code though, we sell solutions. if it is possible to create a solution without source code, it would be fantastic. let’s take an industry that handles tangible objects. automobile industry does not sell carbon and metall — it sells cars. it sells a solution to transportation problem. teleportation is an ideal solution, but we can’t teleport nothing but electrons, sadly. we buy cars to get from point a to point b. we buy a solution .
code != solution
i think the main problem with projects is that they provide either bad solution or no solution at all . nobody buys stagecoaches these days, since there are more efficient solutions. if a project does not solve anything, it will fail. if a project solves something, but in a nasty, unusable way, it will fail. you can create an absolutely beautiful architecture with the cleanest code in the world. you may have 100% test coverage, complete separation of concerns, flat hierarchies and methods without boolean arguments. you may have all that beauty, but still fail miserably if the program does not solve user’s problems efficiently.
you may argue that with clean code you can refactor it fast and change everything. c’mon, it will be a full re-write if it solves the wrong problem. can you fix a stagecoach to make it a true competitor of a car?
on the other hand, if a projects solves a right problem, but with some issues, clean code is very important. you can’t adopt fast without it. you can’t change things and react to people demands.
don’t get me wrong, i believe that clean code is an important thing, but it is not the most important asset in software development.
Published at DZone with permission of Michael Dubakov, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.