103
AI chatbots were tasked to run a tech company. They built software in under seven minutes — for less than $1.
(www.businessinsider.com)
this post was submitted on 11 Sep 2023
103 points (68.5% liked)
Technology
59322 readers
4428 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's a lot less in my opinion, because you can just ask it a question rather than having to read and interpret things. Every programming tutorial in every language is going to waste my time explaining how loops and conditionals work, when all I want is how this language does them.
Seriously?
If I google for example:
The first result is https://www.w3schools.com/cs/cs_for_loop.php
In the time it took me to get to that ChatGPT would still be writing its reply.
Right, but you can't give it the variable names you're using and have it fill them in, and if you want to do something inside that loop with
I can ask ChatGPT "Write me a loop in C# that will add the variable value_increase to the variable current_value and exit when current_value is equal to or greater than the variable limit_value, with all the variables being floats"
You won't find that answer immediately on the Internet, and you're more likely to make errors synthesizing the new syntax.
But you do you, I'll keep using ChatGPT and looking like a miracle worker.
Why are you actively trying to avoid learning how to write the loop? Are you planning to have ChatGPT fill in your loop templates for the rest of your life?
It's going to be slower overall than just using the reference and learning how to do it. I really, really am skeptical that a developer at the level where they need that feature is going to seem like a miracle worker to anyone other than people who are just impressed when you can do anything with a computer.
First, how is this different from having your IDE fill in your loop templates?
Second, no, of course I learn how to do it and then copy/paste from my existing code like a normal person.
Third, this is much more customizable. The example I gave is pretty simple, but you can explain algorithms to ChatGPT and have it figure it out.
Finally, I'm usually doing this for a customer in a language I'll never use again. Last week it was LabView. My role has me writing proofs-of-concept for customers frequently so I'm not going to learn something I'll never use again.
Not when you're not familiar with the syntax and don't have an IDE set up for it.
This happens in my job a lot more than I'm comfortable with.
I don't do that actually, but I think there are some differences.
That said:
Maybe you're the one in a million exception where this approach is a benefit. Most of the time when you talk to people on the internet, they're going to assume you're a reasonably typical case and not the extremely rare exception.
If writing simple loops with ChatGPT makes you a miracle worker then you might have other problems than AI.
And even simple things break down when you ask it about using library functions (it likes to hallucinate heavily there).
It's not that writing loops does it, it's that I can ask ChatGPT to hand me pre-assembled parts that I can snap together instead of typing them out with my squishy human fingers. And I can do it for pretty much any language without too many syntax errors.
I'm a senior software developer (Currently .NET backend with DevOps). Writing code is probably less than 10% of my work day. And in that 10% Visual Studio autocomplete does most of the typing. It's frequently wrong, but it's good enough plenty of the times.
Actually working on software consists of writing specifications, security concerns, architecture, talking management out of dumb decisions, having meetings with stakeholders or other companies, working on automatic deployments, writing unit and integration tests, refactoring, performance optimizations, database migrations, bugfixing, ...
Green field writing new code is rare and that's mainly what AI can do (80% correct, maybe). Most of real programming work happens on existing code.
I'm not saying AI will write entire applications, but it is really useful at writing small bits of code for a human being to assemble which can greatly improve productivity.
Though if we could get it to handle stakeholder meetings I'll never use it for programming again.