mastodon 4.7.3Hey hey! I'm René, and I make things. Using tech like Python/pygame, C, golang, JavaScript/TypeScript, React, Kubernetes, Linux and such. I ❤️ data audio reactive video synths, and book smell.
(Always a student, always a teacher, employed by Microsoft, toots are my own. Dungeons AND Dragons, They/them, sustainability volunteer, drawing, human things humans do, and such like)
Monopoly, but you start with nothing.
One billionaire player has 95% of the board. They also control what cards get handed out. Plus they know what you’re doing.
The billionaire player has convinced the rest of the players to fight each other and takes 50% of their moves each round whilst they pay only 1% of their moves each round.
Unfortunately the only house left costs you a lifetime of playing monopoly to buy.
How do you win?
Every time I fix issues for screen readers, it ALWAYS ends up making the component better for everyone else. Often it's missing states, clunky form controls, and bugs.
For example in this latest one:
- an auto complete was messed up searching on wrong values
- missing states for logged in / checking logged in
- wrong busy states when loading other things
- keyboard works much better
It's improved for developers/maintainers too because there's now tests and story states.
@otfrom@functional.cafe I like to imagine the designers are beside the beach wearing their black turtlenecks kicking around a hacky sack…
ok we keep going and whatever we get up to that is the number of tabs that are allowed!
Funny, “hand made” parser made with a bunch of examples slowly building up the parser and unit tests one by one. With debug info built into the generation tool, to capture any failing input. Then based on those making a bunch more synthetic examples. Now the parser is up to about 100KB of code with 1000+ generated unit tests and 20 real (once) failing input examples and 45 synthetic examples. Every time I see there’s a failure whilst using it, I just plop the example in and the parser updates.
Found a couple of nice tools for #a11y web issues.
Guidepup, has a virtual screen reader for writing SR tests in CI. Works with voiceover/nvda too.
A storybook based “axe” testing library, which renders all your story states and checks them with axe. No extra work needed (assuming you’ve already generated many states).
Playwright to do exploratory testing running through checklists automatically.
Anyway, so far they are catching things other techniques didn’t. A lot of it automagically.
So, there’s these mushroom memory articles and videos popping up. Basically quoting a pop sci article covering a US based paper on using mushrooms for memresistors.
https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0328965
All coverage I saw was talking about how they could be used for ram or so. Not processing. Memresistors can do processing too!
2ndly, coverage represents this is a new discovery. But anyone who takes part in the asian science world knows this has been a topic for over a decade now. Paper cites well.
https://www-cs-faculty.stanford.edu/~knuth/papers/claude-cycles.pdf
The Knuth paper is worth reading. It shows the social interactions of people working on a problem together. It’s fun.
Glad yoga saved some weeks of toil. Maybe we’ll get that next volume after all? lol
Humans using agents to work through problems from different angles together is where it shines. Try 30 different approaches, measure, prove. Ideas sparking not hindered by the toil. The creativity and social co-working together making it fun and better.
Unabashed Redox OS fan. Living vicariously through the monthly updates.
First time tet/chinese new year and carnival aligned in over 50 years. Big time celebrations.
Perhaps up to 2.5 billion people combined celebrating.