Replying to @webdevcody
Well, it's really easy to create or generate lots of code that doesn't achieve much.
I've seen it many times in really life.
I'm happy to have vibe coded an app at #GoogleIOConnect 2026 in Berlin.
Especially understanding better when to use AI studio and when to use antigravity instead will help me in the future.
#BuildwithGemini
Replying to @scripter_js @Govind_tiwari_
This is not only a list of great open-source Go projects but also a list of projects that are difficult to contribute to.
So the chosen meme hits the nail on its head.
I'm having a great time at #GoogleIOConnect with #BuildwithGemini
🤩
Replying to @AndreaBarisani
The problem has been solved the other way around:
I usually buy paper tissues that withstand washing just fine.
I had a flatmate who washed them intentionally so he could reuse them.
Not the original idea of paper tissues though.
Ole Bulbuk retweeted

Mitchell Hashimoto@mitchellhMay 15
United States
United StatesConnected via United States App StoreAccount-level information, not a live location or per-post device.
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.
Replying to @tsenart
I think it's more about sec teams now being *forced* to learn and use these tools next to everything they have on their plate already.
And even much more that the time to roll out patches is reduced to minutes.
This essentially removes any chance to test patches first.
Ole Bulbuk retweeted
A rare personal note. My dear friend Ivo (the dad) has a rare genetic liver disease (PSC) and has, after concerted persuasion from those of us who love him dearly, finally consented to a public appeal for a living donor.
Liver donation is quite miraculous in that one can give half and both halves grow back.
Fwiw, none of the AI models yet understand how to cure PSC, though I would bet that the next generation of humans will be more lucky.
I've never asked for RTs etc before but I think it would help in this case!
Link below.
Replying to @duginabox @ibuildthecloud
If they are your (de)serializers, you can build a custom way to hand any data to them. 🤷♂️
Replying to @VaughnVernon
And what are those better ways?
I would love to learn more about it
Replying to @JasonThorsness
I'm finishing a parser combinator library that can report multiple errors.
Only parsing (mathematical) expressions isn't finished yet.
github.com/flowdev/comb
Replying to @nzachow_
I think it's a good decision.
A better one might be something aspect oriented. That could help to centralize errors, logging, metrics, and other technical aspects.
Replying to @zajacr
There are already a lot of testing libraries. And many Gophers are happy with the standard library.
I'm not sure the world is waiting for yours. 🤷♂️
Replying to @zajacr
Clearly B and D.
want has to be the edge value. The actual one has to be great or later.
Replying to @bernoussama
It's good for many in-house projects.
But I wouldn't use it for open-source libraries.
I don't like to force dependencies that aren't strictly necessary on others.
And it's one more thing to keep safe/up to date.








