How NOT To Be a Code Monkey
Tech Talk | by Dhananjeyan Balaretnaraja
Are you fully aware of the purpose of the product you’re developing and how it will affect the users? Do you actively participate in the development process and give your input on how to improve this product? Are you on your way to becoming an expert in your domain?
If the answers are ‘no’, then, my friend, you are a typical code monkey. But don’t worry, you are not alone and, more importantly, there is a cure.
In the video below, Martin Fowler — software developer and renowned author — talks about how conversational stories help software engineers build better software and become real engineers.
Instead of being a passive recipient of requirements, Fowler encourages you to get into a conversation with the users/clients and actively contribute in shaping up the software you are developing.
Here is a summary of Martin’s notes on how to evolve from a code monkey into a software engineer:
1. Participate in and contribute to the development
“We build whatever we’re told to build,” says Martin. Are you that guy?
You have much more to offer than serving the orders. Take an active role in the development by offering your expert opinion and suggestions.
Think of Amazon. “Frequently bought together” feature brings them millions in revenue and it never would have happened had their software engineer thought he’d better stay out of planning.
2. Know your domain
Don’t sweat the tiny programming language updates. Instead, invest your efforts into learning more about the domain. Go beyond technicalities. This will significantly improve the quality of your contribution.
3. Take responsibility for your code
…
Originally published on www.CreativeSoftware.com/Blog
