Ole Bulbuk @flowdev_org

Back-end engineer since the nineties, co-organising GDG Berlin Golang, developing open source software. flowdev.org Berlin Joined August 2012

Tweets

236
Followers

207
Following

44
Likes

443

Ole Bulbuk @flowdev_org

3 days ago

@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.

0 0 1 34 0

View Details

GopherCon Europe @gopherconeu

4 days ago

⚡️ #gopherconEU Lightning talks ⚡️ @jespinog @flowdev_org @AinSoph #golang

1 2 3 248 0

View Details

Ole Bulbuk @flowdev_org

4 days ago

@gopherconeu @jespinog @AinSoph Thank you so much for having me! 😃

0 1 3 125 0

View Details

Ole Bulbuk @flowdev_org

a week ago

@rodrimora @dhh No, Trump. 😉

0 0 1 34 0

View Details

Mitchell Hashimoto @mitchellh

a month ago

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.

512 2K 15K 1.6M 5K

View Details

Ole Bulbuk @flowdev_org

3 months ago

@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.

0 0 1 49 0

View Details

Ole Bulbuk @flowdev_org

4 months ago

@goinggodotnet Not in Germany either. 😉

0 0 1 60 0

View Details

Casey Handmer @CJHandmer

9 months ago

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.

6 120 403 50K 35

View Details

Ole Bulbuk @flowdev_org

9 months ago

@duginabox @ibuildthecloud If they are your (de)serializers, you can build a custom way to hand any data to them. 🤷‍♂️

0 0 0 7 0

View Details

Ole Bulbuk @flowdev_org

10 months ago

@VaughnVernon And what are those better ways? I would love to learn more about it

0 0 2 106 0

View Details

Ole Bulbuk @flowdev_org

11 months ago

@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

0 0 1 49 0

View Details

Ole Bulbuk @flowdev_org

11 months ago

@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.

0 0 1 36 0

View Details

Ole Bulbuk @flowdev_org

11 months ago

@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. 🤷‍♂️

1 0 0 36 0

View Details

Ole Bulbuk @flowdev_org

11 months ago

@zajacr Clearly B and D. want has to be the edge value. The actual one has to be great or later.

0 0 1 18 0

View Details

Ole Bulbuk @flowdev_org

a year ago

@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.

1 0 2 74 0

View Details

Ole Bulbuk @flowdev_org

a year ago

@CAFxX I would like to see an example of that, too.

0 0 0 3 0

View Details

Ole Bulbuk @flowdev_org

a year ago

@VipinJangi3398 So it becomes easy to understand. 😀 It depends mostly on the context.

1 0 1 182 0

View Details

Ole Bulbuk @flowdev_org

a year ago

@thehumanmaskot Idiomatic Go code. It often gets the most optimizations from the compiler, too. 😀 Unless you can prove that it's a bottleneck. Then you write efficient Go code. 😁

0 0 2 142 0

View Details

Ole Bulbuk @flowdev_org

a year ago

@CAFxX Your statement is so abstract. So what exactly are you talking about then?

1 0 0 12 0

View Details

Ole Bulbuk @flowdev_org

a year ago

@Rajshri0987 Usually web APIs. I'm using GORM only for a desktop APP. ORMs are great for simple cases. But if things get complex, they become a bottleneck, IMHO.