Shipyard

@shipyard.build

Full-stack ephemeral environments on every PR. E2E testing on every code change.

up until recently, there was a very real tradeoff between delivery velocity and stability shipping fast meant monitoring new deployments really closely fast forward to 2026, and we have a new environment “stack” that developers and agents move with, not around

Bild

now you can schedule your #ClaudeCode tasks to repeat on a loop devs are finding this super valuable for PR babysitting: tell Claude to watch your PRs, react to build logs, and resolve any issues brought up in the comments

Bild

Claude tokens == NLP tokens these are the smallest units of text that LLMs use to process input/generate output (1 token = 1 word, 1 subword, or 1 letter, depending on your model)

a token generator with the Claude logo, implying that this is the LLM taking input and generating code, token by token

there isn’t exactly a wrong choice for a container registry, but how to eval which is right for you? - use the CR bundled with your cloud/git ecosystem - OSS vs. proprietary: both $$ in different ways - artifact support (OCI, helm, AI model) - vuln scanning/IAM

Docker Hub page for node Docker imageQuay container registry repository settings page

engineering teams are improving their #ClaudeCode workflows every day. but CC can test its own work autonomously a feature might take ~10 tweaks to get right, most obvious after running simple smoke/UI tests give agents access to real infra so that they can self-verify + iterate

Bild

some tasks are too complex for @claudeai subagents. that's where #multiagent orchestrators come in, allowing a lead coding agent to delegate tasks and spawn agents as needed in this post, we take a quick look at Gas Town and Multiclaude ⬇️

a cover image showing multiple claude code agents linked together in an orchestration pattern

#claudecode has always stood out for its filesystem + ops capabilities. in fact, CC is a CLI-based agent for anything, not just coding they built a solid UI on top of Claude Code’s foundation to make a tool for file-related work, called Claude Cowork

claude cowork cover image showing a laptop with the claude logo

Yes, we need code reviews. In addition to reviewing intent, code reviews are an opportunity to review the how and ask questions: should we bring in these 3rd party dependencies, are we duplicating existing functionality, did we check in credentials by mistake, etc. Most of this can be automated.

Ian Bull (Elbows Up 🇨🇦)@ianbull.com · 7mo ago

Do we need code reviews. I argued that we need "Change Review" not "Code Reviews". That is, we should review the intent (what & why) and not the how. But then everyone told me this is obvious, this is what we did all along. So do we need "Code" Reviews?

engineering teams spend so much time during the year talking about dev productivity. dec is a difficult time to keep those metrics up anyway. why not use the holiday stretch to catch up on your skills + learn new things?

cover image for a block post showing a fireplace with three christmas stockings. each one has symbols that represent developer tools

we’ve got some HUGE news: the Shipyard #MCP server is now in open beta! use it for: ✅ writing + improving #E2E tests ✅ sandboxing #agent workflows ✅ live, in-depth code reviews we’re looking for user feedback, so reach out with any questions/comments 👀

shipyard logo next to MCP (model context protocol) logo, showing integration

why should agents get to do all the fun parts of software dev, like writing code? #ClaudeCode has a feature that allows you to make agentic dev more active: it assigns you programming tasks and reviews your work. agent pair programming keeps you in the driver’s seat 👍

Bild