4 ms·
He writes: "But my code is bad: This is just ego. The person who spends the most time thinking about you is you, and the person who spends the most time stressi
by wouldbecouldbe 3y ago
He writes:
"But my code is bad: This is just ego. The person who spends the most time thinking about you is you, and the person who spends the most time stressing over your bad code is you as well."
In most places in life this is valid, but in the developer community I disagree. Developers love talking shit about each others code.
Still yearly ritual here to bash the "Clean code" book.
- guappa 3y agoNot true. When I happen to having to fix stuff or have to decode insane json, I curse other developers.
- flurdy 3y agoThe article then also contradicts itself slightly with that for hiring look at their previous public contributions. However, I get their point for both cases. Looking at contributions gives a glimpse of that person. However with a grain of salt. And the imposter syndrome is strong in public contributions. I get it, and agree with the article, don't worry. I am working with a gov client at the moment so back to coding in the open again, and it is great. I am not worried that my quick one-line comment on a PR for a tiny repo is now public. Or pushed typos. It happens.
- tomashubelbauer 3y agoThis sentence goes well with the one at the end of that paragraph: > Toxic community members who complain about bad code instead of making suggestions to improve it are not the people you want in your community anyway. If someone finds your code and goes out of their way just to shit on it, they can get fucked. I'd be handing out blocks for that.