Why though? I've yet to come across an auto formatter that formats things the way I personally like. But that's fine. I do whatever the hell I want until I'm ready to open a PR, then bang it through the auto formatter. And you know what? I can also go the other direction and run a home-brew auto formatter to reshape things the way I personally want on my local machine.
I'd go so far as to argue that person to person differences are helpful to a reader. When I am dealing with a long term code base it's easy to develop a feel for who is responsible for different constructs without needing to rely on the git history. This gives me immediate information on what to expect.
> That's why I like Go, every piece of code looks the same, there's one default enforced linter and this discussion (or discussion if discussion should be allowed or prohibited) doesn't even cross anyones mind
I remember people saying this exact same thing about Python ~20 years ago.
Fair. I'm comparing it to the output I see generated in more mainstream, day to day, languages. I'm not going to bother to get into an argument on if the frontier models can generate amazing code in general.
What I've found is I can get get the frontier models to generate bash scripts, perl one liners, etc that do exactly what I need at roughly the same quality as any other code it generates.
I've seen this too and I get it. However, we should not assume that certain phrases are AI tells. And that was my point. There are all kinds of things I see described here as "AI slop" that are things I just do, and have done, for decades.
It turns out that LLMs are really good at writing bash too. even perl! maybe we should rethink some of these lost bits because we no longer need to worry about the arcane parts.
I definitely saw MU* games with graphics schemes in the 90s, although most of the moment to moment activity happened in standard trulytext base "rooms". For instance there were a series of Battletech MU* games that would replicate cockpit HUDs, the hex maps, and related via ASCII art for you while piloting a mech.
There's a difference between always being hypercholesterolemia as a fit person and being obese and losing a bunch of weight when it comes to these conversations.
It's one f those things where some people's "I can't help it!" claims are true, but many are not. That doesn't invalidate the first category even though most people in the category are in the latter.
Dietary cholesterol has little impact on blood cholesterol. However the post that started this debate mentioned mass loss. And that does have a decent correlation. Go from obese to not obese and the median person's cholesterol will drop quite a bit.
I'm not sure. And to be honest, typing speed was never that big a deal. By the time I got out of college a few decades ago I was in the 110-120wpm range.
However as I progressed in my career as a developer what I found is that both my "working" WPM and then my "normal" WPM dropped over time. Once I moved out of truly junior, pure code grinding roles, I spent more and more time thinking, talking to people, etc than I did typing. At that point, what does it matter if I'm at 20wpm or 200?
Likewise, in day to day life, it's not like I'm sitting there typing a novel. I'm mostly clicking buttons, writing short messages, tweet,s and the like. My day to day typing speed has also decreased. I'm sure it's still up around 80-100wpm, but it's rare that I'm sitting there typing long enough to matter.
Same with LLM. Who cares if it takes me 10 seconds or 20 seconds to type in a prompt, when it's going to sit there and spin for a minute anyways?
Sort of. As a developer I had my stack of reference books, man pages, etc. I’d try hard to memorize syntax as it was a pain to look things up. And I also devoted some memory to remembering where in a book to look, which set of man pages to use, etc
With google that mostly went to the wayside. I just needed to know something existed and I could pull together far more information faster than I was spending before to just do quick lookups
I didn’t say the job was about memorization back then. Rather I found that each of these new abstraction layers made it easier to go broad with one’s on hand knowledge instead of deep
I realized later you likely meant the latter anyways and yeah that's much different. It's important to know what these things are, how they work, and why one would need to tweak them. It was never important to have the syntax on instant recall.
That's fair. This all feels similar to the shift that happened when Google came on to the search scene. To use your example, people realized they no longer needed to memorize syntax. Instead they only needed to ensure they understood the big picture concepts, and they could fill in the blanks on demand with Google. This is all just moving that layer of abstraction one level higher.