Samuel Cochran.oci

@melissa This is very growth/fixed mindset

it seems patently better to buy in to persistence as opposed to the belief that losing results from randomness or unfairness, and never that you were outplayed

one time as a kid, my dad told me about some old research he'd read he said, maybe asian kids are better at math because they just try 50% longer

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???

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

@jasonfried Day 1: "Have you considered ruby on rails?"

Finally! Please, someone take this loudmouth vibecoding hack off our hands! 😂

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

@NAP_benkimchi What’s it called on steam?

GAMEPLAY：You can roughly think of it as a version of TAUR with a movable base. ARTSTYLE： 90s Mecha anime #gamedev #indiegame #ゲーム制作 #ゲーム開発

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

@Rainmaker1973 Restaurant name?! I know where I’m going next time I’m in Osaka! Yummy!

This is a Wagyu Steak Rice Bowl restaurant in Osaka. The A5 Tadaki brand uses only Wagyu beef, grilled over charcoal, and served with tare sauce. This restaurant is located near Dotonbori.

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

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.

@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.)

@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 😅

Fun fact: Fizzy is using UUIDv7 primary keys. Plan is to offer import/export between our SaaS hosting and people's own on-prem installations. Start on SaaS, grab your own SQLite DB, then run it yourself (or the other way!). Will upstream to Rails soon. github.com/basecamp/fizzy…

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

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

@HankYeomans @WAVArchive Please release a download for this, I’d love this 🙏🙏

@parkersity_9 “Well, it depends.”

Without naming your job, tell me something you say 20 times per day at work

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

Service meshes are the middle management of software architecture.

@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??

Tip for engineers working with talented but time-constrained designers: Instead of asking them to design something and waiting weeks, just slap something together. It will literally jolt them awake like a cartoon and they’ll design something 10× better, same day.

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

Looks like Google reverse-engineered AirDrop’s protocol and came up with their own implementation! This is so cool! Now, if Apple deliberately breaks the interoperability and limits it to Apple devices only… I think Google might be able to build an antitrust case out of it

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

@wongmjane Nobody mentions that EU adopted new specification decisions that required Apple to adopt new interoperable wireless standards, starting in this year’s iOS 26 release. So basically every phone will be able transfer data with iPhone.

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.

I think a good angle is: what would a human do and then how could an LLM mirror that? So if CI fails, what does a human do: - I see the alert - I check the error to see if it seems like a flake, if so I re-run - If not, I pattern-match/search my brain to see if this is a known type of failure - I leave a comment on the alert in Slack that says "Flaky; re-running" or "Weird error, taking a look" So instead, could an LLM be inserted so that: if it seems flaky (how to detect? dunno but you could give an LLM examples of common flaky tests or look at what builds re-ran without code changes), just re-run it for me. If it still fails, maybe the Slack alert has a note at the bottom like (We tried re-running this and it still failed)

I would love to read much more about using LLMs in product features and much less about using LLMs to code the features