7 ms·

A brief history of programming: 1. Punch cards -> Assembly languages 2. Assembly languages -> Compiled languages 3. Compiled languages -> Interpreted languag

A brief history of programming: 1. Punch cards -> Assembly languages 2. Assembly languages -> Compiled languages 3. Compiled languages -> Interpreted languages 4. Interpreted languages -> Agentic LLM prompting I've tried the latest and greatest agentic CLI and toolings with the public SOTA models. I think this is a productivity jump equivalent to maybe punch cards -> compiled languages, and that's it. Something like a 40% increase, but nowhere close to exponential.

defrost 8mo ago
1. Punch cards -> Assembly languages Err, in my direct experience it was Punch Cards -> FORTAN Here, for example, is the Punch Card for a single FORTRAN statement: https://en.wikipedia.org/wiki/File:FortranCardPROJ039.agr.jpg https://en.wikipedia.org/wiki/File:FortranCardPROJ039.agr.jp... PunchCards were an input technology, they were in no way limited to either assembley languages or to FORTRAN. You might be thinking of programming in assembly via switch flipping or plug jacking.
- asadotzler 8mo ago
  They're simply bluffing, and you called them on it. Thanks for your service. Too many people think they can just bullshit and bluff their way along and need to be taken down a peg, or for repeat offenders, shunned and ostracized.
ThrowawayR2 8mo ago
Except punch cards are a data storage format, not a language. Some of the the earliest computers were programmed by plugboard ( https://en.wikipedia.org/wiki/Plugboard#Early_computers https://en.wikipedia.org/wiki/Plugboard#Early_computers ) so that might be thought of as a precursor to machine language / assembly language. And compiled and interpreted languages evolved alongside each other in the 1950s-1970s.
PunchyHamster 8mo ago
That's jump if you are a junior. It falls down hard for the seniors doing more complex stuff. I'm also reminding that we tried whole "make it look like human language" with COBOL and it turned out that language wasn't a bottleneck, the ability of people to specify exactly what they want was the bottleneck. Once you have exact spec, even writing code on your own isn't all that hard but extracting that from stakeolders have always been the harder part of the programming.

defrost 8mo ago

1. Punch cards -> Assembly languages Err, in my direct experience it was Punch Cards -> FORTAN Here, for example, is the Punch Card for a single FORTRAN statement: https://en.wikipedia.org/wiki/File:FortranCardPROJ039.agr.jpg https://en.wikipedia.org/wiki/File:FortranCardPROJ039.agr.jp... PunchCards were an input technology, they were in no way limited to either assembley languages or to FORTRAN. You might be thinking of programming in assembly via switch flipping or plug jacking.

asadotzler 8mo ago
They're simply bluffing, and you called them on it. Thanks for your service. Too many people think they can just bullshit and bluff their way along and need to be taken down a peg, or for repeat offenders, shunned and ostracized.

ThrowawayR2 8mo ago

Except punch cards are a data storage format, not a language. Some of the the earliest computers were programmed by plugboard ( https://en.wikipedia.org/wiki/Plugboard#Early_computers https://en.wikipedia.org/wiki/Plugboard#Early_computers ) so that might be thought of as a precursor to machine language / assembly language. And compiled and interpreted languages evolved alongside each other in the 1950s-1970s.

PunchyHamster 8mo ago

That's jump if you are a junior. It falls down hard for the seniors doing more complex stuff. I'm also reminding that we tried whole "make it look like human language" with COBOL and it turned out that language wasn't a bottleneck, the ability of people to specify exactly what they want was the bottleneck. Once you have exact spec, even writing code on your own isn't all that hard but extracting that from stakeolders have always been the harder part of the programming.