Scott Shinn
Aug 19, 2026 - Sep 16, 2026
4
Decisions
0
Active Todos
12
Patterns
Categories
Decisions (4)
Route all new Shin-brothers requests through Bjorn for a month, in writing, with technical direction staying with the asking manager
Nathan asked how much CIQ could use Mike and Scott on work outside Core42 - specifically the RLC-H 10.2 lockdown RPMs and updating the STIG and CIS guidelines to match EL10 - because Jason is committed to CVE automation and Oleg is a month or more from starting. Peter did not know the contract limits, said so, said he would find out, and came back with the answer. He then set the interface: for the next month, new requests to the Shin brothers go through Bjorn. Nathan writes a one-page brief on what he wants done and sends it to Bjorn with Peter copied for visibility, and Bjorn makes the ask so that the work happens at Nathan direction. If request volume grows, Peter said they would probably build a pipeline or agreement to short-circuit the routing so managers could go straight to them. On Core42 work specifically, Peter told Nathan to assume they are full time working for CIQ if needed. Nathan accepted and said he would get a one-pager written.
Constrain the AMD commitment to lab validation on an MI300 rather than promising CIQ will acquire one
In the group DM with Bjorn Hovland and Adam Jackson on Sept 9, after Adam reported progress on the AMD motion, Peter cut back what could be promised. He told Adam to be careful about promising CIQ will acquire MI300s, allowed the exception that if Adam actually has one in hand from a contact then fine, and said that otherwise he does not think CIQ could get one in the timeline that matters. He substituted the commitment CIQ can keep: telling AMD that CIQ will run validations on a 300 is fine, because he is confident Scott Shinn can get CIQ test access in AMD own lab. He bracketed the correction with support, telling Adam the work is awesome and to let him know how Engineering can support. In the same thread he raised the harder problem nobody had asked about - that AMD will not leave themselves partly on Rocky and partly on Ubuntu, so CIQ needs to get into the weeds on what a cutover looks like and make sure plans are in place, or AMD will keep deploying Ubuntu because their setup and management infrastructure is all designed and tested for it.
Refuse to guarantee Oct 5 for Core42 if CIQ is deploying Ubuntu - give a likely range unless the customer demands a guarantee
Asked by Adam Jackson in #core42-build-and-deploy whether CIQ could commit to an Oct 5 completion starting Sept 18, Peter answered no for the full-Ubuntu-deployment scope: there is absolutely a chance CIQ would hit it, but CIQ cannot guarantee it. He then separated the scopes - if it is just Fuzzball, and Ubuntu is already stood up on the racks and networked, and CIQ gets access Sept 18, then absolutely CIQ could hit that date. He gave the rule for how to answer the customer: be VERY careful about guarantees in a new environment and an OS that is not ours, because a guarantee puts CIQ in a position to lose future business when this is the first time CIQ is doing this; if Core42 MUST have a guarantee that is one thing, but if they only want a likely range then give the range and do not make an unforced error. He then asked the four scoping questions that decide which scope applies - is Ubuntu already installed, is networking already set up, is there a provisioning machine available for ELM, and exactly how many machines.
Approve the NVIDIA-supported Fuzzball hackathon at SC - with a Wolford engineer on site a day early and a month of hardware notice from NVIDIA
In the L/P Quick Sync on 2026-08-18, Lindsay Aamodt brought the NVIDIA hackathon she has been building - in person in Chicago, Friday November 13 kickoff, build Saturday and Sunday, judging Monday, winner presented in the booth Tuesday as SC opens - and asked Peter to name the risks that would make it a flop in person. Peter approved it and attached conditions: someone who works for Chris Wolford goes on site a day ahead to stand the clusters up, explicitly not Lindsay; and NVIDIA must confirm exactly what hardware they are providing a month in advance so the networking is handled beforehand. He committed himself as a judge alongside Bjorn, Greg and Scott, and Wolford as mentor staying through Saturday.
Related Patterns (12)
Lead by Example with New Tools
When championing new tools or processes, personally use them and share results rather than just advocating. Learning by doing and demonstrating value through example is more effective than mandates.
Protect Engineering Focus Through Process
When faced with requests that would disrupt engineering focus (from sales, governance, product, or other stakeholders), establish processes that protect engineering ability to innovate while still satisfying legitimate concerns. Prefer systematic solutions over ad-hoc responses.
Reclassify to Route - Decide Who Owns It, Then Give a Criterion Not a Verdict
When a question arrives at Peter framed in one domain, he often does not answer it in that framing. He reclassifies it into the domain that actually governs the outcome, which relocates ownership to whoever owns that lane, and then hands down a decision criterion rather than a verdict. The reclassification IS the decision - it determines who decides. He does this rather than adjudicating on the merits himself, even when he was explicitly cc-ed and even when a direct report challenges him on the substance.
Purpose Is the Decision Procedure
When someone asks how a process, board, tool or artifact should handle their specific case, Peter refuses to answer on the askers terms. He re-derives the answer from what the artifact is for, states that purpose as the only decision procedure, and lets the answer fall out. Anything found to be serving a second purpose is deleted rather than debated. Tools and views are explicitly subordinate to definitions. He will accept that the askers real problem is simply not solved by this artifact rather than widen the artifact to cover it.
Route Non-Differentiating FTE Classes to Partners
When CIQ would otherwise need to staff a function whose work does not differentiate the company — compliance bureaucracy, audit/cert paperwork, ongoing regulatory attestation, etc. — Peter routes the load to a partner who already owns adjacent capability rather than adding the FTE class internally. Org-shape decision dressed as a partnership decision.
Demonstrate the Standard, Then Collect It
When a new leadership expectation has to land across multiple orgs, Peter does not write a spec. He runs a live exemplar in public with the strongest performer first, says openly that the ordering was deliberate, keeps the form of the deliverable open so the ask stays about the thinking rather than the artifact, lets the delta be self-evident to the people who will have to close it, and then collects the same from everyone else on a named rotation. He prefers showing imperfect work now over polished work later.
Decide on the Precedent, Not the Case
When a request arrives framed as a one-off, Peter does not evaluate the one-off. He evaluates the rule that granting it would write, and answers that instead. Peter generalized this himself on 2026-08-11: it is always about understanding precedent - whether it is a comp change or anything that structurally affects the company. It is therefore NOT a compensation pattern; the domain of the presenting request is incidental. The tell that this pattern is live is that the stated reason for the answer refers to future cases rather than to the merits of the present one.
Metrics Must Follow Strategy
When shifting team priorities or strategic direction, the communication alone will not drive behavior change. Engineers may acknowledge the new direction but continue existing behavior patterns without clear, explicit metrics holding them accountable.
Switch Instrument, Not Intensity
Applies when a message, rule or ask has already failed through the channel Peter is currently using - repeated advocacy that has not landed, coaching that produced defensiveness rather than improvement, exhortation that did not change behaviour, or a rule that keeps losing case by case. His response is never to restate the same thing more forcefully. He changes the instrument and usually names the switch out loud. Mined from 7 independent observations between 2026-01-06 and 2026-08-21.
Time Over Cost
Peter treats elapsed time as the scarce quantity and money as the abundant one, and will spend cash to buy schedule, clarity or optionality. Notable because he named it himself as a transferable principle on 2026-05-21 and coached the lens explicitly to a direct report, which is rare - most of his patterns are inferred rather than stated. It generalises past procurement: he will pay to convert an ambiguous dispute into a binary one, remove cost as a variable entirely when a priority has executive visibility, and reason about a commitment in terms of lead time rather than budget. Mined from 5 independent observations between 2026-02-01 and 2026-09-11.
Promise Only What Is Inside CIQ Control
Applies when someone asks CIQ to commit to an outcome whose delivery depends partly on something CIQ does not own - a lead time, a third-party publisher, a customer-provided environment, an unsigned contract. Peter does not accept or refuse the request as posed. He isolates the specific component that sits outside CIQ delivery chain, refuses that component by name, and substitutes an adjacent commitment CIQ can actually keep - then often adds a harder problem worth solving in its place, so the counterparty gets more engagement rather than less.
Measure, Commit Publicly, Then Execute
A three-beat escalation arc Peter runs when he needs a commitment from a peer or the CEO that private pressure has not produced. Beat one: measure the thing and get a number. Beat two: state the commitment in a venue where the people who matter are watching. Beat three: execute against it. The 2026-04-15 observation names the sequence explicitly and notes he does not skip steps, because each beat builds the legitimacy of the next. The venue choice is treated as a decision in its own right, separate from what the message says. Mined from 8 independent observations between 2025-12-29 and 2026-08-28. NOTE: scope this to the venue-and-sequence mechanism specifically - forcing function is a phrase that appears loosely across many unrelated decisions and should not be taken as a match on its own.