> Command-line tools should print colorized output. Just add a "colorless" command line argument if you need to parse things without ASCII color codes. Better

> Command-line tools should print colorized output. Just add a "colorless" command line argument if you need to parse things without ASCII color codes. Better yet, detect when the program is outputting to a pipe and disable colorized output, e.g. like Git https://unix.stackexchange.com/a/19320 https://unix.stackexchange.com/a/19320 > They will use lots of math in their career. The validity of this is highly domain-specific. > 'git' and 'GitHub' are synonymous. Aside from GitHub-a-likes (e.g. GitLab, BitBucket), what does this mean? I'm assuming that it's that you can use Git by its original use pattern (i.e. without a "single-source-of-truth-plus-issue-tracker-as-a-service" system and more as a "true" DVCS) but very few projects seem to really use it this way. They're important projects, sure (e.g. Linux) but they are few in number. > Sprinkling printf statements is an efficient debugging technique. This is...opinionated. As useful as GDB can be in a pinch I have often preferred to just output things to console. `printf` specifically is a bad example, as C doesn't have reflective abilities (out of the box, anyway), making debug-by-manual-print harder. > Compiler warnings can be ignored, as they'd be errors otherwise. I smell a Golang programmer... > Using lambda in Python is a good idea because it shows others you have a CS degree and understand the "Lambda Calculus". Kinda rolling my eyes at this one. Yes one can "be annoying" with FP-like concepts but lambdas can be very useful in a pinch. >Object-oriented programming is the best and most common programming paradigm. >Using a custom written Vector class makes your program object-oriented. I feel I should add my personal falsehood: "State objects with methods means your program is object-oriented."