I've worked with "developers that can't code". One example was an external contractor who, according to their CV, had multiple years experience with programming in C. The person was tasked to fix some errors in our code…
There should be naming guidelines just like how a team should have style guidelines. The discussions should happen when creating (or updating) these guidelines. Then these guidelines should be followed, no need for long…
Pretty much spot-on.
My current company seems to apply the following variation of the motto: Move slow, break things anyway, disable tests to hide it. Yeah, I've quit.
I've recently got a Xiaomi one myself. Will look into these ressources, thanks.
Depending on what version of C you are using, there are no "boolean" values. X != Y returns an integer value, no "implicit cast" required for &.
I've worked with "developers that can't code". One example was an external contractor who, according to their CV, had multiple years experience with programming in C. The person was tasked to fix some errors in our code…
There should be naming guidelines just like how a team should have style guidelines. The discussions should happen when creating (or updating) these guidelines. Then these guidelines should be followed, no need for long…
Pretty much spot-on.
My current company seems to apply the following variation of the motto: Move slow, break things anyway, disable tests to hide it. Yeah, I've quit.
I've recently got a Xiaomi one myself. Will look into these ressources, thanks.
Depending on what version of C you are using, there are no "boolean" values. X != Y returns an integer value, no "implicit cast" required for &.