The human side of software development.
Applying development practices against every-day life, and applying life lessons to development
This is developer++
I tell my kids all the time to make the world a better place, and it’s something I try to live by as well. How much better you make it is basically irrelevant, and ultimately out of your control. People around you choose how to respond, all you can do is provide situations / conversation that are positive.
Did your actions today contribute joy, love, thankfulness, companionship, comfort, and / or peace to someone around you?
Or did you introduce hatred, fear, contempt, sadness, loneliness, and / or jealousy into the world today?
There is great power in the cumulative effect of tiny choices over time. Doing one small selfish act isn’t going to define who are, just like helping an elderly person cross the street won’t magically turn you into Mother Theresa.
However, by habitually making tiny choices, good or bad, you will be setting yourself down a path, and it eventually does define who you are.
Which side of the line do you want to be on? Where you are on that scale determines how people interact with you, or even if they want to interact with you. We’ve already talked about the importance of relationships as it pertains to a developer.
What does this have to do with software development?
The whole concept of making the world better each day can be applied to the code you write as well.
We’re talking about reducing technical debt. The accumulation of sub-optimal choices over time that ends up slowing down new development as you constantly have to work around and impedes progress of new features.
Why does technical debt happen?
Technical debt happens for many reasons:
- Tight deadlines forcing developers to make short cuts
- Changing requirements near a deadline
- Inexperienced programmer with a poor understanding of the business domain or development tools
- Rapid prototyping to meet an aggressive deadline to get a product to market.
What can you do about technical debt?
Whatever your task or new feature, leave the surrounding code in better shape than you found it.
Basically any task involves modifying existing code, so spend a few minutes and do something small to make things just a tiny bit better.
- Rename a variable or class to give it more meaningful context
- Write a single test outside of your feature / task
- Add some documentation (I know, right?!?!)
- Do some minor refactoring (make sure you have tests if you do this)
Or just have a conversation and make your team just a tiny bit better.
- Show another developer a new technique that they’re not familiar with
- Tell someone they did a great job on something
- Ask for ideas for an alternate solution to what you were planning to implement
It’s not rocket science, it’s just tiny choices. You don’t really even have to get out of your comfort zone, just take a minute and make a deliberate decision to make something better.
Your future self will thank you, and the world may even throw a little karma your way too.
Thanks for visiting!
If you enjoyed this article, please subscribe to my newsletter below and I'll make sure you are notified of any future articles
As a thank you for signing up, you will receive my free ebook - Iterative Development for the Human Condition. This book takes a look at how the same principles used in software development can be used to effect positive changes at a personal level.[nm-mc-form fid="1"]