Comments by "Ton Bong" (@tongobong1) on "How Senior Programmers ACTUALLY Write Code" video.

Yes there is too much Yagni - "You aint gona need it" in so many object oriented projects...
4
On the other hand there is another terrible metric - the 100% or close to 100% of code coverage by unit tests that promotes writing terrible unit tests that are bad for the project.
4
Yes and it is interesting that despite it always bites them back they seem to never learn how important is the quality of code.
3
@carveratutube all programmers are bad at estimating because it is hard to estimate the exploration since you never know what exactly you will uncover. Just give some reasonable number with some buffer time and if you fail to finish till the deadline then tell your boss why and ask for some more time and relax. If your boss doesn't understand the programming business and why estimating is so hard then this is his problem and if you get fired for that then this is good for you since your boss is clearly a moron.
3
@nickbarton3191 time and also the right directions. I know few developers that didn't improve much in the last 10 years and while they have 25+ professional experience they are still rather bad at refactoring...
2
@lilis969 You should relax at your job and only rarely work for more than 8 hours and never work on the weekends. If you fail to deliver just say that you need more time. I am a programmer-contractor and I earn far more than employed programmers so customers expect more from me and they can dismiss me anytime they want and yet I almost never work more than 8 hours also because if they want me to work after hours I charge them double. I just think this is my output and if you are not satisfied then you can end my contract and I will have holidays and then I will find a new contract job - a new adventure.
2
The best programmers are those that can write a really good unit tests and there are very few of them. Writing good unit tests on top of cleaning the production code by refactoring to make the code even easier and faster to understand and change because unit tests help us with that even more than the clean code.
1
@l00k4tstuff you should always refactor your code to make it clean and you do it not for efficiency but for readability so next time you or some other programmer will have to change you will understand it faster and you will make the change faster.
1
Development is also explorative work so you never truly know the problem-solution space until you implement it and then refactor it and then you find ideas how to improve it... Only after many iterations you truly grasp the problem and solutions and rarely you know it before you even start to write the code.
1
@nickbarton3191 There are many problems with TDD that we don't hear about. This is why very few developers are using it IMO The problems are that TDD is not applicable to every code, it is hard to write the test before the code especially when we are exploring the problem-solution space, it is hard to mentally switch between the problem of writing unit test and developing new functionality in production code... For most developers it is better to write unit test after they write production code.
1
@carveratutube Wow you are the first developer that I met who is good at estimating so you shouldn't have any trouble explaining your management that everything is completed right?
1