Unintelligible code
Have you ever given code to a non-developer? People don't know what to do with it! Code is unintelligible.
When you hand code to a client, they'll ask, “What now?”
They're not developers and have no idea what to do with the code you wrote for them. Even though it could have saved them hours, the code was useless. They didn't know how to run it.
To make a solution valuable, it's a good idea to write some documentation on how to run the script. Then you can teach them what to do next.
Bottom line: Code by itself is only useful with some documentation, maintenance, and support.
The job is about solving problems
Software engineers are paid to automate business tasks. To do that, they deploy, document, and maintain code.
Writing code is actually a small part of solving the problem.
Experience makes code valuable
We take it for granted, but it's our experience deploying code that makes software developers such valuable employees.
It's all the other things around the code that make it usable:
- Choosing an architecture and bringing code together to solve complex problems
- Deployment strategies to get code working and maintain uptime
- Good documentation on how to use the application
- Better yet, good UX, so the product is intuitive to use and you don't need as much documentation.
- Incident response to solve problems when they occur
It only becomes useful once it's deployed, documented, and maintained.
The value chain
Software engineers are critical to the business value chain. Companies spend a lot on engineering because it's the foundation for creating business value.
I like to think of our work as part of the value chain. As you move up this chain, you also climb the career ladder in the organization (from junior engineer to CEO).
Code is valuable only when it's deployed as an application. Applications are valuable only if they're understandable and easy to use. Usability is valuable only if the application solves a business problem. Business problems are valuable only if they increase revenue or reduce costs.
Start thinking of your code as part of the value chain. It will change your perspective and your approach to work.
