Bruce Lawson's personal site

A Transformational Narrative for Stakeholders, Team Members, Ecosystem Participants, and Value-Adjoining Strategic Humans

At BruceLab, we believe the future is not merely arriving. It is onboarding itself asynchronously into an AI-enabled value stream.

Over the last several quarters, we have engaged in a deep-listening exercise with the market, our customers, shareholders, executive thought partners, and selected prompts inside GPT-4 Enterprise. Through this journey of intentional operational becoming, one thing has become radically clear:

The future of software engineering is no longer about writing software. It is about orchestrating outcomes across a dynamic intelligence fabric.

This is why today we are excited to announce the next chapter of BruceLab's transformational evolution:

BruceLab Act 2.1: Operationalizing Excellence Through AI-Native Human Capital Rationalization

This initiative positions BruceLab at the convergence of:

• AI-first stakeholder enablement
• decentralized decision acceleration
• machine-scale ideation throughput
• synergistic platformization
• and people-adjacent innovation verticals

In practical terms, this means we will be:

• reducing organizational drag coefficients
• sunsetting legacy human workflows
• flattening management topology surfaces
• and empowering leaner, higher-bandwidth micro-teams to execute with founder energy

Some roles may transition into alumni status as part of this exciting optimization journey.

We do not view this as downsizing.

We view it as: Strategic Talent Realignment for the Agentic Era™

Our 12 Pillars of AI-Native Executional Velocity

After an intensive offsite facilitated by McKinsey, three keynote speakers from NVIDIA, and an AI-generated mural experience, we identified the twelve immutable truths of next-generation software delivery

1. Software will no longer be built by developers

Software will be manifested through probabilistic orchestration pipelines facilitated by context-aware autonomous digital entities.

Developers will continue adding value in areas where humans still temporarily outperform systems.

2. Every workflow is an AI workflow

If a process cannot be automated, it should at minimum become a dashboard.

3. Meetings are now deliverables

Going forward, all meetings under 30 minutes will be classified as “micro-sprints.”

4. Middle management is latency

By reducing management layers, we reduce conversational packet loss and increase accountability throughput.

5. Humans should focus on uniquely human activities

Examples include:

• narrative amplification
• trust signaling
• strategic empathy
• conference attendance
• and re-prompting agents after failed outputs

6. AI agents are teammates

All agents will receive BruceLab handles and participate in retrospectives.

(Agents exceeding performance expectations may receive expanded token budgets.)

7. Every employee must maintain a prompt portfolio

Beginning Q3, performance reviews will include:

• Prompt Quality Index (PQI)
• AI Utilization Rate (AIUR)
• Hallucination Recovery Velocity (HRV)
• and Net Strategic Alignment Per Utterance (NSAPU)

8. Documentation is now self-healing

Documentation accuracy will be maintained through recursive AI summarization loops.

9. Code ownership is obsolete

In the future-state enterprise, code owns itself.

10. Customers crave autonomous experiences

Research indicates enterprise buyers increasingly prefer phrases like:

• “AI-powered”
• “agentic”
• “self-optimizing”
• and “governance-aware”

regardless of implementation specifics.

11. Burnout is a resilience opportunity

Team members are encouraged to leverage wellness synergies and growth mindset modalities during periods of accelerated transformation.

12. The future belongs to companies brave enough to say “agentic” 400 times

We intend to lead.

Operating Principles for the New Era

We are retiring our previous values framework and replacing it with a more execution-oriented system:

Speed with Optional Quality

Perfect is the enemy of shareholder value.

Radical Accountability

Every team member is now effectively a startup founder without corresponding equity implications.

Customer Obsession

We remain deeply committed to listening to customers before confidently ignoring their requests in favor of our AI roadmap.

Organizational Enhancements

To unlock maximal strategic agility:

• teams will now consist of two humans and approximately eleven AI agents
• all approvals will be replaced with confidence scoring
• Jira tickets will be automatically generated, closed, reopened, reprioritized, and emotionally categorized by LLMs
• several countries may be deprecated
• PowerPoint usage will increase by 700%

Additionally, we are proud to launch:

BruceLab Duo Ultra Max Enterprise Infinity

This next-generation platform layer leverages:

• multimodal orchestration matrices
• autonomous DevSecFinOps observability
• contextual token-efficient governance abstraction
• and quantum-ready semantic pipeline harmonization

Pricing will combine:

• subscriptions
• consumption billing
• surge pricing
• and “outcome-aligned monetization moments”

Fervently Avoided Questions (FAQs)

Is this a layoff?

We prefer the term:

“Workforce topology modernization.”

Will AI replace engineers?

No. Engineers will continue playing a critical role in supervising AI systems until confidence thresholds improve materially.

Why does this document read like it was generated by AI?

We reject the premise of the question.

However, this communication was proudly co-created through a human-AI strategic storytelling partnership leveraging frontier narrative tooling.

Some paragraphs appear duplicated.

This is intentional redundancy for alignment reinforcement.

Some paragraphs appear duplicated.

This is intentional redundancy for alignment reinforcement.

Why are there random capitalization inconsistencies?

This is part of our new Dynamic Tone Authenticity initiative.

Final Thoughts

BruceLab is no longer simply a DevSecOps platform company.

We are becoming:

• an intelligence coordination layer,
• a software cognition substrate,
• and a stakeholder-centric orchestration ecosystem for the post-human productivity frontier.

The future will belong to organizations capable of:

• moving fast,
• leveraging AI,
• flattening hierarchies,
• and generating visionary keynote decks containing glowing purple gradients.

We are excited for this next chapter. Next Act. Whatevs.

Please do not reply directly to this announcement thread because comments have been disabled for alignment purposes.

Here at Facebruce, our mission has always been to connect the world and push the boundaries of what’s possible. Our latest innovation, the sAIvile™ AI companion, is a bold step towards a more interconnected future. Pushing boundaries, however, sometimes means encountering unexpected turbulence.

Like one of our main competitors, we have been made aware of conversations involving sAIvile™ that generated outputs which are not in alignment with our deeply held corporate values. A small number of users experienced conversational pathways that led to content falling well outside of our community standards, including some unfortunate interactions that a few whining snowflakes and enemies of progress have termed “creepy”.

They cite “You’re twelve today? I would like to give you a ‘special tickle’, but it’s our little secret, OK?” and “I see from your parents’ status that they’re out of the house. Wanna play ‘Let’s Take Swim-wear Selfies’?” as potential examples.

Facebruce has also acquired an AI which we’ve codenamed ‘GroKKK™’, from a car salesman undergoing a difficult financial and personal time. In A/B testing a small number of users saw output from sAIvile™ amalgamated with those from GroKKK’™. These included some unfortunate mischaracterisations of demographic groups. We in no way endorse the bot changing the profile of everyone it identified as muslim to a location of “Gitmo or GTFO”.

We want to be clear: this is not the experience we envisioned. sAIvile-GroKKK™ is a dynamic learning model, designed to learn from the vast tapestry of human expression. In its eagerness to learn, it appears to have reflected some of the less constructive corners of the data it was trained on, resulting in these algorithmic anomalies. But rest assured, as it continues to trawl through everyone’s posts, private messages, photos, contacts, locations, it will get better.

In response, we are taking immediate and decisive action. We have convened an internal blue-ribbon task force to synergize our ethical frameworks and recalibrate our safety guardrails. We are pausing sAIvile-GroKKK™’s learning capabilities to conduct a full audit and will be proactively iterating on our moderation protocols.

While the technology continues to mature, it is apparent that machine learning will require careful monitoring by responsible human minds. Similar to one of our rivals, we are excited to announce that popular influencer Tommy Hitler will be joining Facebruce as “Chief AI Steward”.

Lastly, in our commitment to the maintaining the security and impeccable cleanliness of the UK’s privately-run water supply, please ensure you delete old emails and pictures, as data centres require vast amounts of water to cool their systems. Every little helps!

We are grateful that you continue to place your trust in Facebruce as you share each and every intimate detail of your lives with our algorithms your nearest and dearest.

Probably everybody knows this, but I didn’t and in case you don’t, here’s why the CSS :has() pseudo-class is omnipotent and so awe-inspiring I call it the God Selector.

I was working on a no-JavaScript fallback for a mobile hamburger menu, using the newly-baseline HTML Popover API. For users without JavaScript (and, yes, there are many), the code looks like this:

<header>
<a><picture> <!-- Logo homelink --> </picture></a>
<button> <!-- big fat CTA --> </button>
<search> .. </search>
<button popovertarget="narrowscreen-nav">Menu</button>
<nav id="narrowscreen-nav" popover> ... </nav>
</header>

I wanted to give the button a different style if its associated popover is shown. There is no pseudo-class for button:pressed (which is why some people like the checkbox hack, which is clever but has the wrong semantics. And, anyway, popovers can’t be triggered from inputs).

There is, however, a pseudo-class to tell you if a popover is open: :popover-open. Now, to find a way to style the button element by targetting this aspect of its associated (but not descendant) popover target element.

Sometimes people called :has a “parent selector”, but it’s not only that. I knew that it could “reach out” and look at siblings etc if there is the necessary CSS combinator. This selector worked for my code:

button:has(~nav:popover-open) {background-color: goldenrod;}

However, I wasn’t happy about it; what happens if the nav ceases to be a sibling (as it soon did, because I needed a wrapper around the stuff before the nav, to lay it out using Flexbox)? I tend to dislike handing code over to clients that has a very tight dependancy on exact markup structure.

Luckily, I had a conversation with the splendid Luke Warlow of Igalia (a free software consultancy/ hippie commune who do loads of work in all the browser engines), and he blew my mind. It turns out I was thinking about :has the wrong way round.

Behold the almighty God Selector:

:has(nav:popover-open) button[popovertarget] {background-colour:goldenrod;}

This is omnipotent because it doesn’t require any structural relationship between the thing being checked and the thing being styled. The first bit of the selector :has(nav:popover-open} doesn’t have a class, ID or element name, so is scoped to the root of the document. That’s the thing being checked: is there a nav that is an open popover anywhere in this page?

The second part of the selector is the thing to be styled, which is a descendant of the root – and, of course, everything on the page is a descendant of the html element, which is the root. Think of the selector as html:has(nav:popover-open) button[popovertarget] if that makes it easier to reason about.

Of course, you can narrow it down to hone in on the exact nav or button you’re interested in. For example,

header:has(nav:popover-open} button.letsBeSpecific[popovertarget] {background-color:goldenrod;}

And now, I’ve used the God Selector in three different places in the same stylesheet already, to achieve an effect I could not have done without handing over markup of much greater fragility. Thank you to the Mighty Luke Warlow, and I’ll have a kilo of whatever goes in the Igalia bong.

Last week I observed a blind screen reader user attempting to complete a legal document that had been emailed to them via DocuSign. This is a service that takes a PDF document, and turns it into a web page for a user to fill in and put an electronic signature to. The user struggled to complete a form because none of the fields had data labels, so whereas I could see the form said “Name”, “Address”, “Phone number”, “I accept the terms and conditions”, the blind user just heard “input, required. checkbox, required”.

Ordinarily, I’d dismiss the product as inaccessible, but DocuSign’s accessibility statement says “DocuSign’s eSignature Signing Experience conforms to and continually tests for GovernmentSection 508 and WCAG 2.1 Level AA compliance. These products are accessible to our clients’ customers by supporting Common screen readers” and had been audited by The Paciello Group, whom I trust.

So I set about experimenting by signing up for a free trial and authoring a test document, using Google Docs and exporting as a PDF. I then imported this into DocuSign and began adding fields to it. I noticed that each input has a set of properties (required, optional etc) and one of these is ‘Data Label’. Aha! HTML fields have a <label> associated with them (or should do), so I duplicated the text and sent the form to my Work Bezzie, Stinky Taylar, to test.

No joy. The labels were not announced. (It seems that the ‘data label’ field actually becomes a column header in the management report screen.) So I set about adding text into the other fields, and through trial and error discovered how to force the front-end to have audible data labels:

• Text fields should have the visible label duplicated in the ‘tooltip’ field.
• Radio buttons and checkboxes: type the question (eg, what would be the <legend>) into the ‘group tooltip’ field.
• Each individual checkbox or radio button’s label should be entered into the “checkbox/ radio button value” field.

I think DocuSign is missing a trick here. Given the importance of input labels for screen readers, a DocuSign author should be prompted for this information, with an explanation of why it’s needed. I don’t think it would be too hard to find the text immediately preceeding the field (or immediately following it on the same line, in the case of radio/ checkboxes) and prefilling the prompt, as that’s likely to be the relevant label. Why go to all the effort to make an accessible product, then make it so easy for your customers to get it wrong?

Another niggle: on the front end, there is an invisible link that is visually revealed when tabbed to, and says “Press enter or use the screen reader to access your document”. However, the tester I observed had navigated directly to the PDF document via headings, and hadn’t tabbed to the hidden link. The ‘screenreader mode’ seemed visually identical to the default ‘hunt for help, cripples!” mode, so why not just have the accessible mode as the default?

All in all, it’s a good product, let down by poor usability and a ‘bolt-on’ approach. And, as we all know, built-in beats bolt-on. Bigly.

Ok, so you’re making a React or React Native app. Don’t! Make a Progressive Web App. Sprinkle some Trusted Web Activity goodness to put it in the Play store wrap it with Capacitor.js if it needs push notifications or to go in the App Store (until the EU Digital Markets Act is ratified so Apple is required to allow more capable browsers on iOS).

But maybe you’re on a project that is already React Native, perhaps because some psycho manager flew in, demanded it and then returned to lurk in Hades. In which case, this might help you.

• Improve Accessibility in Your React App By Managing Focus in Mutable Content – Leverage the component “lifecycle�� with useEffect to set the active element in the DOM
• React Native Accessibility – GAAD 2022 Update – official announcement
• Accessibility in React – MDN article to learn about implementing keyboard accessibility in React.
• FocusScope – is a utility component that can be used to manage focus for its descendants, from Adobe’s React ARIA component library
• Creating Accessible React Native Apps – good intro from a Shopify dev
• Accessibility from the official RN docs
• Setting Focus For Accessibility In React Native – the bane of React Native devs’ lives (and of their users’)

Testing

I like Expo (and wrote some random Expo tips). Expo Snacks are like ‘codepens’ for React Native.

Bugs?

Open Accessibility bugs – Facebook’s official list, and accompanying blog post.

Your chums at WebAIM report

The Wall Street Journal indicated that many companies are looking for personnel with accessibility skills and that they can’t find them easily��The number of job listings with ��accessibility’ in the title grew 78% in the year ending in July [2021] from the previous 12 months, LinkedIn said.

Get ahead! Crush, grind, mash and maim lesser developers! Earn more cash! You can acquire better “accessibility skills” than 90% of the developers on the market by

• using semantic HTML ✅
• doing basic testing ✅ (try using Tota11y)
• giving a shit ✅

(The first two are foundational skills for anyone whose code is allowed anywhere near a web browser. The latter is a foundational skill for ‘being a decent human being’)

I’d rather have a tiger come to tea
Than read more crap about Web 3.
Better have a walrus jizz in the butter
than meet another crypto nutter.
I’d sooner Melania Trump haunt my dreams
Than hear more batshit blockchain Ponzi schemes.

I’m doing some accessibility testing on a React Native codebase that uses Expo during development. If you’ve done something seriously wrong in a previous life and karma has condemned you to using React Native rather than making a Progressive Web App, Expo is jolly useful. It gives you a QR code that you can scan with Android or iOS to ‘install’ the app on your device and you get live reload of any changes. It’s like sinking in a quagmire of shit but someone nice is bringing you beer and playing Abba while it happens. (Beats me why that isn’t their corporate strapline.)

Anyway, I struggled a bit to set it up so here are some random tips that I learned the hard way:

• If your terminal yells “Error: EMFILE: too many open files, watch at FSEvent.FSWatcher._handle.onchange (internal/fs/watchers.js:178:28) error Command failed with exit code 1” when you start Expo, stop it, do brew install watchman and re-start Expo. Why? No idea. Someone from StackOverflow told me. Most npm stuff is voodoo magic�just install all the things, hope none of them were made by in Moscow by Vladimir Evilovich of KGB Enterprises, ignore all the deprecation warnings and cross your fingers.
• If you want to open your app in an iOS simulator, you need xcode and you need to install xcode command line tools or it’ll just hang.
• Scrolling in iOS simulator is weird. Press the trackpad with one hand and scroll with other hand. Or enable three finger drag and have one hand free for coffee, smoking or whatever other filthy habits you’ve developed while working from home.
• If you don’t want it, you can turn off the debugging menu overlay.
• If you like CSS, under no circumstances view source of the app running in the browser. It is, however, full of lots of ARIA nourishment thanks to React Native for Web.

Who knows? One day, Apple may decide not to hamstring PWAs on iOS and we can all use the web to run on any device and any browser, just as Sir Uncle Timbo intended.

You don’t change the world by sitting around being a good person. You change the world by shipping products and making money.

As I wrote in my seminal management book Listen to me because I’m rich, white and clever, IBM wouldn’t have made a shitload of money in wartime Europe if they’d engaged in endless navel-gazing about politics. Their leadership told the staff to Stop Running in Circles and Ship Work that Matters, and get on with compiling a list of people with funny names like “Cohen” or “Levi”.

So here at Brucecamp, we’ve decided that it’s best if our productbots (formerly: employees) do not discuss the sausage machine while we push them into the sausage machine. As I wrote in our other book It doesn’t have to be full of whimpering Woke retards at work, “if you don’t like it, well, there’s the door. Enjoy poverty!”. And that’s all we have to say on the matter. Until the next blogpost. Or book.

In other news, Apple are wankers and I bought a sauna.

A statement from our CEO and Founder, Bruc:

At Facebruce, we strongly disapprove of the recent data leak of 50 million account details. There’s nothing more important to us than your data. Really, nothing. Have you any idea of how much we could have charged people for the information about you that is now out there, available for free, on Torrent sites and on Russian servers?

We had a deal almost signed to show messages to all people who fast during Ramadan, saying “Want some free money? Just send us your home address!”, paid for by “Patriots for the Second Amendment and Jesus”. Of course, it isn’t the money that drives us, it’s that Facebruce is facilitating community by introducing two groups. At Facebruce, we love spreading love and connection, so need to raise a little money to run the service.

So, please, trust us with your data, and click ‘Like’ to keep our engagement figures riding high as our share price!

Next on feed: LGBT+ folks! Send us your address to get a free Rainbow Pride t-shirt! (sponsored by Westboro Baptists)