4,247 karma · joined February 17, 2015
That's a straw man. Nobody in authority said this once the vaccine was out and it was obvious that immunity wasn't 100% or permanent. All vaccines are different. No one knew until it came out what category this vaccine would fall into. You can still get measles after getting the measles vaccine. But you're much much less likely to die from it.
What the vaccine did do is greatly reduce the severity of the disease, which saved countless lives. See Wuhan, Northern Italy or NYC before lockdown. If the vaccine didn't work, as soon as lockdown ended, the hospitals would have filled to over capacity like they were in those places in the early days.
Did you not read the article, or are you refuting it?
No one is suggesting that.
Maybe if grocery store peaches weren't a fibrous, tasteless representation of a real fresh peach, they'd still be in business.
Burning Man may have peaked by now. But looking back, most would agree it still had a lot of good years left in it in 1998.
The vendor was basically right at the end of the "fun" part of cranking out features, and just about to hit the "rubber meets the road" part where you start fixing bugs, finding new edge cases, discovering new hidden requirements, and realizing X% of your design assumptions were completely wrong. Oh yeah, and minor little mop-up tasks that don't wow the client, like integrating with a payment processor, integrating with our internal scheduling system, exporting invitee lists from our CRM into our app, etc.
It's possible we're in a similar cognitive debt situation to having to maintain a large, swiftly-AI-coded app. After about 6 months of stressful development, which started with what I call throwing dye in the water and eventually progressed to understanding one small feature or flow at a time, we have maybe 50% of the mental model we'd have if we'd built the app ourselves. Whole chunks of the app are still a black box to us.
It doesn't help that requirements have evolved so much since the original documentation that it's worse than useless because we can't trust it. So the code, which we don't understand, is the only documentation of the current requirements.
Of course, our internal clients are pissed because the final product is taking so much longer than expected, when they could see all these awesome shiny, happy-path, 80%-done features 6 months ago. We're in a constant fire drill. Everyone on the project is miserable. It's the least fun kind of development.
> It sounds like you’re thinking of Kwisatz Haderach from Dune.
> The spelling/pronunciation gets mangled a lot (“quiz-atz haderach,” “kwitzatteracht,” etc.), but the original term is Kwisatz Haderach.
I asked it if Hacker News was in it's training data and gave it the website and it gave me the first "I don't know anything about that" I've ever seen from it.
Just saying, "We should do science for science's sake" is not enough. We've done that. Go read The Bell Curve and knock yourself out. What people like you seem to want is continued, motivated hammering of the issue.
I never felt like I had more energy in the morning, afternoon, or night. But if I tried to work out in the afternoon when I was in the 6am habit, I felt completely dead.
I go to ChatGPT for basically any annoying code snippet and even functions now. I'm done ever having to guess at map reduce syntax again, or trying to remember if slice mutates the target array.
I'm messing with with codex more and more. But I still don't trust it to design features for me. Maybe in 6 months, I will. Is it really that important to force developers NOW to get to a place they'll get to in a few months anyway, assuming the hype is real?