Samuel Cochran.oci @sj26

Founding Engineer at @Buildkite sj26.com Melbourne, Victoria Joined May 2007

Tweets

16K
Followers

1K
Following

774
Likes

17K

Samuel Cochran.oci @sj26

5 months ago

@melissa This is very growth/fixed mindset

0 0 1 24 0

View Details

Samuel Cochran.oci @sj26

6 months ago

Trying to read a markdown document on @github this morning and it keeps refreshing and scrolling back to the top. What are they doing with their frontend???

0 0 1 75 0

View Details

Samuel Cochran.oci @sj26

6 months ago

@BrandonWaselnuk @jasonfried Yes. jobs.apple.com/en-au/details/…

0 0 1 36 0

View Details

Samuel Cochran.oci @sj26

6 months ago

@TheDyla34646123 @NAP_benkimchi store.steampowered.com/app/4175180/DR…

0 0 0 200 3

View Details

Samuel Cochran.oci @sj26

6 months ago

@Yummy_TheArtist @Rainmaker1973 Looks like Wagyu IDATEN share.google/Gteurp3CpGLa9u…

2 1 8 419 8

View Details

Samuel Cochran.oci @sj26

7 months ago

@AmpCode weird, website seems to be flapping down for me (from Melbourne, Australia)

0 0 0 38 0

View Details

The crisis of software quality was already coming. Coding agents have just accelerated everything. Folks shipping quality are still shipping quality but faster. Those in crisis are unravelling faster. The problems are systemic. So must be the solutions.

0 0 3 95 0

View Details

Samuel Cochran.oci @sj26

7 months ago

@dhh @buildkite (We still have int primary keys for database and legacy reasons but they’re an implementation detail, everything has a uuid representing its true identity, public apis have only ever exposed uuids, and many models have uuid primary keys only.)

0 0 0 77 0

View Details

Samuel Cochran.oci @sj26

7 months ago

@dhh Same as @Buildkite. I’m hoping we can bridge our central service into self hosted components with distributed key generation etc. Hardest part is sequential build numbers 😅

1 0 0 152 0

View Details

Samuel Cochran.oci @sj26

7 months ago

fidexCode @fidexcode

7 months ago

Which number is your current level of setup?

9K 985 20K 3.7M 3K

0 0 0 121 0

View Details

Samuel Cochran.oci @sj26

7 months ago

Bueno @0xBueno_

7 months ago

Which one was your favorite messenger?

331 82 748 60K 84

0 0 0 93 0

View Details

Samuel Cochran.oci @sj26

7 months ago

I would rather a smooth backed phone (no camera bump) and a camera attachment like this for when I want to take nice photos.

Pascal Bornet @pascal_bornet

7 months ago

The smartphone just declared war on the camera industry Xiaomi just dropped a wild idea: a smartphone with a detachable pro-grade camera lens. A phone that snaps on a real lens with magnets. Yes, magnets. It’s a clever move at a strange moment in history. Camera sales keep

529 897 8K 1.5M 3K

0 0 1 119 0

View Details

Samuel Cochran.oci @sj26

7 months ago

@dogeki113rr @HankYeomans @WAVArchive re-amp.ru works

0 0 0 49 2

View Details

Samuel Cochran.oci @sj26

7 months ago

@parkersity_9 “Well, it depends.”

0 0 1 232 0

View Details

Samuel Cochran.oci @sj26

7 months ago

For a product about exploring time series data, @datadoghq is truly terrible at time. Copy/pasting within the application confuses it.

0 0 1 106 0

View Details

Samuel Cochran.oci @sj26

7 months ago

Service meshes are the middle management of software architecture.

0 0 1 55 0

View Details

Samuel Cochran.oci @sj26

8 months ago

@markjaquith This is also how you trick a toddler out of a temper tantrum, start saying things that are wrong - oh look at that blue apple, what a nice red banana, has you seen this purple orange??

0 0 1 55 0

View Details

Samuel Cochran.oci @sj26

8 months ago

@wongmjane It’s thanks to changes in response to EU rulings: arstechnica.com/gadgets/2025/1…

0 0 0 86 0

View Details

Samuel Cochran.oci @sj26

8 months ago

@ivjukic @wongmjane Was looking through the comments for exactly this. Ars Technica covers it well: arstechnica.com/gadgets/2025/1…

1 0 0 49 0

View Details

Samuel Cochran.oci @sj26

8 months ago

Yeah our tools already detect and retry flaky tests automatically etc so if a build fails it requires diagnosis beyond a repeatable pattern. That’s why it’s tricky. What the human would do is dive deeply into the build result and its artefacts to understand the error and how to fix it. This is a difficult problem to solve generally. Pipelines, build graphs, etc, vary wildly. Solving this specifically is better, as a human at a terminal with an agent, or an agent in a coding environment of its own trying to push a PR. Neither of those should live within CI, imho, they are adjacent.