The post isn’t claiming perfection. It’s claiming production ready. Very different things.

The confusion there is the claim that good/perfect means done. It means ready for use and extensible.

Note: I’m not agreeing/disagreeing with the claim. Just clarifying the point

I’d bet it’s less simple input sanitizing and more 2 mistakes made separately because they don’t know any better.

1. The input field converting everything to a string indiscriminately
2. Because they did 1, converting everything back to the assumed type

If the front end Dev makes the first mistake, null would be sent in the body as “null”. Then on the backend, somebody might even be binding the variables correctly, but before hand realizing they have to deal with the market and rather than just have a conversation undoes it in their own code.

I’m not going to tell you you shouldn’t do that, I think everybody else has done enough telling others what to do. I’ll try to focus more on what you’d need to accomplish and why what you’re asking hasn’t been done.

Building an OS involves a lot of complex work using very low level calls. The easiest way to think about it, IMO, is that whatever language you use needs to be able to communicate directly with the hardware without any abstraction between the code and the hardware after it’s compiled.

Basic Python, out of the box, requires multiple levels of abstraction to run.

(I’m simplifying here) You write code which is run through an interpreter. The interpreter is a compiled application that translates Python into code the operating system can understand. Then the operating system translates that to calls the hardware can understand.

In that process, the python code is translated to byte code, assembly, and machine code. The Python virtual machine handles memory management for you. It also handles some processing concepts for you.

You’d need to start by finding (or inventing) a solution that compiles Python to assembly without the need of an interpreter or OS in between you and the hardware. It’s worth noting here that Python itself isn’t even fully written in Python and is instead written largely in C because Python isn’t a compiled language. You’d then need to extend Python with the ability to completely manage memory and processor threads without the VM. You’d need to do that because that’s really the main purpose of an operating system.

Something we learn in programming is choosing the right tool for the job. Python isn’t a great option for this type of project because the requirements just to get to where you can start are so high that it’s not really considered worth while. Is it possible, yes, in theory. But without the python interpreter and VM, you’d have to ask if you’re really developing Python or something else that just uses pythons syntax.

Not sure if you’re suggesting that it’s a problem of knowing the language or sarcastically saying that Node.js allows for developers to not know what’s happening.

On the case that you’re thinking it’s a knowledge of the language issue, that’s not what I’m getting at. Typically, what I see with full stack developers is an over reliance on frameworks to do the heavy lifting to the detriment is their skill sets. Often not knowing how to optimize DB queries or trouble shoot performance problems. This works fine in purely CRUD use cases, but falls apart when scaling using more complex patterns starts to occur. I’ve spoken with Sr and staff full stack developers that truly believe the only thing you need to do in order to scale a web app is add nodes.

I’ve worked with my fair share that were front end devs that didn’t understand the backend, too

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

Different user here.

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

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.