Throughout most of my life I've lost something maybe once. In the last two weeks, I've lost two things already. And to the point of not even being able to tell when they "disappeared" — I was convinced I have them on me until I've noticed they're gone. I feel like I was losing my mind.
It doesn't help that I was raised to feel guilty about my mistakes. It doesn't help that people around me take this lightly (it's nothing "important"), so I also feel guilty about feeling guilty. And completely estranged.
#ActuallyAutistic
Apologies for the earlier post. Someone pointed out the mistake and I deleted it. I realized it probably came across as news. It was not news. I definitely need to post more carefully, sorry if there was any confusion.
I bet it's really difficult to get a profile pic like that when you lack a spine. Probably a whole elaborate system behind him holding his head upright.
https://bsky.app/profile/did:plc:jl6bnuiemddpm3orm2kcedxh/post/3miw3zs3dak2f
🇺🇦 #NowPlaying on KEXP's #AfternoonShow
IDLES:
🎵 I'm Scum
#IDLES
https://idlesband.bandcamp.com/track/im-scum
https://open.spotify.com/track/0mXDySw7m2OXK6Wd9hc9Js
Signal Privacy – Better Than You Thought
If you’ve ever tried to write a secure and private distributed communications protocol, you know how hard it is to get it right. (If you have, you are seriously nerdy!) It is really easy to make mistakes, even for professional security developers. So, when Guy Kawasaki mentioned the Signal “Double Ratchet” protocol I was intrigued. I thought I knew a lot about security protocols but this one caught me flat-footed. Down the rabbit hole I went.
@… not rw by default in single user mode.
I usually:
mount -uw /
(I can't remember where I learnt that variant. Lost in the mists of time.)
@…
I'm at @… for Mesh Night tonight. We'll be here for at least a few hours. Stop by if you're in Montreal and curious about #meshtastic , #meshcore , or
from my link log —
6 things Markdown got wrong.
https://www.swyx.io/writing/markdown-mistakes/
saved 2020-04-04 https://dotat.at/…
The real talk is I use claude code all day at work because I didn't want to loose my job and every developer at my company that started using it was accomplishing more things faster.
It feels bad to say but it often codes better and faster then I ever have and can look at dependencies to understand how they work faster then I ever could.
I'm lucky I know code well enough to see where it has made mistakes. I'm lucky to have a job.
Put your name on your work and find like-minded people to share credit with. It is now on you to build not your brand, but the demonstration that you know what's going on.
It is going to be very hard to get a job by printing a list of skills at the top of your resume and hoping to get noticed. It already was and now it's worse than ever.
Be a person on the internet and by that I mean do not hide your person-hood. Your curiosity, your learning, your willingness to consider angles. Professional polish is something the clankers do better than us, because they are trained on all of us doing it.
If not putting your name on your learning, put a stable pseudonym out there. Be known by the work you do and even the mistakes you make and reconsider. Showing that your knowledge has _depth_ is now one of the most important things. We can all vibe up to a basic understanding. It's the people who can see where they went wrong, and course-correct that really are going to carry the day.
You no longer get to be perfect and only show what's finished and polished. And you're gonna have to show your work.