brunojppb

Clickhouse has been a game changer for some of the companies i have worked in the past. This reminds me of this podcast episode (1) from the Rust in Production pod about their Rust adoption.

1. https://open.spotify.com/episode/0TBKDUhO0KihBxEzZqnQx1

You call the GitHub folks “monkeys” and “rookies” and at the end you “humbly” ask people to donate off? That is pretty depressing to see.

I used to look up to the Zig folks…

Based take. It is rarely back and white when it comes to social-technical challenges like this.

Interestingly enough, the iOS app has been working really well for me.

Performance, usability and overall adaptability to the phone size, it is incredible how a native app can be that good.

I wish the Web UI performed as well as the native iOS app.

Beautiful write-up! Thanks for sharing this. I want to write a game boy emulator in Rust and your blogpost really inspired me to kick this off. I’m bookmarking this.

My workaround for this as a person who travels a lot was to buy 2 raspberry Pi’s and put them at my family houses in different countries and use Tailscale on them as exit nodes, behaving like my own VPN. The residencial IP address makes things a lot easier when connecting from random places.

Thanks for sharing this. I used to care for my grandma back home (Alzheimer’s), but the financial burden is brutal. I moved countries so I could be able to afford caring for her but ended up leaving the large part of the physical work for my mom and sister. Thankfully I can now afford to support her financially much more, including paying for a dedicated nursing home nearby my moms.

I’m 35 now and keep wondering how future is gonna be as I have no kids and no desire in having them (also not wishing them a life where they would have to care for me)

I’m trying to keep my health up now and dedicating more time for it so I can hopefully hold the fort.

I wish you the best for you and your father.

I’m currently reading this book called “Supercommunicators” and while I’m not done with it, there are some ideas there that really resonate.

One of them is that this kind of people are generally in the minds of their friends/acquaintances. And one of the reasons there is that they see them as very good listeners during conversations. They match their conversation style, they confirm what they’ve been talking about with feedback and this sort of behaviour that tend to help people build trust and friendships.

I’m not done with the book yet, but I can see many things relating to what I generally practice. And I’ve got good friends :)

> the only technology we should be using to create web UI is JavaScript

Quite an interesting idea, but stating that JS is the true way of creating Web UIs misses the mark by miles. You would be surprised by how far you can get with HTML and CSS alone. You will ofc need JS for more dynamic interactions, but ditching the server entirely and delegating everything to JS will just take us to the SPA mess that most of have been burned with.

> I make my money doing literally whatever I want…

Classic take from somebody that most probably could spend their entire time just fiddling with ideas, with zero worries about money. Everything else was taken care of. Not everyone has this luxury pal.

The author is plain, simple sharing his story. Can you replicate his success? Who knows. But I respect him for sharing this candid blog post documenting his steps.

Fantastic write-up. Major props for disclosing the details of the attack in a very accessible way.

It is great that this kind of security incident post-mortem is being shared. This will help the community to level-up in many ways, specially given that its content is super accessible and not heavily leaning on tech jargon.

> Boring is good. Boring is stable. Boring means being able to focus on your work, not on what’s different about Go.

This really resonates with me. I work with NodeJS and the JS ecosystem in general on my day job and I have to tell you, the struggle is real. The ecosystem is fragmented, everyone is doing their own thing, which is hard to make things stable. Don’t get me wrong, I still enjoy this work, but I really wish the JS ecosystem could have a stable modern foundation we could rely on.

> There was a handful of new data that had been created in the intervening ~30 minutes. We pulled that diff data manually, and uploaded it to the new database.

But doesn’t that mean you had some partial downtimes? How did you manage to keep everything running during these 30 minutes where data was copied from the old DB to the new one? Let’s say there is a cron job that must be executed and its result would be stored back to the DB. Did you “pause” everything and reschedule it in the new instance once the diff copy was over?