What prompt did you use to make this 🤨🤔
this post was submitted on 10 Feb 2024
1000 points (100.0% liked)
Programmer Humor
22444 readers
3221 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
The irony. I bet the guy who prompted that calls himself an artist.
Was going to comment about how there is a stock photo for everything. Fingers seem too good for AI?
Nevermind, that kids right hand... 😅
load more comments
(3 replies)
https://knowyourmeme.com/memes/family-laughing-at-crying-child-opening-christmas-present
That includes some history, but not the prompt itself.
"prompt engineering"
Sounds made up af
The US add engineer to everything to sound most prestigious than they are. If you sell your service as a AI prompt writer, you get paid peanuts. If you sell the same service as AI prompt engineer, the C-Suites cream their pants.
load more comments
(3 replies)
load more comments
(2 replies)
"Engineering"
They're not engineers and they're too chicken shit to act like engineers.
Looks like an ai did that
HATERS will say it's fake
If you look close enough, all pictures are fake.
load more comments
(1 replies)
load more comments
(1 replies)
“prompt engineering” in itself is such an embarrassing term for the act of saying “computer uhhh show me epic boobies!!”
like that joke about calling dishwashing “submerged porcelain technician” but unironically
It's not engineering either. Or art. It's only barely writing, in an overly literal sense.
People in glass houses...
Software engineering isn't engineering.
Yes, it is. Mostly because "real engineering" isn't the high bar it's made out to be. From that blog:
Nobody I read in these arguments, not one single person, ever worked as a “real” engineer. At best they had some classical training in the classroom, but we all know that looks nothing like reality. Nobody in this debate had anything more than stereotypes to work with. The difference between the engineering in our heads and in reality has been noticed by others before, most visibly by Glenn Vanderburg. He read books on engineering to figure out the difference. But I wanted to go further.
Software has developed in an area where the cost of failure is relatively low. We might make million dollar mistakes, but it's not likely anybody dies from it. In areas where somebody could die from bad software, techniques like formal verification come into play. Those tend to make everything take 10 times longer, and there's no compelling reason for the industry at large to do that.
If anything, we should lean into this as an advantage. How fast can we make the cycle of change to deployment?
I help make Healthcare software. Mistakes can easily lead to death. Not most, but it's something we always have to worry about.
We might make million dollar mistakes, but it’s not likely anybody dies from it.
I had a coworker who got a gig writing PDA software for a remote-controlled baseball machine. He was to this day the most incompetent programmer I've ever met personally; his biggest mistake on this project was firing a 120 mph knuckleball (a pitch with no spin so its flight path is incredibly erratic) a foot over a 12-year-old kid's head. This was the only time in my 25-year career that I had to physically restrain someone (the client, in this case) to prevent a fist fight. I replaced my coworker on the project after this and you can bet I took testing a little bit more seriously than he did.
load more comments
(2 replies)
load more comments
(1 replies)
In many cases this is accurate. Programming alone doesn't amount to engineering. Lotta low quality lines of code being churned out these days because standards have dropped.
By how some teams operate, and some developers think, there is certainly cases where the "engineering" aspect is hard to find.
mm yes ai
Bro if you could get there just by prompting, it would be.
There are no models good enough to just ask for something to be done and it gets done.
There will be someday though.
There are no models good enough to just ask for something to be done and it gets done.
We call those "compilers". There are many of them.
Sounds like someone's worried about how easily replaced they'll be in the future...
load more comments
(5 replies)
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.
Lol that's like not hiring someone because they take notes with a pen instead of a pencil.
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:
- Refactoring code
- Turning code "pure" so it can be unit-testable
- Transpiling code between languages
- Slapping together frontends and backends in frameworks I'm only somewhat familiar with in days instead of weeks
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)
- Adding tonnes of unit tests
- Making helper functions instantly
- Basically anything autocomplete does, but on steroids
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.
Your original post referred to wanting to hire people based on the tools they use to do a task, not their ability to do the task - in fact, you talked down to people for using certain tools by calling them elitist. That's why my pen/pencil comparison is accurate.
Personally, I think caring about that is silly.
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.
load more comments
(2 replies)
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.
load more comments
(2 replies)
Using an IDE definety IS programming.
Sure, you can code in Vi without plugins, but why? Leave your elitism at home. We have deadlines and money to make.
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.
load more comments
(4 replies)
Looks like every Christmas I've ever had...
j/k, or am I?
No I am... but am I really? :-P