It sounds like you really have this well thought out and planned already.

Personally my only concern here would be trying to grow two new brands in English at the same time between all the other ongoing projects.

One reason that build in public is generally one way to grow a maker brand, is that it's hard to constantly come up with content while you're also actually doing the making part. So, perhaps stick with Maker Ibon being like your daily log of whatever you're working on. That gives you one clear thing to talk about on that side, and you would always have something to post since you're always going to be working on something.

Find all the cool Laravel peeps here ;)

Agreed.

Personally I see life tasks as a bit of a copout just for keeping streaks going anyway.

You mean for hosting the backend?

Any VPS of any kind can do that, yeah.

If you're looking for something super simplistic, maybe PocketBase would be an even easier step than Supabase: pocketbase.io/

Thanks for sharing! Very eloquently said, and perhaps a bit of a mirror to my own past and future. Mine was not as stark as yours but has some rhymes - difficult late teens, forcing incredible autonomy and motivation fueled by resentment, that propels you to great heights.

I've slowed down in my late 20s on this front at least.

In 2022 I had a period of reflection where I wrote on some similar ideas, and I'd like to share those with you:
nik.software/thoughts-on-comm…
nik.software/my-myths-of-belo…

Best of luck in your path further. While you may feel lonely in some regards, know that you have many kindred spirits hidden among everyone who passes you by.

Agree with Martijn - R2 is good and cheap for this right now.

As for Supabase, I mean yeah any backend will work if you want to split the downloads.

Agree with Ben here. Marketing site is for SEO and building persona-specific landing pages, among other marketing-specific purposes. So whatever you use to accomplish those goals is A-OK.

Since you're in Rails land, any method you'd use to render HTML is probably good.

I'm a Laravel guy, and for mine I use a combination of FilamentPHP + Folio + some hand-written data models to create a very simplistic blog. It gets deployed the same as my app server since it's part of the app.

IBKR has extensive documentation on how they function, including for how residency and taxes might work with them. First brush up on your local tax law around investments and capital gains, and then figure out how to pull the necessary documentation from IBKR whenever tax time comes around.

Conveniently, they also are able to "migrate" your investments to a different residency while keeping them in IBKR. So if you ever emigrate, you won't have to sell your investments off just to move the funds "out" of your old residence country.

I actively avoid ever needing to use it

If I need to handle the kind of scale it handles, I should ideally be earning enough to pay a devops person to take that pain away because I just find it soul draining to use almost any infra tool

I've tried to find a "must have" use case for dot files. Beyond a few personalised handy aliases, I'm really not convinced they're necessary for the average developer.

They'll reduce setup time if you move between machines often sure, but it won't stop you from the endless tweaking, configuration and debugging that developers are prone to do :)