If you write for yourself, whether you use generated text or not, (I am using the text completion on my phone typing this message), the only thing that matters is how it affects you.
Reading and writing are mental processes (with or without advanced technology) that shape our collective mind.
Debugging is harder than writing code. Once the code passed linter, compiler and test, the bugs might be more subtly logical and require more effort and intelligence.
We are all becoming QA of this super automated world.
After passed 50, I started to do non competitive long distance running (jogging). With proper running form, it builds up core muscles and endurance naturally. And I do my coding either standing up or lying down on the couch, avoiding sitting as much as possible.
The Source Code Control System, the first UNIX revision control system, written by Marc J. Rochkind
The remote job entry batch-submission system
The PWB shell, written by John R. Mashey, which preceded Steve Bourne's Bourne shell
The restricted shell (rsh), an option of the PWB shell, used to create widely-available logins for status-checking, trouble-reporting, but made safe by restricting commands
The troff -mm (memorandum) macro package, written by John R. Mashey and Dale W. Smith
Utilities like find, cpio, expr, all three written by Dick Haight, xargs, egrep and fgrep
yacc and lex, which, though not written specifically for PWB, were available outside of Bell Labs for the first time in the PWB distribution
Dynamicland is still going, just quietly. We closed the Oakland space for covid, but Realtalk development and collaborations have continued -- basically as originally planned, if more slowly due to our small size.
I'm hoping to spend the summer working on bionano, and get back to the new Dynamicland website in the fall. It might be ready by the end of 2023? It'll have everything.
I'll try posting at @bret@dynamic.land (currently Mastodon until we have time to do our own thing in Realtalk). (I'd appreciate if you don't ask for my opinions about things.)
From development point of view, workerd would encourage this new nanoservices/lambda/function paradigm because it would be much easier to develop and test in self-hosted environment or even CI/CD pipeline.
I think you might want to change your perspective a little bit and think about what value this system could offer for the problem solvers other than compensate for their time and attention.
(Why would I spend 15 minutes reading your post and writing this comment if I am not getting paid?)
Follow the article and some Googling, I found this VSCode extension. Idea like this might help people (and AI?) read, analyze and build some automation on old COBOL code with modern tool chains.
Reading and writing are mental processes (with or without advanced technology) that shape our collective mind.