3 ms·

Not by that definition, I'm not. Look, I get that you're trying to cleverly put in a bunch of rules that "make a good programmer", but rules do not the master

Not by that definition, I'm not. Look, I get that you're trying to cleverly put in a bunch of rules that "make a good programmer", but rules do not the master make. A master knows the best practices and rules, knows why they apply, and knows where their usefulness ends. Many of the properties here range from naive to downright dangerous. Example: - "A lazy programmer do not deploy in production, they instruct Jenkins to do that. Therefore a lazy programmer is not afraid of deploying on Friday afternoon." Using a tool to deploy does not remove all of the risks of deployment. If you deploy on Fridays, you WILL eventually be there on Saturday fixing a problem. - "A lazy programmer is a master of delegation. After they delegated a task, they immeditaly forget about it." Also very bad advice. Forgetting about a delegated task removes you from the chain of responsibility. If you're delegating, it's on YOU to follow up. Otherwise things get lost in the chaos. I'm not going to run through all of them. Please just disregard this site and take lists of "a good programmer does..." as a red flag for the company promoting it. A good engineer is not made through lists and rules. If it were that easy, we'd all be good engineers.

ipaddr 6y ago
Your countpoints are solid advice for a good programmer. For a great programmer you are missing that they control the environment as well. If you know who you are delegating to you know what will be returned, when and how that is going to affect the next step. As a great programmer you are 15 moves ahead. Why would you worry about chaos? There is a lack of trust in your plan if fear of chaos exists. You are Michael Jordan and can see the entire court. As an average developer I don't trust anything will work even if it was just tested.
gabereiser 6y ago
Upvoted because every counter point presented was on target and with solid examples. The article for me read a little tongue in cheek but there are some serious errs in reasoning for some of these. Just toxic behavior.
athrowaway3z 6y ago
If i had to take a cynical guess, this was written by someone who thought: "Programmers respect laziness ( See Bill Gates quote ). So attaching my beliefs to the idea of a 'lazy programmer' and putting it on a dedicated domain my virtue signaling has a higher effectiveness" I'm a little sour because apparently "writing a blog" is not hip anymore and we need dedicated domain for every brain fart.
- bckr 6y ago
  Well, it's a marketing page.

ipaddr 6y ago

Your countpoints are solid advice for a good programmer. For a great programmer you are missing that they control the environment as well. If you know who you are delegating to you know what will be returned, when and how that is going to affect the next step. As a great programmer you are 15 moves ahead. Why would you worry about chaos? There is a lack of trust in your plan if fear of chaos exists. You are Michael Jordan and can see the entire court. As an average developer I don't trust anything will work even if it was just tested.

gabereiser 6y ago

Upvoted because every counter point presented was on target and with solid examples. The article for me read a little tongue in cheek but there are some serious errs in reasoning for some of these. Just toxic behavior.

athrowaway3z 6y ago

If i had to take a cynical guess, this was written by someone who thought: "Programmers respect laziness ( See Bill Gates quote ). So attaching my beliefs to the idea of a 'lazy programmer' and putting it on a dedicated domain my virtue signaling has a higher effectiveness" I'm a little sour because apparently "writing a blog" is not hip anymore and we need dedicated domain for every brain fart.

bckr 6y ago
Well, it's a marketing page.