Readit NewsDeleted Comment
How do you fix that, when the process is literally "we throw an illegible blob at it and data comes out"? This is not even GIGO, this is "anything in, synthetic garbage out"
It's a model. It either predicts usefully or not. How it works is mostly irrelevant.
("But it works - when it works" is a tautology, not a useful model)
Maybe spaghetti code delivers value as quickly as possible in the short term, but there is a risk that it will catch up in the long term - hard to add features, slow iterations - ultimately losing customers, revenue and growth.
I really don't know how to feel about this, maybe it's my education making me bigoted, looking down upon what's clearly ephemeral; slang words like these come and go with time, and I think the timeframe for words to be included in the dictionary has greatly reduced.
Almost no one apart from a very small, terminally online subset of people will ever use these words and an even smaller subset will use these in IRL conversation; adding these is a bad idea and doesn't bode well for dictionaries wrt credibility.
They should release a DLC for dictionaries that covers slang like this, not make it part of the official English specification.
- DLC
- IRL
As in, "things that happened before my Xth year of life are Normal, nay, Traditional even. Everything afterwards is Ephemeral, and possibly Heresy as well."
Alas! All is ephemeral.
Only similar in the vaguest sense.
- vibe code a thing
- it doesn't work, but it was CHEAP
- hire someone "to fix it"
- actually means "rewrite most of it, but cheaper"
- also means "become the scapegoat"
To a developer, it offers most of the work for very little payment. Not an enticing proposition.
(Yes, I've been burned by various "it's 90% done, we just need a few fixes", and that was BEFORE the current slop era)
I mean, this is much less common than people make it out to be. Assuming that the context is there it's doable to run a bunch of calls and take the majority vote. It's not trivial but this is definitely doable.