On the 18th May the accessibility team at Solirius ran their first ever Global Accessibility Awareness Day (GAAD) event. Thanks to all who attended and those who contributed in the planning and del...

On the 19th June the Engineering Management chapter will be joining the Leading with AI - The London Edition event with a panel discussion on the impact of AI on modern Engineering Management. You ...

Judy and Clare trade spicy hot takes, from notification overload and 'done > perfect' learning, to a passionate deep dive on accessibility as a moral (and business) imperative.

San Francisco depot is a mnemonic for the SFDPO software exploratory testing heuristic. SFDPO stands for Structure, Function, Data, Platform and Operations. Each of these represents a different aspect of a software product.StructureStructure is what the product is. This is its physical files, utility programs, physical materials, etc. FunctionFunction is what the product does. This is like the product's functional requirements. How does it handle errors? What is its UI? How does it interface with the operating system? DataData is what the product processes. What kinds of input does it process? This can be input from the user, the file system, etc. What kind of output or reports does it generate? Does it come with default data? Is any of its input sensitive to timing or sequencing? PlatformPlatform is what the product depends upon. What operating systems, browsers, runtime libraries, etc. does it run on? Does the user need to configure the environment? Does it depend on third-party components? OperationsOperations are scenarios in which the product will be used. Who are the application's users? Where and how will they use it?

Software development is inherently discriminatory because we know about digital accessibility and still don't do it. We have the knowledge, the skills, and the moral imperative to include all ...

A mnemonic (pronounced ni-mon-ik) is a tool or technique used to aid human memory

Oleksandr said: My hot take of the week: If you don't fully understand the thing you want to test and measure - you might get the results that are surprising but yet mysterious. So - first - unders...

Inspired by Clare Norman's recent lightning learning sessions. A speaker pulled out last minute so a developer stepped in to share what they've been working on. While Clare pointed out that it's no...

The question of who actually benefits from a productivity gain. In an AI context, if a developer produces ten times more output using AI tools, value capture describes whether that surplus flows to the employer (in the form of more work for the same pay), to the employee (in the form of reduced hours for the same pay), or is divided somewhere in between. The term frames productivity improvements not as neutral gains but as contested resources, with company and worker pulling in opposite directions over who keeps the benefit.

A metaphor for the way AI-assisted work drains human energy without commensurate reward. When workers adopt AI tools that dramatically increase output, but employers absorb most or all of the productivity gain, the worker is left exhausted with nothing to show for it. The term draws on the "energy vampire" archetype: proximity to the source is what depletes you, not direct harm. Common manifestations include compulsive overworking driven by the addictive feedback loop of agentic coding tools, and organisational pressure to sustain AI-boosted output as a new baseline indefinitely.