Are these the same bike lanes that start and stop randomly and are often just the shoulder of a 45-mi/h road with a bike, and implied middle finger, painted on?

Adult brains, too. I appreciate the study, but this is one of those "yes, obviously" situations for anyone who has ever been outside amongst cars.

It's one of those "yes, obviously" situations that are surprisingly controversial if you mention it in conversation. There are a lot of people (likely the already heavily hearing-damaged) that have zero problem with road noise and are very dismissive of any and all noise concerns.

At soms point I realized people who think noise sensitivity is ridiculous are always either old, partied a lot or are hard of hearing through other means.

Yeah, of course problems you don't have seem silly. At least, for the minimally empathetic.

That’s the best result for a study

To work on the same code base as the rest of my team? Like everyone else. Certainly not to nitpick about how history is written, in what order or what is omitted.

I'm very surprised you've never gone hunting for bugs in your git history.

"Hey something went wrong with X service"

Find commit like "add y to x service'

It's a time saver to me. Plus if the bug is extra tricky, you can ~easily~ revert or pick it out.

I did try when I was a junior. I learned this relies on good commit messages, and the information can be lost during squash. Honestly if I’m playing the role of bug detective I’ve become much faster using other techniques.

"I've found history is useless because people don't maintain good history, so don't bother with maintaining a good history"

Pick something that works != don't bother. But nice attempt at misrepresenting my argument!

How is it supposed to know how you want your errors handled by default? Handling errors is the programmer's job.

There are lots of techniques to make it obvious that errors can happen and need to be handled.

1. Make it difficult to ignore that a function can return an error. This is the golang approach. Errors are part of the return values and unused return values are compiler errors.

2. Make it impossible to use parts of the return value having an error state. Rust does this with the Result sum type and pattern matching.

3. Tailor for the happy-path and throw exceptions in case there are any errors. With optional means to catch them if recovering errors is desired. This is how most other languages function.

Hiding the error status in another variable, that is super easy to overlook and that the programmer might not even know exists, then continuing despite this variable not being checked will inevitably introduce bugs allowing faulty data in your system.

Can't you just install it?

It's not. This is a non-issue. Every web shop is writing bash to twiddle a build script on servers they also manage, which includes the ability to install any package they want.

I never started using python, ruby or node because all of them were a pain to use for me - this was 7-8 years ago, so maybe it has changed a lot. But even 2-3 years ago I had lots of issues just running one python project. Module, not module, pip or not...

Way too confusing, compared to go for example. Or hell, even Java/Kotlin when you use an IDE and it autoconfigures most things.

Not once have I worked anywhere where the people writing shell scripts didn't also control all of the boxen those scripts ran on.

I'm glad you never worked at a bank or an insurance company!

It's tongue in cheek, and he's right. I am a old man Sunos/VMS/Linux admin. Having root used to be my god given right.

However I haven't worked at a company in years that gives anyone access to root anywhere except your own local machine or maybe in rare cases a dev box that is destroyed and rebuilt at will.

That depends on your valuation.