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?

That is right on. Same situation here.

That would be a bit depressing if this eventually happen. But I do understand where you come from.

I would also not accept if I had to do this during off hours. And it's also very different from hackathons where you have a company agenda. Hopefully this does not change, but we never know.

You misunderstood it. These are not days off. They are meant for you to learn, experiment and level-up.

It needs to be something that helps you to level-up somehow. But it does not force you into specifics, so it’s up to you to choose.

At the end of the second day, there is usually a little show-off session where folks that got something interesting at the end and want to share, they can. But you are not forced to.

It’s still normal working hours, so you are expected to do something.

This kind of hackathons outlined by the OP indeed sounds like trouble. In the current company I work at, we have every 6 weeks, 2 full days to hack on whatever we want. Zero expectations.

This has been really cool because: - it’s during normal working hours. 9 to 5. No weekends or all nighters. - you are entitled to cancel all your meetings - you can work on product-related ideas or experiment with a new language. It’s 100% up to you. No expectations or strings attached.

A few cool features in our app eventually started out from days like that, but so far it has been more like a side-effect than a requirement per se.

I see a lot of positive things coming out of this. And the company for sure gets benefits. So far it has been a win-win from my POV.

> Are we slowly losing a joy of reading blog post because there are so many?

Interesting perspective. My experience so far is that I've come across very few blog posts, at least good-quality ones. I do agree that it's hard to find the good ones tho.

I also have this feeling that books are becoming stronger somehow. I'm big fan of books in general and I tend to read them cover-to-cover as they work best for me compared to video courses and other mediums.

I have a similar experience as the OP. I got a vacuum robot (Roborock) and it does work like advertised. Vacuum and mop works so well that I almost never to mob my house manually anymore.

Andreas is a truly inspiring individual. I follow his videos on YouTube for a long time and his calmness and direction while coding the SerenityOS is something I try to learn from him.

This is interesting because one thing people ask me when a system is using JWT is in case they reset their password, how can they invalidate all existing sessions? They basically can’t.

Using A cookie-based/token-based session strategy, you can do that quite easily.

But then you introduce a database-like dependency that potentially every micro service will need access to.

Because it’s effective and works.

First thing I would check would be to see the new company is profitable or it is well funded and on its way to profitability. If that is the case, I would consider switching for sure.

Kotlin and Scala are the most popular I’m seeing in my current field (finance).

Great article! I am also using turborepo and it has been fantastic! Being able to skip builds from packages that have already been built either in CI or in other developers machines is really amazing.

If you are not using Vercel caching, I’ve built my own open-source turbo cache backend[1] that can be self-hosted

[1] https://github.com/brunojppb/turbo-racer

Elixir + Phoenix sound like a great stack. I've been building a side-project with that stack and it has been a joy.

With that being said, I believe it might be quite a learning curve for you. Not because it will be difficult, but just because there might be many topics at once to learn. Like you said, GraphQL, Postgres, Elixir (and a little bit about the BEAM ecosystem), Phoenix and CouchDB. If you are doing anything for the Web, you will inevitably touch JavaScript as well.

Not sure if you are open for suggestions, but one thing you could consider would be using JavaScript or TypeScript with NodeJS. I'm not the biggest fan, but you would be able to use the same programming language in the frontend for our Web app and also the backend with NodeJS and a full-stack framework like Remix[1] or NextJS[2]

This could reduce the overhead to start your side-project and will give you fewer puzzle parts to learn and put together.

[1] Remix: https://remix.run/ [2] NextJS: https://nextjs.org/

Cross-compiling binaries for many platforms and architectures using Docker and QEMU[1] was a neat way I found to support more targets without having to have the hardware.

[1] https://www.qemu.org/

> We handle the hard stuff so you can focus on the UI.

That sounds very arrogant and diminishing to the UI folks doing the frontend work. Creating a proper UI is hard. Ask your backend engineers to create a good UI and you will see.