|
|
|
|
|
|
by miningape
597 days ago
|
|
|
> You can do most of the things the author showed with your craftfully set-up IDE and magic tricks, but that's not the point. Wrong you can do most of the things the author showed with a fresh install of vim/emacs or by logging in to a fresh install of vscode/intellij - In other words no lifetime was spent on this, I like having as bare an experience as possible so I can use the same setup on any computer. > I don't want to spend a lifetime setting up these things only to break when moving to another language. Editor configs don't break across languages? > For the chat and editing, I've gotten a pretty good sense as to when I can expect the model to give me a correct completion (all required info in context or something relatively generic). For everything else I will just sit down and do it myself, because I can always _choose_ to do so. Just use it for when it suits you and don't for when it doesn't. That's it. A lot of people don't have this level of wisdom or the skills to pick and continue without AI. Would I be wrong for assuming you've been programming for at least 10 years? I don't think AI is bad for a senior who has already earned their scars, but for a junior/no skill developer it stunts their growth simply because the do expect the model to give them a correct completion, and the thought/action of doing it without an AI is painful (because they lack the requisite skills) so they avoid it. |
|
|
Sure, though, for example, I haven't a clue for the shortcut for wrapping an expression in a try/catch block. With Cursor I just press tab and it often also adds a useful print or other useful expression inside the catch block. It comes down to requiring less discoverability.
> A lot of people don't have this level of wisdom or the skills to pick and continue without AI.
I have been coding for some time, but I think you underestimate people's BS detector. People are well aware that language models hallucinate. Most of the time you'll figure it out soon enough (compiler/run time) and adapt accordingly. I have learned much of my coding through reading public repositories/code which were also not always up to standards. You figure this out by banging your head once or twice.