Programmers Aren't People(elliotbonneville.com) |
Programmers Aren't People(elliotbonneville.com) |
While the definition changes, the expertise shifts and with it the field. Computers eventually became statisticians and data scientists. Printers became graphic designers.
What I found most interesting is that when positions undergo such evolution (printer -> graphic designer), a number of skills which were previously different expertise altogether, combine to create a new field. In other words, a new multidisciplinary field is born.
I think a good example is data science, the field at it's core is applied statistics using modern techniques such as data management and computing [0].
The question is, what is the new evolution of a programmer? Lots of folks like to use the term "engineer", and previously I thought this was silly. But now with LLMs, maybe that is a good descriptor; software engineer.
[0] https://www.welcometothejungle.com/en/articles/story-origin-...
The moniker already exists which we need to revive and repurpose for the LLM era;
"Systems Engineer" i.e. one who does Systems Engineering - https://en.wikipedia.org/wiki/Systems_engineering Because the focus is no longer on coding alone but involves specification, verification (formal and testing), traceability and correctness. All using a whole plethora of third-party infrastructure, tools and components.
In the early days there used to be "Systems Analyst" and "Systems Designer" in addition to the above. All of them go together. The Systems Analyst is business requirements facing, The Systems Designer maps it to implementation architecture and The Systems Engineer pulls everything together (including costs/risks/specific implementation technologies etc.) to produce the complete functional system.
See also my previous comments here - https://news.ycombinator.com/item?id=48264680
[1] https://en.wikipedia.org/wiki/Turing_machine
[2] https://en.wikipedia.org/wiki/IP_over_Avian_Carriers
[3] https://www.karriweaver.com/selvagenotes/weaving-computing-t...
Very deepity. But you’ve apparently misunderstood mathematical notation - it’s just a shorthand, nothing stops one from expressing the same concepts in natural language.
> Furthermore, natural language specifications are, at best, wishful thinking.
More deepitism. There are plenty of counterexample to this, your claim only serves to suggest that you have no experience with software development.
> Feed this into a stochastic parrot
To might want to looking for terminology in papers that were published after GPT 3.5 was released, it’ll make you sound less like an Amish person objecting to the “English”. Then again you used “clanker” in another comment, so I don’t hold out much hope.
Amazing how you said that like it made any sense at all.
"Coding is a pseudoscience" makes sense like "plumbing is a pseudoscience" makes sense: Fluid dynamics might be a pseudoscience, but plumbing either works or it doesn't, and it's either maintainable and modifiable or it isn't. Computer Science is what you're groping for, in your speech laden with things you will probably defend as not-slurs but which you're still bizarrely excited to get to use, but outright saying Computer Science is a pseudoscience might make you realize you're talking absolute nonsense.