I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.
I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).
It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.
The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.
We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.
I worry.
Hey @EU_Commission I enrolled for an Apple Dev account for my company last Monday, and I'm stuck in the queue due to a "high volume" of requests
Can you apply some pressure? Thank you
The new ideal co-founder pairing is:
1. Person who decides what you are and aren't doing and keeps course
2. Person who ensures your company metabolizes a post-AI scale of contributions effectively
@OsokoyaF@auth0@clerk Not wanting yet another account to keep track of, one fewer dependency, it's simple/easy to do without a service, and to be real, many of the things I've made never saw the light of day, so I had one fewer thing to cancel when I moved onto the next thing