Derek Featherstone

AI x Accessibility Builder & Strategist. Author. Speaker. Teacher. #Woodworking

[Derek Featherstone @feather]

@TheXSami Exactly that -- and it's almost a good litmus test for "did I/my agents document this well enough?"

[Derek Featherstone @feather]

Working with AI → the rate of change is immense, and keeping up is difficult. One of the key tenets of the systems I'm building is resilience to change: key components being "swappable". Like the LLM. Or a CRM. Or an automated accessibility checker. Or... well, you get the idea.

[Derek Featherstone @feather]

After about 5 hours running my personal OS with Opencode and Sol 6.1 as the LLM, I have come to some conclusions:

- nothing is load-bearing or doing the heavy lifting
- nothing is worth noting
- nothing is actually different

And, given that there have been no "It's not X, it's Y" statements... it must, in fact, actually be X.

#MindBlown #AI #humour

[Derek Featherstone @feather]

One of the best things I’ve read or heard this year was Peter Bell saying in a LinkedIn live something along the lines of:

“Use LLMs to write code to replace themselves”

It changed the way that I thought about and architected the systems I was building.

It’s a great way to force yourself to think more clearly about what it is that you’re building, what needs an LLM’s judgment, and what can/should be code.

[Derek Featherstone @feather]

What I don’t understand is how millions of reviews, returns, and similar customer orders has ANYTHING to do with my “recommended shoe size” :)

The signal for my recommended shoe SIZE should be purely about the shoes I have purchased, reviewed, returned, etc. Other aspects of the shoe? Sure, maybe let them be influenced by other factors. But definitely NOT size.

[Derek Featherstone @feather]

I'm tempted to take it to another level: every instruction that I create to have an agent run the system is something that is well documented such that another human could run it themselves :)

[Derek Featherstone @feather]

I decided to see if I can get my Claude Code/Opus/Obsidian Vault setup running on OpenCode/Sol 6.1/Obsidian Vault.

After I get that running properly, I'll aim for the ability to use local inference rather than a cloud service.

So far, so good.

[Derek Featherstone @feather]

ENERGIZED!!

That's how I felt after speaking at an internal conference on Thursday. My talk was "Accessibility & Inclusion in the Age of the Builder". Wow, I'd forgotten how much I love presenting at events. Wonderful hosts that placed their trust in me to share my experience and perspectives.

Yes, it was virtual. That's not my favourite, but I still love being in the moment and connecting with people as best as we can over the internets.

I took a look at what's different now than about 10 years ago (when I spoke at the very same event). How do we ensure we're scaling inclusion and not exclusion? (people is the answer). So many programs are built on people, process, and tools → what's changed? Process and tools. What's stayed the same? People. So much has changed, and so much has stayed the same. And... importantly, how do we chart a path forward, and who should be the authors that shape the direction we head? Also people.

There's a pattern there.

[Derek Featherstone @feather]

@davidsven A concerning number of smart glasses, but... not at all surprising? :)

[Derek Featherstone @feather]

Accessibility doesn’t take longer JUST because it’s accessibility.

It takes longer because you’re learning new things:

New techniques, new processes, new things to consider, new insights from working with people with disabilities, new measures of success.

[Derek Featherstone @feather]

@rachelnabors Just sent over some via DM → let me know if you want to run through it together or just catch up :)

[Derek Featherstone @feather]

When you're asked the question "How do we make this accessible?" try responding with a whole bunch of questions before responding with a whole bunch of answers.

#accessibility #a11y #UX #design

[Derek Featherstone @feather]

The best time to get started on accessibility for your project is before it started.

The second best time is now.

[Derek Featherstone @feather]

Accessibility itself IS NOT hard.

But, accessibility at scale IS hard.
Doing accessibility consistently well IS hard.
Accessibility where it hasn't been done before IS hard.
Creating a culture that values accessibility IS hard.

Don't confuse one with the other.

[Derek Featherstone @feather]

@rachelnabors Will do for sure! How would you like to receive my commentary/feedback/questions?

[Derek Featherstone @feather]

@janisveryklug Yes, exactly that... Say more about that project -- sounds interesting!

[Derek Featherstone @feather]

Designing for extremes makes experiences better for everyone.

I have Claude Code setup to connect via remote control by default. Then I can check in on my terminal sessions while on my phone.

[Derek Featherstone @feather]

I share my thinking about these types of topics all the time, and you can enjoy them on my list, algorithm free...
https://t.co/4YdjMgyVHZ

[Derek Featherstone @feather]

Here's the latest approach I've been taking to autonomous work that gets authorized and queued up for my agents to work on.

[Derek Featherstone @feather]

My goals? Increase the portion that can run autonomously over time. Increase parallelization.

Just getting started, but really liking how this is going so far.