Ask a developer to what extent they comment their code and you’ll learn something very quickly about how they approach their work and their team. Very little comments – whoever comes next can fend for themselves, just as I did. Substantive comments – this was very confusing, I don’t want the next person to have to go through all of that again. Commenting your code serves no purpose today, for you. But for the next…
If a Developer on your team says this, it means the following… I have too much on my plate to really think about this. I am hoping this is not a bug. I don’t know enough about the problem to give you a solid answer. The problem with this phrase, is that the developer means it the context of – I’m not 100% sure, but I think we might be able to do something here…
New technology can be a little daunting, especially when you are no longer going greenfield and have to move an existing application to a new platform. But it can be so exciting, so much to learn, so much to understand, so much to try out. And then we pick up the old system and dump it onto the new platform, not changing a thing, leaving it as it were and moving on. We pat ourselves on…
I hear this a lot – “I’ll learn it when I’m given a project that I can learn it on”. Translation – “I’m not going to invest my own time in figuring this out until you tell me I can invest my own time in doing this for you… and pay me for it.” Perhaps not what you were thinking at the time you said that, but you can’t argue with the logic. Would that…
As Developers, there is an all-too familiar trap where we start to become really good at what we do. We start to become really, really good programmers. And with that, we start to code less, because we want to put more effort into design to making sure our code is perfect and beautiful and adapting and pristine and self-healing and and and… So we do more design, then we code, then we write tests, lots…