Microtransactions for devs
Microtransactions for devs
37 comments
-
No one uses this meme correctly and it makes me irrationally upset.
-
At this point, this movie is probably older than most of the people that use this meme template.
-
brb crawling into a hole and crying
-
-
-
In which case would a competent dev use an LLM?
-
When the documentation is shit and you do not have time to scroll through 100 classes to find that one optional argument that one method accepts, I found LLMs very useful. They are pretty good at text understanding and summarizing, not so much at logic though, which is key for developing.
-
When Management™️ demands the app "Do AI" because "it's the hot new thing"
-
Manglement will have to fill an open position real soon
-
-
Looking up how to do something, as an improved stackoverflow. Especially if it provides sources in the answer.
Boilerplate unit tests. Yes, yes, I know - use parametrized test, but it's often not practical.
Mass refactoring. This is tricky because you need to thoroughly review it, but it saves you annoying typing.
I'm sure there's more, it's far from useless. But you need to know what you want it to do and how to check if done correctly.
-
Boilerplate unit tests.
It will generate bad tests, so you will have lots of tests blocking your work, but won't actually test the important properties.
Mass refactoring.
That's an amount of trust in the LLM capacity to not create hidden corner cases and your capacity to review large-scale changes that... I find your complete faith disturbing.
-
I very rarely find result summarizers useful. If I didn't find something normally, there won't be anything in there.
I sure love tests and huge codebases with errors in them. In the time I read and understood an LLM's output, I could write it myself. And save on time later when expanding/debugging.
-
I am so far from trusting and LLM to do mass refactoring even with heavy review. Refactoring bugs can be super insidious.
-
-
If you need to use a new language that you are not yet used to, it can get you through the basics quite efficiently.
I find it quite proficient at translating complex mathematical functions into code. Specially since it accept the latex pretty print as input and usually read it correctly.
As an advanced rubber duck that spits wrong answers so your brain can achieve the right answer quickly. A lot of the times I find myself blocked on something, ask the AI to solve and it gives me a ridiculous response that would never work, but seeing how that won't work it makes easier for me how to make something that will work.
-
I use it daily. I wouldn't blindly trust code it writes, but it offers alternative solutions and when I'm hunting for a but it's very good at giving me ideas of what might be wrong at a glance. Terraform and infra too it can catch nuances i may be missing.
-
It's outstanding at bridging the gap between "I need to mash these two concepts/technologies together" and "the answer is spread across six different StackOverflow threads." Hunting that stuff down using Google has been a delicate operation even at the best of times in the last 25 years, but it always took a lot of time. With an LLM and each such query, I've saved hours, maybe even whole workdays. Fact-checking an AI takes far less effort.
-
I have to, for my KPIs! I guess job interviews are the real personal performance meetings though.
-
Boring, tedious shit that doesn’t require brainpower, just time, when fixing whatever comes out of the LLM is less annoying than doing it myself.
-
Do quickly write the same pattern thousands of people write every day
-
-
What a terrible idea.
If I were to pay for a digital item, I would get a guarantee that the data is valid and works.
As in, paying for LLMs, imo, is actually a worse deal than standard micro transactions.
They are more like loot boxes, you pay for the chance of a good result.
-
Pay per loaf of bread at the baker
... Microtransactions for hungry people
37 comments