Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

FWIW I think your style is better and more honest than most advocates. But I'd really love to see some examples of things that completely failed. Because there have to be some, right? But you hardly ever see an article from an AI advocate about something that failed, nor from an AI skeptic about something that succeeded. Yet I think these would be the types of things that people would truly learn from. But maybe it's not in anyone's financial interest to cross borders like that, for those who are heavily vested in the ecosystem.


But, yeah, looking again, that was a pretty big omission. And even moreso, a missed opportunity! I think if this had been called out more explicitly, then rather than arguing whether this is a realistic workflow or not, we'd be seeing more thoughtful conversation about how to fix the remaining problems.

I don't mean to sound discouraging. Keep up the good work!


there is a portion in the article where I talk about how our hadoop refactor completely failed


I think what the OP is asking for is an article _like this one_ about where you go in-depth into what you tried, where the system went, and more specifically what went wrong (even if it's just a list of "undifferentiated issues"). Because "we tried a thing. It didn't work. We bailed out." doesn't show off the rough edges of the tool in a way that helps people understand "the shape of the elephant".

Or, in the vein of https://adamdrake.com/command-line-tools-can-be-235x-faster-... - "here's a place I wouldn't use an AI tool because _other thing_ is far better"




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: