[HN Gopher] 60 Terrible Tips for a C++ Developer
___________________________________________________________________
60 Terrible Tips for a C++ Developer
Author : signa11
Score : 6 points
Date : 2023-09-30 21:20 UTC (1 hours ago)
(HTM) web link (www.modernescpp.com)
(TXT) w3m dump (www.modernescpp.com)
| jokoon wrote:
| I started a job in startup, c++ and qt.
|
| Again, I'm being asked to just read and execute the code step by
| step to understand it.
|
| Important parts are uncommented, I don't think there are tests.
|
| Talked about good coding practices on my one month review to make
| it easier for new employees and the future of the software.
|
| I get that reading the code is what developers should do, but why
| not help others and make it easier? Even I add comments so that
| future me can remember how it works.
|
| I remember emitting the idea of building a tool to calculate an
| opinionated code quality score on irc, I got mocked. If your
| codebase is low quality either hire people to refactor it or
| rewrite it.
|
| Bad codebase don't deserve developers in my view.
| mindfulmark wrote:
| There are a some things in your comment that give me the
| impression that your opinions are too strong for your
| experience. 99% of codebases are bad. It's the baseline
| condition. It's our job everyday to slowly make them better.
| I'm extremely picky about what comments are allowed to make it
| into the codebase since the majority of comments I see are
| wrong, outdated, obvious and riddled with typos. I think it's
| very easy to complain about bad code when really the best thing
| to do is just suck it up and fix things.
___________________________________________________________________
(page generated 2023-09-30 23:01 UTC)