What prompt did you use to make this 🤨🤔
this post was submitted on 10 Feb 2024
940 points (94.5% liked)
Programmer Humor
19471 readers
1325 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 1 year 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... 😅
Also: the middle fingers are far too long
load more comments
(2 replies)
https://knowyourmeme.com/memes/family-laughing-at-crying-child-opening-christmas-present
That includes some history, but not the prompt itself.
That's why I'm proud to be also programming in HTML
"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.
Is that you, Samsung?
Hey, no need to accuse the guy of cutting tvs to get out of honoring the warranty.
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
Making middle management do everything is not 'running a business'.
If middle management is doing everything aren't they no longer middle management?
They get middle paychecks.
And vetoed on sensible decisions in favour of non-sensible ones that make the upper management larger bonuses.
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.
Build an entire ecosystem, with multiple frontends, apps, databases, admin portals. It needs to work with my industry. Make it run cheap on the cloud. Also make sure it's pretty.
The prompts are getting so large we may need to make some sort of... Structured language to pipe into.. a device that would.. compile it all...
I mean it can start much smaller.
Here is access to a jira board. Here are unit tests. Do stuff until it works.
Perfect! We'll just write out the definition of the product completely in Jira, in a specific way, so the application can understand it - tweak until it's perfect, write unit tests around our Jira to make sure those all work - maybe we write a structured way to describe each item aaand we've reinvented programming.
I see where you're going, but I've worked with AI models for the last year in depth, and there's some really cool stuff they can do. However, truly learning about them means learning their hard pitfalls, and LLMs as written would not be able to build an entire application. They can help speed up parts of it, but the more context means more VRAM exponentially, and eventually larger models, and that's just to get code spit out. Not to mention there is nuance in English that's hard to express, that requirements are never perfect, that LLMs can iterate for very long before they run out of VRAM, that they can't do devops or hook into running apps - the list goes on.
AI has been overhyped by business because they're frothing at the mouth to automate everyone away - which is too bad because what it does do well it does great at - with limitations. This is my... 3rd or 4th cycle where business has assumed they can automate away engineers, and each time it just ends up generating new problems that need to be solved. Our jobs will evolve, sure, but we're not going away.
load more comments
(5 replies)
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.
BUT I TOOK ALL THESE COURSES!
view more: next ›