My issue isn’t any particular language but the advocates of various languages treating their language as the best hammer for every nail.

I only do that when the problem space is interesting.

Most developers are just implementing CRUD using a framework that does most of the work. There isn’t the interest motivation to keep on trying to fix things.

Different user here.

My only criteria for a backend language is it tells me something went wrong and where. Hence my distaste for JS.

Some things we would want to install aren’t in the official repos. Downloading the deb file is a solution to that for newer users.

It’s not attitude they are giving you. It’s strong recommendation. It’s the strong recommendation of the entire Linux community.

Sudo is different than run as admin and is not intended to be used to do things the way Windows does them.

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

Windows reports using binary and continues to use the Greek terms. Windows is still the holder of largest market share for PC operating systems.

This is such a weird take to me. We don’t even colloquially discuss computer storage in terms of 1000.

The Greek terms were used from the beginning of computing and the new terms of kibi and mebi (etc.) were only added in 1998 when Members it the IEC got upset. But despite that, most personal computers still report in the binary way. The decimal is only used on boxes for marketing terms.

Many organizations vendor packages in the repo for a number of different reasons and languages. Not just for node.

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.

Don’t worry. They’ll change it again next week.

I don’t know that I agree with this for anything but GPUs. There are plenty of distros that are stable and don’t require constant fiddling.

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.

That makes it sound more like it is Linux, but not GNU. Which is accurate

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.