280 karma · joined August 14, 2025
MVP means just enough engineered code to solve a problem, rough around the edges and lacking features sure, but not built by someone who has literally no idea what they were doing.
Prototypes of physical products are never put into production and sold to consumers. Unfortunately software prototypes "run", and are sold at that point. Then they begin to scale, and the inherent flaws in their design are amplified. The same thing used to happen with MS Access apps; the same thing still happens with "low code" solutions.
The engineers cost just as much after the prototype phase, but if you don't hire them to build your MVP then you never have one.
It's decent for scenarios where I need to look something up but don't have the most likely specific words for the concept, it seems to be able to consider synonyms and/or domain-specific jargon that I don't have a grasp of yet.
It's bad for scenarios where I need to accomplish something using a specific version of a library, language or platform. It can help to be very specific with your version numbers in your prompts, but at a certain point it doesn't seem to alleviate the effort of just reading version-specific documentation for whatever you're trying to do yourself.
It's worse than terrible at writing code, because it's great at writing code which looks correct and is thoroughly commented as though it understands what the code it's generating should be doing, but that code is often wrong in subtle ways.
The most surprising thing is that despite the initial discomfort, I often find myself waking up on the thing an hour or more after laying down on it. I always set a stopwatch timer on my phone when I use it since 20 full minutes on it is the baseline recommendation, but very often I'll blow right past that.
Car loans have a bit more of an inherent predatory bent since most Americans need a car to get by. That's not to say we all need a car which costs so much that an 84 month term becomes worth considering...
The adjective "needful" means:
- being in need
- necessary, required
It's an attempt to use emotional leverage to acquire assistance.
In the author's case they're appealing to prowess; "if you can help me with this then clearly you are an accomplished java person."
In my first two examples it's usually someone leveraging the nature of your relationship; "if you care about me you'll do this/look at this for me."
In my third example they're probably drowning or something and are trying to get someone's attention before that happens.
It's all very needful.
Dedicated for sure though, and commendable, especially since it's FOSS.
For now, AI can give you an implementation, but it can't tell you if that implementation is good, if it's secure, if it's fast, or if it will play nice within the ecosystem of an existing project.
We've got plenty of work over the years fixing code that was written by people who shouldn't have been trusted to write it, and we're going to get plenty more work fixing code that was written by AI that shouldn't have been trusted either.