The biggest thing he got wrong is the assumption that it’s good programmers writing libraries.

Human made changes is likely not what caused this image to occur.

111 files with that kind of change count is most likely a dependency update. But could also be that somebody screwed up a merge step somewhere.

None of those things are required but they sure do help.

As a developer, the baby is how I see developers, too.

I’ve had questions like your 3rd bullet point in relation to why somebody’s friend is having trouble with connecting a headset to a TV.

No idea. I don’t know what kind of headset or what kind of TV. They are all different Grandma.

As a senior engineer recently turned manager I hear this type of mentality from most of my junior all the way up to senior devs.

The only thing I’d suggest to you is spend some time digging into the tools you’re building outside of the project you’re working on. Just to get a general understanding of how the pieces fit together. Definitely do it during work hours, though. I’m in no way suggesting outside of work, here. Once you’ve spent enough time digging, you’ll surprise yourself in how effective you get at answering questions.

Fiddle was found in a thrift store. Couldn’t afford the bongos.

I’ve never seen a problem with asking people to code in a live session. It’s about the problems they are asked to solve. Leetcode style problems are generally unrealistic and have little to do with the skills that are actually needed.

If the problems were more focused on the day to day type of work, nobody would complain. “solve x problem without the industry standard library that solves that problem already” is just testing the ability to quickly reinvent wheels.

I see nothing wrong, here.

My furry ass isn’t sysadmin certified and I sit it on the switch without a wristband, keyboard, and laptop daily.

A program that works right but doesn’t solve the problem is also not very useful.

It’s been my experience that the .NET developer will miss the actual statement and take it as an assault on .NET being the best solution for every use case.

I think Python is easy to learn but difficult to get past the basics. I’m also not convinced that getting past the basics is even worth it in three long run. I say this as a person who has used all Python at work for roughly 70 percent of the last 15 years. My current position is moving to Rust and my last 2 positions were moving to Go. Everybody was happier.

This. C# has been losing momentum for years but some people just won’t see it. I think Microsoft trying to move 365 of of it is just another big flag that devs need to start looking elsewhere.

Microsoft has been pretty open that they intend to move to Rust. They are currently re-building the Windows API in Rust as well. I do expect they will try to push .NET in that world which will be a bummer.

It’s that unproductive direction content. It doesn’t. Some people just want to hate things.

It could be a materialized view that is generated off of a weighting where you are nice until you have a certain number of incidents.

Internationalization isn’t about the translation. It’s about not hard coding the strings that display. Putting them somewhere that is easy to swap out would allow users to provide their own if they wanted.

If he’s getting to the first round of technical interviews then it’s likely not a languages issue. That’s the round that many companies put you in front of a mid-level dev who arrogantly asks you a code-kata question and refuses to answer questions. It may be that he’s not inherently good at solving the toy box problems on the spot. That’s the issue I tend to have in these rounds.

Though I guess it could be a languages issue if the mid level dev doesn’t know the language you’re doing the problem in and marks you down for that.

Where is the nearest fire to dump this comment in?

Overall, I think I prefer elixir, but is probably choose go as well.

Not just ease and performance but popularity. I could be happy in only go for the rest of my life. Currently a Rust dev and I don’t know if I can spend the rest of my life with lifetimes. They are an emotional challenge…

It’s only worth it if you’re planning to work in Java or one of the other JVM languages.

If that’s what you are striving for, is worth it to spend the effort ahead of time. If your goal is more agnostic to tech stack, learning Spring Boot won’t be worth it until you land a role that uses it.

It might be worth dipping your toes in the water anyways. But frameworks like that shouldn’t be bothered with without inherent interest or need.

Personally, I’ve no interest in working in Java, Scala, or Kotlin so I’ll skip it.