Nathan Heffley @nathan@heffley.social

Deeply in love with these AI powered spam bots by @neilmendoza !

It seems almost too absurd to be real, but I've been in many tens of meetings where some director/VP repeatedly insists on assigning work items and taking action immediately instead of spending a few days or weeks understanding the problem, which often ends up costing an entire team or large fraction of an org quarters to years doing something worthless or even negative value.

By revealed preference, leadership often prefers having a roadmap, deliverables, etc., to actually solving the problem.

People, please start using CamelCase (aka PascalCase) to break apart words in #HashTags.

It makes it easier to read and more #accessible. Single words are OK to keep lowercase, unless they are proper nouns 😉
It makes it easier to review if you're a #MastoAdmin.

#CamelCaseAllTheHashTags

#Mastodon #HashTag #accessibility

@jamesbritt also shared you can #Use_The_Underbar!

@blindscribe says: https://www.accessible-social.com/copy-and-formatting/hashtags

Please #boost this for visibility and to help improve the lives of many people.

LastPass breach update: the attacker got (encrypted) vaults.

If you have users with weak vault passwords, now’s the time to change any creds those users had access to, and of course enable 2FA everywhere it wasn’t already. #infosec #security https://blog.lastpass.com/2022/12/notice-of-recent-security-incident/

I know $12 USD is a lot of money for some people, so to celebrate 1000 sales, I'm giving away 1000 copies of The Pocket Guide to Debugging (honour system: please only use the free link if you can't afford $12!)

Here’s the link, use code BUYONEGIVEONE at checkout to get a free copy https://store.wizardzines.com/products/the-pocket-guide-to-debugging-pdf

(I can't disable the billing address prompt but you can just enter a fake address like 123 Fake st, new york NY 12345, (123) 123 4567 :))

Twitter introduces its new icon/badges and of course they cannot be distinguished from one another by color blind people because Twitter laid off everyone who thinks about accessibility in design.

https://twitter.com/TwitterSupport/status/1604955466727047168

Interesting to see Twitter regularly have incidents during peak load hours (https://twitter.com/danluu/status/1518677214035726341), e.g., here's downdetector for the past two days.

When Twitter had 2 DCs, this used to be quite rare outside of failover tests, which effectively doubled load. Most failover tests would pass without incident, implying Twitter could handle > 2x normal load, so of course the site would rarely have non-failover load issues.

But now it's normal to have an incident on a random weekday.

🔗 Always use [closed, open) intervals
https://fhur.me/posts/always-use-closed-open-intervals
#best-practices

One of the things that I think is sad about the decimation of Twitter eng is that Twitter was doing a lot of interesting (and high ROI) eng work that, at younger companies, is mostly outsourced at great cost.

A few examples off the top of my head:

The now gutted HWENG group was so good at server design that, in a meeting with Intel, the Intel folks couldn't believe the power envelope Twitter achieved and Google thought we were lying about our costs during cloud price negotiations.

Hello web devs, @SaraSoueidan has started taking pre-orders for her #PraticalA11y course at https://practical-accessibility.today/. This course is going to be amazing!! Highly recommend. I have already pre-ordered myself.

Finding #pest much more intuitive than #phpunit. Almost enjoyable! JS on the other hand gave me grief today. Tomorrow is another day. 🤪

as sad as i am about the rapid destruction of twitter, the (re)surge in blogs and newsletters has been lovely

back to the #indieweb!