And that’s kind of decision making is what’s important. More often than not, you ask someone to explain their decision making in building a feature, and what you get is “I don’t know really”. And the truth is that they have externalized their thinking.
I think there’s a factor of speed there, not a factor of insight or knowledge. If all you have is ‘ed’ and a printer, then I think most of the time you will spend is with the printout. ‘vi’ eliminates the printout and the tediousness of going back and forth.
Same with more advanced editors and IDEs. They help with tediousness, which can hinders insight, but does not help it if you do not have the foundation.
A small but silly one: breaking middle and right click functionality for links.
An auction site I use loads in the list of auctions after the rest of the page loads in, and also doesn't let you open links with middle click or right click>new tab, because the anchor elements don't have href attributes. So that site is a double-dose of having to open auctions in the same tab, then going back to the list page and losing my place in the list of auctions due to the late load-in and failure to save my scroll ___location.
I would submit this as product feedback if you haven't. One of my favorite things as a dev working on client-facing things is when I get negative feedback that presumably has a pretty easy fix to at least part of it ("add 'href' to these links") where I can pretty quickly make someone's life a little easier.
This is not exclusive with an SPA. Even MPAs/SSR apps can have this issue. But I guess MPAs are probably not built with post load interactivity in mind and maybe that's why its less prevalent there.
This issue doesn't get enough attention; apart from the obvious implications on bad UX, I find myself losing interest in a project after realising its broken in so many subtle and non-subtle ways due to the underlying tech. I, like many others, got into programming due to the joy of creating something beautiful and attempting to follow (influencer led) JS trends nearly killed my interest in this field at a time.
Yeah. I don't care for vibe-coding on your personal project, but I would absolutely mind reviewing a PR and finding afterwards you don't have any idea of how the code works, so you can't answer any question.
I wonder how well they do for Go and Java. The first is a boring language where there's little to none chance to stray from the default. The second is verbose, but with strict rules on the syntax.
They are fine with Go. Not with whole codebases but libraries/functions around a thousand lines of code are written perfectly with tests (Although, I always say, never let the LLM write the tests AND the code, or at least write your own tests in addition to what it generates).
> Learning about `git rev-parse` through documentation and learning about `git rev-parse` through AI fundamentally have the same outcome at the end of the day: you have learned how to use `git rev-parse`.
Maybe. But anytime I take on the task to automate something, it was a nice opportunity to check how others do it, what other things the program can accomplish.
The decision to automate is already done, no need to rush through it.
My best workflow to date is to generate snippet of code when you know a lot of the ___domain, but don’t want to go through the docs. Especially with languages like python. Even then, you get nonsensical stuff. But it can be great for quickly locating source material in the docs. Kinda like looking at a reference implementation to get the technique.
But it is slower than someone that is knowledgeable about the library and languages unless you don’t care about correctness.
reply