Track your earnings as they happen. I build
mypay.today which shows your gross & net pay in real time: per day, week, month, and year.
A simple way to see the value of your time (or how much that meeting just cost you).

History doesn't repeat - but sometimes it rhymes.

In the 2010s, tiny dev teams built products w massive impact. A company with just 13 developers served 30M users.

In 2024, a company with just 15 developers is serving 25 million users.

Bluesky deepdive: newsletter.pragmaticengineer.com/p/bluesky

Even if you have no idea. Think out loud. As long as you try to solve it analytically you are golden.
Most of the time it isn’t about the correct answer, there are books for that, also this thing called internet.
HOW you get to an answer is much more valuable.

After hundreds of tech interviews one simple thing that anyone can add to their tool box and doesn’t take barely any effort: think out loud!
This also goes for pairing.
Don’t keep your thoughts to yourself!
Allowing the interviewer to see how you tackle a problem will work wonders.

@bruno-felix.bsky.social welcome!

I’ve always been big on owning my own data. Now I mostly do. What started as a fancy back up is now a full blown suite with lots of little OSS projects.

Firefly, ghostfolio, hoarder, silverbullet to name a few.

The selfhosted podcast is also a nice listen.

I’ve seen people mitigate this by building in their free time outside world. I’m my case, that’s a hard ask, usually work leaves me to drained.

What I have found to kind of fill the gap is self hosting. Tinkering around with docker, spinning up things, networking, automation.

One of the biggest issues with getting more experienced and broadening your impact is that you don’t get to do much hands on work anymore.
Mainly because of time constraints. You may build something but you aren’t able to finish out follow up.

I have to confess I treated myself to a Keychron Q11 QMK for work use, promoted by a good colleague of mine. Can’t wait for it to arrive and share impressions

There are lots of signals to tell a good software engineer from a normal one. But one that is very strong and has rarely failed me so far: Ownership.
Care about what you ship, go the extra mile, check after you deploy, be accountable.

Happy with the quality of the feed and interactions in Bluesky so far.
Account switching in the app and sharing posts via dms could be a bit more use friendly.

That Netflix crashed at the massive (though anticipated) load during the Tyson / Paul livestream shows just how hard it is to handle peak load.

Clearly, they prepared and should have had the infra to handle it: and still something went wrong.

Obligatory Hello world to kick things off: 👋🗺️