this post was submitted on 10 Feb 2024
912 points (94.4% liked)
Programmer Humor
19809 readers
1100 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Using an IDE isn't programming either
But I'll definitely prefer hiring someone who does. Sure, you can code in Vi without plugins, but why? Leave your elitism at home. We have deadlines and money to make.
Edit: The discussions I've had about AI here on Lemmy and Hackernews have seriously made me consider asking whether or not the candidate uses AI tools as an interview question, with the only correct answer a variation of "Yes I do".
Boomer seniors scared of new tools is why Oracle is still around. I don't want any of those on my team.
Thinking AI is an upgrade from pencil to pen gives the impression that you spent zero effort incorporating it in your workflow, but still thinking you saw the whole payoff. Feels like watching my Dad using Eclipse for 20 years but never learning anything more complicated than having multiple tabs.
For anyone who wants to augment their coding ability, I recommend reading how GPT (and other LLMs) work: https://writings.stephenwolfram.com/2023/02/what-is-chatgpt-doing-and-why-does-it-work/
With that in mind, work on your prompting skills and give it a shot. Here are some things I've had immense success using GPT for:
I know in advance someone will tunnel vision on that last point and say "this is why AI bad", so I will kindly remind you the alternative is doing the same thing by hand... In weeks instead of days. No, you don't learn significantly more doing it by hand (in fact when accounting for speed, I would argue you learn less).
In general, the biggest tip I have for using LLM models is 1. They're only as smart as you are. Get them to do simple tasks that are time consuming but you can easily verify; 2. They forget and hallucinate a lot. Do not give them more than 100 lines of code per chat session if you require high reliability.
Things I've had immense success using Copilot for (although I cancelled my Copilot subscription last year, I'm going to switch to this when it comes out: https://github.com/carlrobertoh/CodeGPT/pull/333)
One thing I'm not getting into on this comment is licensing/morals, because it's not relevant to the OP. If you have any questions/debate for this info though, I'll read and reply in the morning.
I don't get the downvotes. I've hired probably 30+ engineers over the last 5 or so years, and have been writing code professionally for over 20, and I fully agree with your sentiment.
It's just the general ai hate. It's not surprising, because machine learning is yet another scam area. But for programming you would be a complete fool to ignore copilot mastery since paper after paper proves it has completely revolutionised productivity. And it's not normal to think you will be better than everyone when not using an assistant, it's just the new paradigm. For starters it has made stack overflow be almost obsolete and it was the next most important tool..
I edited the comment to provide actual info, it was originally just the first paragraph
AI’s not bad, it just doesn’t save me time. For quick, simple things, I can do it myself faster than the AI. For more big, complex tasks, I find myself rigorously checking the AI’s code to make sure no new bugs or vulnerabilities are introduced. Instead of reviewing that code, I’d rather just write it myself and have the confidence that there are no glaring issues. Beyond more intelligent autocomplete, I don’t really have much of a need for AI when I program.
This is how I use it, and it's a great way for me to speed up. It's a rubber duck for me. I have a fake conversation, it gives me different ideas or approaches to solve a problem. It does amazing with that
The code it spits out is something else though. The code it's trained on in GitHub means it could be based on someone with 2 months experience writing their CS201 program, or a seasoned experienced engineer. I've found it faster to get the gist of what it's saying, then rewrite it to fit my application.
Not even mentioning the about 50% chance response of "hey why don't you use this miracle function that does exactly what you need" and then you realize that the miracle function doesn't exist, and it just made it up.
I use it a lot for writing documentation comments (my company's style guide requires them), and for small sections at a time. Never a full solution.
Using an IDE definety IS programming.
Nothing elitist about it. Vim is not a modular tool that I can swap out of my mental model. Before someone says it, I've tried VS Code's vim plugin, and it sucks ass.
Wdym? Vim is in every ide and notepad man
Certain shortcut keys in vim conflict with shortcut keys in the IDE. The flow doesn't work the same.
I don't understand how you think you will convince anyone that you can't use vim, when so many do that without problems
Please avoid double negatives. I'm not quite sure of the meaning of your sentence.
If you're saying I have issues using vim if I can't use it in an IDE, no, that's not how it works. If you use simple vim (not much more than knowing how to get in and out of edit/visual mode, and use hjkl for navigation), then it's fine. Once you get into more advanced vim features, though, the key presses in vim get picked up by the IDE first, so IDE shortcuts take precedence.
If someone were to learn vim inside an IDE and develops it organically as part of their flow, it'd be fine. If you already have a lot of standalone vim flow setup in your mind, it's a problem.