Kind likes

 Like

Liked Filippo Valsorda :go: (@filippo@abyssdomain.expert)
Post details
Attached: 1 image Hey all, I turned 30 this week! 🎈 I feel a bit weird asking for a "present" but if my code, writing, or talks reached you over the years, I would love to receive a postcard from wherever you live 📮 Open source is deeply rewarding, but sometimes I miss a physical reminder of the people on the other side of the wire ✨ Also, if you mention in the card making a donation to a US 501(c)(3) that aligns with my values, I will match it! Mailing addresses, both US and EU: https://filippo.io/#addresses

 Like

Liked Alex Russell (@slightlyoff@toot.cafe)
Post details
Stop defining "developer experience" as "the inner loop while I'm writing code after spending an hour installing node_modules". Setup time is "developer experience". Upgrade toil is "developer experience". Memoise-everything-after-weeks-debugging-stray-rerender toil is "developer experience". Belated, frantic code splitting side quests are "developer experience".

 Like

Liked Cat Hicks (@grimalkina@mastodon.social)
Post details
I don't know if I ever will stand up and talk about this practice in public, because it's a somewhat terrifying idea to imagine all the potential backlash or judgment idk, but if I did and everyone agreed, there is a GREAT talk I've imagined: "The Salary Ring." I'd describe these couple of years in my life when several of us joined together to support each other learning to negotiate, doing group market research, workshopping what we'd say in toxic situations together.

 Like

Liked Ana Rodrigues (@anarodrigues@front-end.social)
Post details
My no-nuance take on the recent discourse: I am not less than the other people in the IndieWeb community for not having a fancy, automated, cool setup on my personal website. Nobody has ever made me feel that way. It doesn't matter if all you have is a simple page with your name and email. If there is one place where you can do whatever you want and how you want is your personal website. I'm lucky to have found a community that supports this.

 Like

Liked Terence Eden (@Edent@mastodon.social)
Post details
In today's adventures of finding out weird things you can do with HTML… You should not put a `<style>` element anywhere other than the `<head>` So `<body><style> ...CSS...</style></body>` is an error. (It works, because browsers are tolerant.) But you *can* put a `<link rel="stylesheet">` element in a body. Obviously, that needs an *external* data source for the CSS. So you can cheat by Base64 encoding it! `<body><link rel="stylesheet" type="text/css" href="data:text/css;base64,LyoqCi…">`

 Like

Liked Jacky (is looking for work) (@jalcine@todon.eu)
Post details
Lukewarm take: using tabs instead of spaces isn't hard at all if you have a well-behaving editor. In my experience of a week now, it makes the resizing of code even a bit easier (you can make its width two spaces in more narrow views and expand it to four in larger ones). It sucks that it's hard to do this with Python. TBH it seems like it was a mistake for PEP8 to recommend (and in a way, enforce) the use of spaces. A bit of a "heated" discussion at https://stackoverflow.com/questions/120926/why-does-python-pep-8-strongly-recommend-spaces-over-tabs-for-indentation