Engineers spend countless hours dealing with syntax, typos, indentation, linting, errors, arguing over style and best practices, and making shortcuts to try to coax some of the code to type itself. It’s absurd. And it’s a waste of time.
Coding Is Over
Lauren Mendoza
2.2K20

Lol. It must be clear to you at this point and after so many replies that the majority of us do not recognize your version of coding. Like somebody said, have you ever heard of an IDE?* Are you still coding in Notepad++, because we all know people like that, we just don’t particularly like them.

But the problem you are trying to address os actually this, right?

Thousands of CRUD apps have already been built. We’ve already solved that problem. But for some reason, we’re still building more of the same apps, mostly from scratch.

No, we are not building the same apps. Whenever people spend money on building a new app, they do this thing first where they look on the market for apps with enough of the features they want and not too many of the features they don’t need, and only after that do they spend like hundreds of thousands of dollars, sometimes millions, on a team of engineers. And if the problem only requires some clicking and dragging, it will not ever earn the “grossly overpaid” salaries you are referring to. I personally have not worked on the same kind of app twice, even though I have my own niche. The problem you are identifying doesn’t exist.

We should be throwing data into a pile and databases should organize and optimize themselves using machine learning and other buzzwords. People should not be writing database schemas, because we inevitably get it wrong. Database design is an optimization algorithm, not an area of engineering.

No. Like, 100x no. The problem with data is not the wrong database design, it’s that there is too much of it and too little manpower to sort through it, which is why the NSA is so comically ineffective. Look at how Netflix solved the data problem — by throwing people at it! There are things that people are good at and that machines are terrible at, and this is a classic case.

Also, lol at calling machine learning a buzzword. Is that all machine learning is to you?

Software engineers are grossly overpaid, and many (I) feel entitled to the money and benefits they (I) enjoy. In reality, software engineers are not smarter or better than any other type of worker. With the death of coding, diversity will increase. Engineering will reflect the rest of society, rather than favoring a very small and socioeconomically exclusive subset of people.

Wow. I feel entitled to a decent wage and some benefits, how privileged. Stay woke.

And how is diversity a goal when you are in fact proposing an expansion of the underclass? You know those socioeconomically advantaged people are just going to move up to better jobs, right? And you know the reason why jobs like nursing and teaching are so “diverse” is because they are devalued, not that engineering is overvalued, right?

And software companies are ALREADY employing vastly fewer people than other companies of comparable size and revenue. Automating more coding is merely going to decrease the number of available jobs.

Fyi, throwing a progressive sheen on your dumb idea is not going to make it less dumb.

Finally, speaking as somebody who regularly works with Winforms and C#: clicking and dragging will not save us. Have you ever tried to read machine generated code? They are 7K lines monstrosities that put to shame any buggy piece of shit C program out there, and anything less complicated is just not going to cut it. Who is going to troubleshoot that, once something goes wrong — because trust me, something always goes wrong, mostly with user error, human user error, you know, which is not going to be abstracted away.

And fully half of this industry and the research already goes to “building tools for building tools for building tools” anyway.

*Before some white knight accuses me of sexism yes, I am a woman.