Do you not have the browser open all the time? Not necessarily in the foreground, but at least in the background I always have a browser window. But tbh, most of the time it’s in the foreground on the second monitor

Also then there are Jour Fixes and standups for the side projects you got rented out too and and and

But it’s also important to learn that comments should be brief and concise. We have one file from an ex-dev in which there are 750 lines of code and 2000 lines of comment, when someone wants to maintain this code they always have a hard time because this many comments are taking up so much screen real estate that you can’t find the code that actually does stuff

A colleague of mine has one. They are easy to overlook and he sometimes has pretty bad looking crashes (from the outside) but the chassis themselfs are extremely sturdy and protecting. He slid down a road 25m at one point, crashing into a pole, but only got a bruise from it. Because, and that’s the main point: these things are not going down 50mph, they are at 18mph and the only dangerous parts are intersections where cars are slower anyways

The problem is that a lot of people don’t understand when to ignore the rules and just stick with them forever.

We had a developer once that always said KISS KISS KISS whenever we pointed out that her functions are working but not reusable, so she wrote 20 functions that all did the same thing, but with slightly different parameters. And that’s just one of the examples