Feels like we're heading towards a world where computer languages disappear, and we just use human language to tell machines what to do. Kinda like how typewriters got replaced by computers in the 80s. Back then, people spent so much time making sure there were no typos, they'd lose focus on the actual story they were trying to write. Same thing's happening now with code. We waste so much time dealing with syntax, fi…
> Back then, people spent so much time making sure there were no typos, they'd lose focus on the actual story they were trying to write. Were you a published author in the 80s? Because I highly doubt this was how writers in 80s thought of their job.
I want to be a Journey Programmer Again
41–50 of 79 posts
Re: I want to be a Journey Programmer Again
#42Earlier quoted context omitted.
> Back then, people spent so much time making sure there were no typos, they'd lose focus on the actual story they were trying to write. Were you a published author in the 80s? Because I highly doubt this was how writers in 80s thought of their job.
No, but I've studied the history of computers and keyboards. There's plenty of evidence that writing with typewriters was much slower than using a computer. Writers were also more limited creatively, since they couldn't easily edit or move things around once the page was written.
This is even enhanced when you create a superficial barrier such as writing in all caps.
Re: I want to be a Journey Programmer Again
#43Earlier quoted context omitted.
Perhaps solving the real problem implies using programming languages?
Or perhaps it doesn't. An architect also solves a real problem, even though he's not laying brick.
I think that in programming we will still have to understand the builder's execution, which should remain deterministic, hopefully not at the level of assembly.
Re: I want to be a Journey Programmer Again
#44Feels like we're heading towards a world where computer languages disappear, and we just use human language to tell machines what to do. Kinda like how typewriters got replaced by computers in the 80s. Back then, people spent so much time making sure there were no typos, they'd lose focus on the actual story they were trying to write. Same thing's happening now with code. We waste so much time dealing with syntax, fi…
As much as I'm finding LLMs incredibly useful, this "world where computer languages disappear" doesn't resonate with me at all. I have yet to see any workflows where the computer language is no longer a critical piece of the puzzle, or even significantly diminished in importance. I think there is an important difference between LLM-interpreted English, and compiler-emitted Assembly, which is determinism. The reason w…
Originally I thought LLMs would add a new abstraction layer, like C++ -> PHP, but now I think we will begin replacing swaths of "logically knowable" processes one by one, with dynamic and robust interfaces. In other words, LLMs, if working under the right restrictions, will add a new layer of libraries.
A library for auth, a library for form inputs, etc. Extensible in every way with easy translation between languages. And you can always dig into the code of a library, but mostly they just work as-is. LLMs thrive with structure, so I think the real nexy wave will be adding various structures on top of general LLMs to achieve this.
Re: I want to be a Journey Programmer Again
#45Earlier quoted context omitted.
Perhaps solving the real problem implies using programming languages?
Or perhaps it doesn't. An architect also solves a real problem, even though he's not laying brick.
Re: I want to be a Journey Programmer Again
#46Re: I want to be a Journey Programmer Again
#47So I look at tools like LLMs as just the latest incarnation of tools to reduce the number of hours the human has to spend to get to the end.
When I very first started programming, a very long time ago, the programmer actually had to consider where in memory, like at what physical address, things were. Then tools came along and it’s not a thing. You were not a programmer unless you knew all about sorting and the many algorithms and tradeoffs involved. Now people call sort() and it’s fine. Now we have LLMs. For some things people think they’re great. Me personally I have not found utility in them yet (mostly because I don’t work on web, front end, or in python) but I can see the potential. But dynamic loaders and sort() didn’t replace me, I’m sure LLMs won’t either, and I’ll be grateful if it helps me get to the end with less time invested.
Re: I want to be a Journey Programmer Again
#48Feels like we're heading towards a world where computer languages disappear, and we just use human language to tell machines what to do. Kinda like how typewriters got replaced by computers in the 80s. Back then, people spent so much time making sure there were no typos, they'd lose focus on the actual story they were trying to write. Same thing's happening now with code. We waste so much time dealing with syntax, fi…
Re: I want to be a Journey Programmer Again
#49Does this not just prove how much the software industry has ignored building "boring" libraries for decades? Why do we want this stuff to be written by AI?
Re: I want to be a Journey Programmer Again
#50Let me share a problem I solved recently (well, a year ago god I'm getting old)! I had to write this template loader for my space sim... reference resolution, type mapping, and YAML parsing. This isn't the code I wanted to write. The code I wanted to write was behavior trees for AI traders, I'm playing with an idea where successful traders can combine behavior trees yada yada, fun side project. But before I could tou…
OP here, I whipped this up in like 10 minutes after modelling the problem from a new perspective (I want to be less of a perfectionist with my blogs) so there are definitely grey areas I didn't consider/cover. I do think LLMs can be good for certain boilerplate code whilst still allowing you to enjoy the problems you care about, and as far as my binary definitions this is more of a grey area. I guess for me, this has…