Stephen Way

@stephenway.bsky.social

19 Followers 161 Following

Feedback loops should be instant, I think

White slide showing a simple diagram: one source branching to two ovals labeled "Reused" (green) and "Rerun" (red), caption "same inputs → different outcomes."
Announcement header with paragraph stating a $0.002 per-minute GitHub Actions cloud platform charge applying to GitHub-hosted and self-hosted runners.
Dark tech landing page for Layerun promoting causal temporal CI, highlighting skipping 80% of unnecessary builds with call-to-action buttons and geometric glowing cube graphic.
Screenshot of a terminal showing Layerun running a demo pipeline. The command lrun exec --goal goal.json executes a 12-task build graph. Only one task, parse-config, is marked as executed with a duration of 11ms. All other tasks are labeled cached and appear dimmed. A summary section below shows: 12 tasks total, 1 executed, 11 cached, 91.7% cache hit rate, and the execution ID and commit hash. The terminal window is centered on a purple contour-pattern background, matching a typical developer screenshot style.
Screenshot of a terminal showing Layerun running a demo pipeline. The command lrun exec --goal goal.json executes a 12-task build graph. Only one task, parse-config, is marked as executed with a duration of 11ms. All other tasks are labeled cached and appear dimmed. A summary section below shows: 12 tasks total, 1 executed, 11 cached, 91.7% cache hit rate, and the execution ID and commit hash. The terminal window is centered on a purple contour-pattern background, matching a typical developer screenshot style.
Dark-themed CI dropdown showing "Re-run jobs" with options "Re-run all jobs" and "Re-run failed jobs" over a dashboard panel.
Concentric black ruler-like spirals forming a tight coil that resembles a sleeping snake with a small red forked tongue.
Dark code editor window showing Rust code: let goal = Goal::new("prod_ready").requires("build_complete").requires("tests_passing");
Two-panel diagram: left flowchart shows commit → path checks ('/api/*', '/schema/*') leading to skip, ignore, or trigger build; right causal graph links source, infra, deps to system state feeding build, deploy, tests.
Left panel shows crime-scene board with suspect silhouette, evidence pins and caution tape; right panel shows monitor with CCTV camera and person labeled EPOCH.
Laptop covered in colorful Beanie Baby stickers: owls, frogs, flamingos, bears, unicorns and penguins clustered around an Apple logo.
Minimal UI slider labeled "EPOCH" showing a horizontal track numbered 1–7 with the circular handle positioned at 4.
Left: flowchart using brittle path-based rules to skip or trigger CI. Right: causal graph linking source, infra, deps to system state and build/deploy/tests.
Screenshot of a terminal showing Layerun running a demo pipeline. The command lrun exec --goal goal.json executes a 12-task build graph. Only one task, parse-config, is marked as executed with a duration of 11ms. All other tasks are labeled cached and appear dimmed. A summary section below shows: 12 tasks total, 1 executed, 11 cached, 91.7% cache hit rate, and the execution ID and commit hash. The terminal window is centered on a purple contour-pattern background, matching a typical developer screenshot style.
A digital sticky note labeled “Vault” sits centered on a vibrant blue-to-orange gradient background. The note lists three placeholder keys — DEV_API_KEY, STAGING_API_KEY, and PROD_API_KEY — with each value obscured. It looks like a simple, minimal notepad for secrets against a jazzy, colorful backdrop.
Frosted windshield with someone scraping the ice and frost off
A GitLab CI yml file showing off an example pipeline in stages.
Screenshot of a terminal where Jenkins has been running since 2022. Nobody’s touched it. Everyone’s afraid to stop it.