Vincent Tunru @VincentTunru@fosstodon.org

Like #RSS? Know #CSS? I created a tool to generate RSS feeds from arbitrary websites using CSS selectors.
And it's called... Feed me up, Scotty!

https://feed-me-up-scotty.vincenttunru.com

I cracked my phone's screen 😢

However, it's a @Fairphone, so I just replaced the screen with that of a friend's old Fairphone. Took me all of five minutes 😎

The cool thing about working on developer tools is that you get continuous UX research, for free, just by lurking on your issue tracker, forums and/or chat rooms.

Just did my first system upgrade since switching to #Fedora and... Wow! Not only was it easy (literally: press the "download" button, then the "restart and install" button), but also very fast. Like, I quickly got to 50%, then I went to the bathroom, and as I got back it was done.

And here I'd set aside my Saturday to deal with any potential issues.

Often, the good parts of an approach will be discarded because they are outweighed by the upsides of a newer approach. Then when eventually someone finds a way to get the benefits of the old approach with the new one, some clever cynic will come out of the woodworks lamenting how 'everything old is new again', completely disregarding the advances made in the meantime.

The boy scout rule: leave the code you touch cleaner than you found it.

It sounds attractive, but I'm having second thoughts. What's "clean" isn't usually universally agreed upon, and inconsistently-applied conventions makes those conventions hard to learn for new contributors.

There's two ways to learn abstract tools.

There's rote learning: if I do this, this happens. This'll get you started.

But real understanding happens when you form a mental model of the tool.

Sounds obvious, yet so many engineers use Git every day only knowing `git commit -am`.

(Of course, this is where I should plug my tutorial that helps you form a mental model of Git in ~11 minutes: https://agripongit.vincenttunru.com/)

My perfect employer:

- aligns with my ideals,
- makes products I'm personally excited to use, and
- has competent colleagues.

There's always been one organisation in particular that always seemed to me to tick all those boxes, so I'm very excited that, starting tomorrow, I'll be joining Mozilla!

Apparently https://replay.io now works on Linux too, and I'm excited! It's going to help me solve so many gnarly bugs.

If anyone wants an invite, let me know. (Unfortunately a Google account is required for now.)

I wanted to add some nuance to the whole #Tailwind kerfuffle. In my view, it solves some pretty specific problems that you may or may not have.

More at https://vincenttunru.com/why-tailwind/

Installed #Fedora today — first time ever on a non-Ubuntu-derived Linux. The installer was a little bit confusing, but other than that everything except the fingerprint reader works flawlessly and so far is pretty straightforward!

Anyway, it's been a great ride, and I want to thank everyone who made it so. I'm very much looking forward to seeing what will become of both Solid and Inrupt.

And if anyone wants to discuss anything Solid, get in touch!

I also want to continue seeing the Solid community grow beyond the limited demographic it used to represent, and to support the fantastic initiatives that have been and will be started that help make this happen. To make this work for everyone, we need to involve everyone.

In fact, I experienced that solid-client works well first-hand, when using it in my spare time to build what I'm proud to consider a vital tool for Solid app developers: Penny.

https://penny.vincenttunru.com

...which brings me to #ProjectSolid: the enthusiasm around it is fantastic, and even in my life-after-Inrupt I would love to see it succeed.

Which means that yes, I'll try to stay involved, keep maintaining Penny, keep empowering people building on top of it.