I agree with your overall sentiment but i have two nitpicks. Ofcourse bad programmers write bad code, but alot of 'good' programmers write bad code aswell. Id say it is a problem with lazy developers, and unlazy developers with lazy/bad days.
I also dont think your sentiment of 'just dont be a halfass developer' is good advice, since it doesnt really provide a solid course of action, and fosters un-original thinking.The only way of learning what is bad/good about certain approaches is trying, failing, learning. This ofcourse assumes that you are not lazy and competent.
I agree with your overall sentiment but i have two nitpicks. Ofcourse bad programmers write bad code, but alot of 'good' programmers write bad code aswell. Id say it is a problem with lazy developers, and unlazy developers with lazy/bad days.
I also dont think your sentiment of 'just dont be a halfass developer' is good advice, since it doesnt really provide a solid course of action, and fosters un-original thinking.The only way of learning what is bad/good about certain approaches is trying, failing, learning. This ofcourse assumes that you are not lazy and competent.