Test first? How do I test something that is not yet written? And before all, why? It makes no sense.
Try it a few times and you’ll see how powerful it is!
Open–closed principle? The more I close my code to modification, the more closed it gets for extention. You can’t have both. It makes no sense.
Only until you realize that it’s actually possible – with interfaces or other dependency inversion techniques.
The best code comment is the one that never existed? Comments are the only thing that allows me to navigate my messy code. You want me to stop writing them? It makes no sense.
Yes, stop writing comments and delete all of them. But only after you clean up the code to the extent that comments are not needed. There are ways to do it.
If you want to be a good communicator, you should practice communication. This requires feedback and questions from your recipients make great feedback. You don’t have to ask anybody for anything extra – questions happen anyway.
You write something -> by the hardness of communication, you aren’t sure if it’s clear or not -> somebody is indeed unclear on something -> they ask for clarification -> you answer, then you improve for future
How to use questions as feedback?
In the previous post, you could learn why visibility is extremely important in IT. If you’re still missing ideas on how to achieve better visibility, read this post. I present you 9 concepts of how you can increase visibility in a typical programming project.
Have you wondered how to effectively communicate in IT?
Make it visible. Extremely visible.
Professional, technical communication is one of my soft spots in software development. It’s useful in situations like code review, status update, standups, meetings, backlog refinement…
Check this post if you’re looking for tips on how to improve your everyday communication.
Check out also part 1 – 10 communication quick wins for developers.
My recent discovery about learning.
So, the reviewer made some comments on a code review and what? Is it clear to your team what happens afterward?
I might be the only developer in my company enjoying code reviews (from both sides, actually). On reflection, the main reason for that is that they make a great opportunity to learn something new. Which is cool, even if it’s someone else’s point of view on programming.
People are so excited about working remotely.
My experience is 4 month of working remotely on daily basis a few years ago, plus an occasional home office for the last 2 years. It’s enough to realize that it’s not my thing. At least when speaking about working from home, which doesn’t exhaust the possibilities.