Conflicts of interest and war profiteering hidden until after the election. The new Congress needs to subpoena this guy and everyone around him to testify under oath.

apple.news/AV2GpcUqn…


Here’s why everything broke: “L3Harris proposed to do the installation during the day—a busy time for flying. The FAA approved the move and conducted a routine risk assessment for such work, the people said.“

apple.news/AkGQvdUHT…


Given the disaster that 3rd country deportations from the U.S. have been, it’s very disappointing to see multiple EU countries pursue the same failed scheme as the U.K. with the same destination: Rwanda.

aje.news/4r1il7


It only requires 4 justices for cert, so at least 4 of the SCOTUS 6 want to rule to preserve the remainder of Trump’s imperial presidency. I fully expect the same conservative majority aiding and abetting 3rd country removals will rule in Trump’s favor.

apple.news/AvMipQ6Qw…


Not sure how viable an idea this is, but I hope the incoming Democratic majority legislates defunding of the mass deportation efforts.

apple.news/Adb5rMKcG…


Chris Christie has resurfaced to drag JD Vance for filth for backing Vivek’s nasty ad. It’s obviously him maneuvering for a role in the post-Trump GOP. But the North remembers he helped usher Trump in to start with.

apple.news/Aq2yjwoKu…


Speak out against ICE when their incompetence and cruelty kills your spouse, and they try to make your child an orphan by deporting you.

apple.news/AqKFVT14q…


Just one more way the Trump administration continues to actively harm military veterans.

apple.news/A0icMJmRv…


It was only a matter of time before the Trump administration’s blood libel of Haitians could be measured in financial terms as well as moral ones. Springfield’s economy has taken a nosedive.

apple.news/Aw7_nMx7_…


The AI-induced memory shortage has apparently gotten to the point that it may force public schools to go lower-tech.

apple.news/ACyo5Cny2…


Tom Nichols is a self-identified Never Trumper who thinks he’s helping with pieces like this. He isn’t. There isn’t a single good idea to be salvaged from the speech of an unqualified drunk who has resegregated the military the way Hegseth has.

apple.news/AiItwgbo9…


Arizona State continues to protect their hockey coaching staff instead of the team’s players. 21-year-old Matthew Mayich will never recover from the heatstroke caused by a workout that both the head coach and the assistant replacing him observed.

apple.news/A-EwaCBMI…


The man behind so-called “3rd country deportations” (government-sponsored human trafficking in my view) is Trump’s nominee for ambassador to Cameroon.

apple.news/AdkwaIXoM…


apple.news/An5fZgnVH… an interesting window into the priorities of the Trump administration.


Building a Code-Along Tutorial with AI (Part 2)

When I reached step 6 (Scheduling) of bluesky-pipeline-tutorial-v4.md, I chose Option A.  Instead of keeping a Terminal or iTerm window open, or using pm2,  I decided to use a Docker container running in OrbStack.  But instead of prompting Claude to generate a tutorial and prompting it to regenerate when I hit roadblocks, I started a prompt and gave it feedback as I progressed.  Here’s the initial prompt:

I want to execute a binary from an npm package as a long-lived process in an OrbStack container.  As a software engineering instructor, guide me through that process step-by-step, prompting me after each step with “Let me know when you’ve finished this step—or if you need help troubleshooting—and I’ll share the next step” until I let you know that my binary is running successfully.

This approach is a deliberate “human-in-the-loop” approach versus the loop engineering you may have read about or may already be executing with AI agents.  But I’m trying to knock off the rust of not having shipped production code since the pandemic—not build a software engineering team of agents (not yet anyway).

Claude started by giving me Step 1: Confirm OrbStack is running and its Docker CLI is active.  Once I finished following those instructions and told Claude I was done, it generated Step 2: Pick the npm package/binary and decide how it’ll live in the image.  But instead of walking through those individual steps, I prompted Claude by attaching bluesky-pipeline-tutorial-v4.md with the following prompt:

I’m trying to run some custom code I’ve written as a long-lived process, specifically the schedule.ts file described in step 6 of the attached file.

In response, Claude generated Step 3: Write the Dockerfile.  The step included a .dockerignore to add so the build context would stay clean.  Once I finished this step, Claude generated Step 4: Build the image.  With that step completed, Claude generated Step 5: Run it as a long-lived, persistent container.  In addition to the docker run command, the step included a bulleted list which explained each flag in the command.  The flag walkthrough pointed out that the openDb() call in my runPipeline function defaulted to a location that would cause the database to be overwritten the next time I rebuilt the container.  I prompted Claude with the following to confirm I had the right idea regarding the change I needed to make:

Do I need to change line 5 in run.ts to set dbPath = “/app/data/bluesky.db” and rebuild the container?

Claude’s response confirmed I was correct, included the full line change to implement, and explained the steps to rebuild the container, stop and remove the existing one, and start the new one.

After I completed Step 5, Claude generated Step 6: Verify it’s actually working, not just “running”.  Step 6 included a lot of diagnostic steps I wouldn’t have thought of, though Claude’s suggested code for querying the database from the command line didn’t work after a couple attempts.  Claude then suggested adding a script to the container solely for counting rows in the database’s ‘posts’ table and rebuilding it.  That check worked.  When I prompted Claude with the actual count (3333), it generated a couple of checks to run to see how long the container had been running and to check the row count in the database against my Bluesky post count.  After I prompted Claude that the count was valid (my profile had 10.8K posts at the time I ran the container), it responded with a summary of the work we’d done and one last check for the container restart count.

A slightly different experience than prompting for a tutorial and asking for an updated one that addressed issues and roadblocks I encountered with the previous version, but the same end results: working code, and a slightly better understanding of the language and tools I used to build it.


Building a Code-Along Tutorial with AI (Part 1)

It occurred to me during a walk one day to try using gen AI to generate a tutorial to walk me through building a tool I wanted, instead of prompting it until it generated a version of the desired tool.  I’m not sure if prompting gen AI to generate tutorials is a meaningful corrective against the deskilling trend a growing body of literature is warning about.  But as a former senior manager of software engineering in transition, I haven’t shipped production software since the pandemic and thought this might be a way to start knocking some rust off.  I decided to prompt a tutorial to build a couple things:
1. A data pipeline for retrieving my Bluesky posts on a schedule and storing them in a database

2. A CLI for querying the database

It took a few iterations with Claude Sonnet 5 set to Medium effort, but the end results were a decent tutorial and working code.

Version 1

The prompt:

As a software engineering instructor, generate a hands-on tutorial for me to follow in order to build the following software components:

  1. A data pipeline which retrieves my Bluesky posts via the AT Protocol API on a schedule and stores them in a database (perhaps SQLite to start).
  2. A CLI for querying the database

The result: bluesky-pipeline-tutorial.md

When I got to the part of project setup that said to create a .env file and add it to .gitignore, that exposed the absence of any prior instructions to configure a local GitHub repo.  So I prompted for a tutorial revision.

Version 2

The prompt:

Revise the tutorial to include the necessary steps to configure a local GitHub repo. The absence of those prior steps stands out when project setup instructions say this:

Create .env (and add it to .gitignore immediately)


The result: bluesky-pipeline-tutorial-v2.md

I followed the revised tutorial all the way through step 5, but manual execution of the pipeline failed.  It occurred to me that error I’d gotten might be because I didn’t properly account for having switched from the default PDS for Bluesky to Blacksky some time ago.  But I narrowed my follow-up prompt to the specific error instead of something broader. 

Version 3

The prompt:

Result was the following: [2026-07-12T21:46:07.397Z] Pipeline failed: Invalid identifier or password

Please generate a revised tutorial that addresses the issues.


The result: bluesky-pipeline-tutorial-v3.md

The revised tutorial added a subsection to verify authentication before completing the rest of the pipeline, including a test script followed by multiple steps to check if the failure repeated.  I walked through the steps, now certain my attempt to connect to the wrong PDS was the culprit.

Version 4

The prompt:
I've verified the issue is not any of the items in the new step 3a, but I forgot that I no longer use the default Bluesky PDS, having switched to Blacksky PDS some time ago. Generate a revised tutorial which accounts for this possibility, so I can update the code accordingly.

The result: bluesky-pipeline-tutorial-v4.md

This version of the tutorial added an environment variable to make the PDS a configurable value.  It also provided a script to resolve the correct PDS given a handle and the BlueSky public AppView.  Writing and executing the script yielded https://blacksky.app as the correct PDS.  Once I updated the .env file, the test-auth.ts script that failed after I followed the steps of version 3 succeeded.  Finally, the first manual pipeline run also succeeded, retriving and storing 3295 Bluesky posts in a SQLite database.

 I haven’t built the CLI yet, since I’ve been using Datasette to explore my downloaded Bluesky posts.  I will write another post about the experience of building the CLI.


Who Counts as an American, Revisited

By the narrowest possible margin, the Supreme Court ruling in Trump v. Barbara preserved birthright citizenship—for now.  In a concurrence with the form of King Solomon’s judgment but without its wisdom, Brett Kavanaugh split the baby of birthright citizenship in half, rejecting the majority’s finding on the Constitution along with Samuel Alito, Clarence Thomas, and Neil Gorsuch, but agreeing with the majority that the executive order was unlawful on statutory grounds.  The vagueness of his “relevantly similar” language for future legislative denials of citizenship makes it far too easy for a hostile Congress to create a multitiered system of belonging much like countries without birthright citizenship.  A future America with multiple generations born and raised here but without any say in how they are governed would be the result.

One common thread between Supreme Court rulings impacting black people and other people of color is the way their technical reasoning yields results which are indifferent to their humanity.  Last week, this court ruled in Landor v. Louisiana Department of Corrections and Public Safety that the plaintiff—a devout, black Rastafarian who was forcibly restrained and had his dreadlocks sheared from his head—could not sue prison officials for this egregious violation of his religious freedom.   This same court which barely preserved birthright citizenship gutted judicial review of terminations of Temporary Protected Status (TPS) in Mullin v. Doe, a decision which places hundreds of thousands of Haitians legally present in this country at risk of deportation along with 6000 Syrians. This is the court that Chuck Schumer jumped on social media to cheer as some great example of a check on Trump’s power. With judicial review not required, nothing prevents the Trump administration from canceling TPS (or allowing it to expired) for El Salvador, Lebanon, Sudan, Venezuela, and Ukraine.

The Supreme Court's earlier ruling in Louisiana v. Callais to kill Section 2 of the Voting Rights Act in all but name, on top of Brnovich v. Democratic National Committee (2021) and Shelby County v. Holder (2013) don’t just shift the electoral playing field further in favor of the GOP, but further toward the pre-civil rights era of American apartheid where black citizens were obliged to obey laws from governments which refused them protection and equality under them.  Along with Trump’s executive branch and the GOP-controlled legislature, the federal government is trying to turn me and people like me into de facto U.S. nationals—people who cannot exercise voting rights at the federal level and cannot hold federal office—despite the law saying we are U.S. citizens.  

Beyond the Supreme Court, we’ve watched Trump’s executive branch subject people of color to mass detention without trial domestically—in facilities like Camp East Montana, and the recently-closed Alligator Alcatraz (shuttered for cost, not conscience)—and abroad in places like El Salvador’s CECOT.  Human Rights Watch has found that the mortality rate in ICE custody has more than doubled since January 2025.  The Supreme Court enabled third country deportations with shadow docket rulings on two separate occasions in the past year. A refugee program which accepted roughly 100,000 people from all over the world in the final year of Biden’s administration has virtually collapsed. May 2026 marked the sixth consecutive month where the only refugees the United States accepted were white South Africans, admitted on the basis of a false and racist conspiracy theory about white genocide there.  These are the stakes of Fall 2026 election and every election after: will the GOP be allowed to continue creating the white ethnostate they want, or will we stop them?


This Post story incorrectly characterizes this ruling as a departure from SCOTUS rulings “expanding religious freedoms”. Every ruling so described only expanded the ability of Christians to impose their interpretation of their beliefs in public spaces.

apple.news/AqjL5jK_o…


Happy Juneteenth! Respect and special thanks to black Texans as its originators.

A Juneteenth flag flying in front of leafy green trees from a trip I took to Philadelphia 4 years ago.

AI Is the Latest Pretext for Role Destruction in Tech

If you’ve worked in the tech industry for a while, you’ve seen numerous stand-alone roles disappear.  The role of database administrator is one example.  Quality assurance staff, whether you called them engineers or testers are another example.  A previous employer of mine, having adopted agile delivery lead as a hybrid of scrum master and project manager years earlier, eliminated every employee with agile in their job title during the depths of the pandemic—1700 jobs in total.  The disappearance of those roles did not mean their work disappeared.  It meant the work shifted to those who remained.  Developers and engineers inherited DBA and QA work.  Product owners and senior engineering managers inherited the work of agile delivery leads.  

In each case, the quality of the work and the level of productivity declined, while we who inherited the new work absorbed and adjusted to the broader scope.  What tech companies previously did by blurring the line between development leads and development managers is now being applied to more senior engineering managers,  brought by AI (at least according to James Stanier).  At least in my experience, the blurring of roles and responsibilities at the next level already happened during the pandemic—prior to the launch of ChatGPT.

In the section of his piece with the heading “The evolving engineering manager role” Stanier  lists the following things AI automates that “defined many engineering manager roles”: status updates, progress tracking, meeting summaries, and scheduling.  This looks a lot like work I inherited after every agilist in my organization was laid off—in addition to my existing responsibilities.  However, that list falls well short of defining all the work I did as a senior engineering manager for 12-18 engineers spanning 2-3 teams over the past few years.  My responsibilities included quarterbacking production incident response, defining and driving application modernization, and providing technical feedback on significant architectural changes across multiple systems within our group.  After the flattening that same organization executed in 2025, my scope of people management above and beyond my technical responsibilities grew from 7 engineers to 12 engineers.  Combining people leadership with genuine technical depth was already the job description for engineering leaders at my level, along with fulfilling the responsibilities of people in roles which were previously eliminated.  Stanier's framing treats coordination as organic engineering overhead.  But in larger organizations, it was a stand-alone role—held by non-engineers—which senior engineering managers absorbed when those roles were eliminated.

Stanier again: “The coordination was never valuable in itself; it was a cost imposed by the limits of what one person could do alone.  AI is removing that limit, and the data is starting to show it.”  I’ve written previously about the impacts of organizational flattening that I’ve observed personally and read, but it’s worth drilling down on what Stanier oversimplifies by calling it “coordination”.  That’s not the only thing happening when engineers collaborate to solve problems.  They are sharing institutional knowledge.  They are building tacit knowledge—the kind that exists primarily in relationships built through repeated collaborations over time.  Engineers have much longer and more durable “context windows” than AI, and the software resulting from repeated collaborations over time is more likely to be better-designed and more robust than its AI-generated equivalent.  

Stanier references The AI Productivity Paradox Report approvingly, but it contains findings which undermine his argument.  He acknowledges its finding that high AI adoption results in 9% more bugs per engineer and PRs which are 154% larger on average. Amazon pivoting to requiring senior engineer sign-off on AI-assisted changes has likely caused review bottlenecks as AI generates large PRs faster than humans can review them.  A Barcelona-based engineering leader for a large online wedding planning company I’ve spoken with regarding Stanier’s article has observed this phenomenon with a recent project his team led.    

Even those boosting AI adoption acknowledge that it drives both significant code bloat, and the same report "observed no significant correlation between AI adoption and improvements at the company level”. By suggesting that senior engineering managers cede coordination and reporting responsibilities to AI and leverage it to generate code, Stanier is advocating compounding AI-associated risk and putting responsibility on the senior engineering manager to effectively mitigate both.  As strategic decision-makers, senior engineering managers should be mitigating risk—not compounding it.