Hacker News new | ask | show | jobs
by __loam 785 days ago
I think the mindset is like, we've done a bunch of development, let's sell it to deliver some value now rather than wait for it to be perfect. It makes sense from that agile manifesto perspective but I miss the days of buying something like a game boy advance cartridge that ships once and mostly just works.
4 comments

I'm seeing this play out at my workplace. Going down the wrong path just because we couldn't add an extra week to think things through and go down the right path from the beginning.
Time to think is unfortunately a luxury.
The trap here is thinking that starting fast is also the way to reach the goal the fastest. That doesn't always work and is especially true the more complex a project is.
The problem is with the lack of transparency and expectation setting. If you sell something with lots of hype and then deliver half of it, you've failed.
The product owner in a company should be defining success for the development goals in agile, not beta tested on the paying public.
I agree. I wonder if the AI-aspect muddled things, like engineers saying "we just need more data for <x feature>, let's push for a cheap product and iterate fast"...
That only works if you are doing something unique enough to ignore its imperfections, otherwise people will use a full-featured competitor. The alternative to the Rabbit is your phone, I suppose.