IndieWeb post types

This content type is full of IndieWeb post types, which are all content types which allow me to take greater ownership of my own data. These are likely unrelated to my blog posts. You can find a better breakdown by actual post kind below:

 Like

Liked Alex Wilson (@probablyfine@tech.lgbt)
Post details
After a long hiatus, I have enough time and headspace to start maintaining adr-viewer again. I spent some time this weekend merging contributor PRs, clearing out old stuff (Travis CI who?), and setting up automated releases. 1.4.0rc1 is now on PyPI and I'm looking forward to giving this project the attention it deserves again. #python https://github.com/mrwilson/adr-viewer

by Jamie Tanna's profile image Jamie Tanna .

 Like

Liked Another Angry Woman (@stavvers@masto.ai)
Post details
genuinely fascinated by the wework collapse because they genuinely could have dominated the covid hybrid working trend by simply offering to businesses that they could have an office for that one day a week lease and they just... didn't. and kept trying to sell individuals a hot desk. literally everyone who has the money is spectacularly bad at reading the room on post 2020 working preferences

by Jamie Tanna's profile image Jamie Tanna .

 Repost

Reposted Allie R. πŸ³οΈβ€βš§οΈ (@grissallia@aus.social)
Post details
A little professional story: Please be kind when "correcting" co-workers about something you feel they've misunderstood or are just wrong about. One of the really weird things in my life is that I seem to encounter -or trigger- edge cases. For non-technical folks: an "edge case" is a generally rare bug that only occurs under a very particular set of circumstances, usually quite obscure. Someone might report a bug that no-one can reproduce, and it turns out that the bug only occurs on the last Friday of the month, if the device is used between 9pm and 10pm. We refer to something like that as an "edge case". A few years ago I found a *really* weird bug in one of our products, and I mentioned it to one of our senior developers. That person then proceeded to loudly, and in front of an entire group of co-workers, lambast me for something that was OBVIOUSLY end-user error, and was "fundamentally impossible" to be anything else. It was one of the most humiliating professional experiences of my life. It made me incredibly wary of raising Jira tickets, unless I could fully reproduce and document a bug. A couple of years after this incident, I was chatting with another dev who'd started working with our company, and was in QA, and he mentioned this edge case he'd recently encountered. If condition A, and condition B, and condition C, AND condition D were all met, it would trigger this really weird bug. ...the same one I'd mentioned to one of our senior devs a couple of years earlier. It wasn't end-user error. It was an edge case. [sigh] Yesterday during our weekly technical meeting, I asked a question as to whether an underlying software process had been significantly & quietly changed recently. I explained that I'd encountered a number of weird incidents over the past couple of months, but nothing I could log or document, just that I had a gut feel that there's a intermittent bug in play, and that after my 15-hour day on Wednesday, I was now almost certain that changes might have occurred in that particular process. Turns out that entire process had been rewritten. I was asked why I hadn't raised any Jira tickets for it. Our dev team could have had a couple of months headstart on this issue, and documented occurrences of it, if a deeply frustrated and under-pressure dev hadn't publicly ripped me a new arsehole five years ago. Everything is copacetic. No-one is upset with me, the dev who asked me why I hadn't raised the ticket was the QA dev, and all I had to say was "Bug X", and we both laughed, and the dev team gets more of my "gut feel" bug reports moving forward. The other dev and I are on excellent terms these days as well. I went to the mat with them three years ago, and they apologised, and we talked out our differences, and we have a great working relationship now. How you treat people matters, even in a moment of deep frustration, and can have long-term consequences in ways that you may not expect. Be kind. Always.

by Jamie Tanna's profile image Jamie Tanna .

 Like

Liked Franck Leroy (@FranckLeroy@mastodon.online)
Post details
Exactly 14 years ago , Satoshi Nakamoto designed the most pathetic / inefficient system ever invented by humankind : the blockchain. Today, it weights 60 000 tons, wastes constantly 10 gigawatts (more than Belgium or Chile) to process less than 7 transactions per second : Less than a 33 bps modem from 1990. This could be a joke if it didn't have such gigantic environmental impact, wasn't enabling billion dollars ransomware industry and was not crushing thousands of lives in the process.

by Jamie Tanna's profile image Jamie Tanna .

 Like

Liked Bodil (@bodil@treehouse.systems)
Post details
Idk why everyone is talking about gender segregation in chess today (and I don't care, so don't answer), but it's interesting to see the discussion veering accidentally close to the real question, which is "why is any competition gender segregated?" Is it 1) because men are obviously superior to women so it would be unfair to women to make them compete with men? Or maybe it's 2) the patriarchy dictates that a man must never have to lose to a woman. It's a mystery.

by Jamie Tanna's profile image Jamie Tanna .

 Like

Liked Introducing Open Ideas by @edent 
Post details
As previously mentioned, I quit my job. So now I'm no longer working for The Man. Instead, I am working for a man. Specifically: me1. I've launched Open Ideas Ltd. It's a bespoke computing consultancy …

by Jamie Tanna's profile image Jamie Tanna .