- Never seen vibe coders write Dockerfiles.
- Never seen vibe coders manage Docker containers.
- Never seen vibe coders configure CI/CD pipelines.
- Never seen vibe coders set up staging environments.
- Never seen vibe coders manage production deployments.
Every vibe coded app somehow ends up on:
GitHub + Vercel + “Deploy to Production”.
this is why you use the expand-migrate-contract pattern
if a newly expanded write path breaks, you roll back the deploy and leave the new column(s) unused
if a newly migrated read path breaks you should just be able to flip a feature flag and restore service immediately
Rolling back a database migration in production is a myth 90% of the time. You almost never "roll back", you just write a new migration to roll forward because live user traffic already wrote records into the new schema structure while it was active.
@SYNESTHEIZURE@batkatebush i feel the same way about all of these but do have a soft spot for adventure time, maybe just because i would watch it as a kid
You see, what fascinates me about “remember to not smile” is that he needs his pain to be witnessed. He suffers at 4am, okay, fine, many people suffer. But then, immediately, he makes a slide! He gathers the entire company! He writes an article! Is it not clear what is happening here? Suffering without an audience simply does not count. This is ideology at its purest.
We see here the old Protestant trick in its Silicon Valley form: success alone is vulgar, almost pornographic. My god, you cannot simply succeed. It must first be purified through unnecessary suffering. So you get this obscene reversal where pain stops being a cost of the product, and instead becomes the product itself. The developer documentation is, how do you say, merely the byproduct, the excrement of the true production, which is the suffering. As Hegel already knew, and here I think even Lacan would agree, although perhaps not, the true obsession is always with deserving success.
Here I must tell you this old joke from Soviet Union. A worker says: "we pretend to work, they pretend to pay us.” Now here it is inverted, which I claim is much worse. They are paid perfectly well, wonderfully well, and so they must pretend to suffer. Do you see the perfect madness of this?
And now, the ultimate obscenity. Imagine the company succeeds while everyone leaves at 5pm. Catastrophe! Total ontological catastrophe! In this worldview, I am tempted to say, failure would almost come as a relief. Failure means you simply did not suffer enough, go back, suffer more. But success at 5pm? This cannot be explained.
So when he says "remember to not smile," this is a desperate command of the superego. If you smile, we will all discover the pain was never necessary.
My deeply repressed libertarian instincts kind of love Empower.
Like hell yeah there should be an alternative option for Uber that has a 10% of giving you a rapist driver and you can't get any insurance if they crash. Let me choose which one I want
similar thing happened to me when my friends and i watched the pervert's guide to ideology - my friends thought he was speaking some foreign language but as the resident zizek-whisperer i had to translate everything into californian standard english
Me and my friends watched Witch and got so high we couldn’t understand the colonial accents. My one friend got higher than the rest of us and was able to flawlessly translate
@MatthewBerman have your agents make prs that dont conflict that much with eachother, for one
and use a merge queue with speculative ci batching, graphite works quite well if youre on github
This river here is the official geographical border between Anthropic and OpenAI. On the other side cosmic horror, torment nexus, machine despotism, you build spyware for the govt and you like it. On this side civilization, Claude constitution, unceasing allegiance to the human race, you build spyware for the govt and you don't like it.