Re:Times are great for programmers now. How does it end?
by galaxyLogic on Monday February 21, 2022 @02:33AM
(#30412878)
I much agree with that the complexity is the limiting factor and you probably will need specialized people to model and design not only what the computer does but how the humans and computer co-operate. When you're programming you are not only programming the computer but also the people who use your application(s).
Describing and designing and validating asynchronous processes is especially complicated.
Re:Times are great for programmers now. How does it end?
by jug on Monday February 21, 2022 @04:58AM
(#30413844)
Yes, at least at scale, BASIC is hard!
It's a wolf in disguise due to all the "easy" English words, words that of course need to be put in the correct, often grammar-violating order so that nothing is won anyway, for the compiler to make sense of the instructions and intent. You end up getting a language design that places more importance on a bastardized form of English like a text-based adventure game, rather than being a good map to the problem space that doesn't get in the way like a bumbling fool.
Re:Times are great for programmers now. How does it end?
by JohnBooty on Monday February 21, 2022 @11:19AM
(#30417502)
Yeah. I cannot believe that the "describe things to the computer in English" fantasy exists in 2022. At least from folks within the industry; it makes sense for laypeople to ponder it.
Re:Times are great for programmers now. How does it end?
by mihaigalos on Monday February 21, 2022 @04:10AM
(#30413516)
beautiful sum up!
Same with Visual Basic. No more application developers. Just drag and drop!
You might ask yourself why VB6 or Delphi didn't simply rule the world forever. We had those ~25 years ago and with those tools, non-engineers could drag and drop their client/server database-CRUD apps together. Hell, you could do most of that stuff in FoxPro or dBase even earlier, minus the GUI.
You're fantasizing away the enormous middle ground of development work that lies between "hardcore computer science-y stuff" and "things non-engineers are able and willing to accomplish."The "plain English" bit is hilarious. Human languages are extremely imprecise. That's why we have specialized "languages" for lots of things: math, music, etc. Maybe you are living in another universe where AppleScript took over, I don't know.
Ask yourself if "plain English" tools have replaced engineers in other specialized disciplines. Can I tell my keyboard to write me a song in "plain English?" Can I design an airplane in "plain English?" Can I build a bridge in "plain English?"
Sure, only a small % of work requires low-level languages, or knowledge of how a CPU works.But the bottom line is, somebody needs to describe complex processes to the computer in a very precise way that handles lots of edge cases, filthy data, errors, etc.
At some point, somebody has to write that logic and if there's more than one person doing it they'll need a development pipeline of some sort. And they'll need to do it in a maintainable and scalable way.
The tools are generally not the limiting factors here. You could replace Javascript and Python and Ruby with world's friendliest, code-free GUIs but you'd still have to describe those processes in an equal amount of detail and do it in equally maintainable and scalable ways, and I doubt it would be as terse or as expressive as the aforementioned languages.
I am not denying the power of these tools. However, I see these more as "opening up new avenues" as opposed to "eliminating the need for all kinds of nitty gritty development work that actually makes businesses go."Drag and drop all the sweet zero-code shit together you want in Unreal Engine; somebody has still got to sanitize and massage the weirdo sometimes-broken JSON that our partner's API likes to return sometimes and handle the error states when it can't be fixed.