Learning everything the hard way has made me a natural consultant and mentor. Because I’ve already explored all the wrong paths, I often know someone is stuck before they do, understand what threw them off course, and show them how to get back on track

This really hits home and is something I simply don’t see often in juniors today - a desire to tinker, experiment or ‘play’ to figure out how a problem might be solved. I’m always telling them to allow themselves to struggle for at least an hour or two before asking for help.

Imagine depending on your creditor, who also happens to be your employer, for the very oxygen you breathe. This would be like a company town x1000.

I generally use ‘count’ for a counter and ‘idx’ for index.

I’m not using C or Java languages though - if I were I would probably go with the more classic terse approach.

Also, if I’m reviewing a PR and I have to load more of the diff context to understand what a variable represents, then that variable has the wrong name.

I’m honestly prefer short but (usually) complete words. Somewhere along the line I realized that being explicit really helps when you need to change it later.