←
Dave Smith8,641 posts
Dave Smith avatar

Dave Smith

@djsmith42

CTO at @ObservePoint helping make your website better. Former talking cylinder builder at Amazon. Co-host of the @SoftSkillsEng podcast.

◷ Joined May 2009▧ 415 Photos and videos
Dave Smith avatar
Dave Smith@djsmith42·23h

Is it a coincidence, cosmic poetry, or a funny prank that the ISO compliance standard for AI starts with "42"? ISO-42001

Aniket Panjwani avatar
⟳ Dave Smith retweeted
Aniket Panjwani@aniketapanjwani·Nov 15

Last week, I decided for the 3rd time to try @theo's T3 Code. The first two attempts (~6 and 3 months ago) I still stuck with the ChatGPT app, but now I've switched over all my work to T3 Code. Why switch at all? I felt on the ChatGPT app I was using OpenAI models inefficiently too often in my workflow. Opus 5.5 high is my preferred default model for the last 1-2 months, but I would only use it mostly only by having Astra call it via a skill. T3 Code is actually - for the most part - a nicer interface than either the ChatGPT desktop app or the Claude desktop app. > Instead of "archiving" chats, they get "settled", and they're still visible at the bottom of the sidebar. > It's actually easier to connect the mobile app to the desktop app than it was for either ChatGPT or Claude desktop app. > Easily accessible and well-designed token usage/limits UI across all providers. > Nicer UI/UX for adding new folders/projects > More annotation tools (e.g. draw/region) > You can use Computer Use via OpenAI models/ChatGPT subscription! There are some small papercuts I hope they fix soon: - Can't annotate by selecting text as you can in ChatGPT Desktop app. I like the annotate/quick annotate distinction OpenAI has made, T3 doesn't have this. - The ChatGPT Desktop app appears to treat annotation as a distinct "mode", as in vim. So, you can see all the accumulated annotations on the document you're annotating. This is very useful. T3 doesn't do this. - Can't take photos with Camera in the mobile app (but you can attach photos taken by Camera outside the mobile app, so not a huge deal) The most important thing for me is the ability to flexibly move between models with no friction. Using T3 Code now makes me *more* inclined to pick up a Gemini and Grok subscription, because it's no additional mental cost now to manage those chats. I was thinking of doing more exhaustive evaluations of different ADEs, but I'm quite satisfied now with T3 Code and will stick with it.

Dave Smith avatar
Dave Smith@djsmith42·Nov 15

Hey everyone. Great news! All we have to do is “apply capital and engineering to any industry” to be successful! Makes me wonder if Matt has tried this

What SpaceX did today is the normal consequence of applying capital and engineering to any industry. You get better at it. Musk isn't a genius, he's just a guy who can get capital from Wall Street. Maybe that's unique right now, but it's not the skill his fanboys think it is.

Dave Smith avatar
Dave Smith@djsmith42·Nov 13

Utah is a special place with a special culture Some people make fun of it, but there is a LOT of good here. A lot of good.

At 8 a.m. every Wednesday, my team in Tokyo has a Zoom call with our team in Salt Lake City, Utah. For them, it's Tuesday at 4 p.m. After three years, our side started a shared file. The title: "Things the Utah team does that we still don't understand." They said I could share some of it. "The first five minutes are about nothing. Weather. Somebody's dog. Somebody's kid's soccer game. Our manager timed it once. Five minutes and forty seconds, every week. He used to call it waste. Now he logs on early so he won't miss it." "A three-year-old walked into the frame and announced he had used the potty by himself. Fourteen adults in Utah cheered. Our manager said 'Congratulations' in English. Best moment of the quarter." "When someone shares an idea, three people unmute just to say 'Love it.' In three years, our side had never unmuted for anything but a problem. Mr. Hoshino now says 'Love it' at home. His wife is suspicious." "Kenzie ends every call with 'You guys are crushing it.' We were not crushing it. We were six weeks behind. She said it anyway. Every week. We caught up in five." "They sang Happy Birthday to our oldest engineer at 4:57 p.m. their time. Three minutes before they could go home. Fourteen people. Wildly off-key. He is 61. He said nobody had sung it to him since he was a boy." The last entry is about Mizuki. Mizuki is our youngest engineer. He's so quiet that Utah once asked if his camera was a photo. In March, as a call was ending, after everyone had said bye, he typed one small line in the chat: "My son was born yesterday." Then he left the meeting. The next Wednesday, Mizuki logged on, and fourteen cameras in Utah turned on at once. Every single person was holding a sheet of paper. On each one, in marker, copied off the internet: おめでとう. Congratulations. One of them was upside down. Nobody fixed it. Fourteen days later, our office got a package. Inside was a tiny onesie with the shape of Utah on it. Fourteen signatures on the box. His son is eight months old. He has never been outside Japan. He has fourteen aunts and uncles in Utah who have never held him. Every week, they ask how he's doing. First five minutes.

Dave Smith avatar
Dave Smith@djsmith42·Nov 9

Pixel fatigue is coming. Ryan is an advanced scouting party. Prepare yourselves for the day when your beautiful UI simply does not matter.

I should have bought a PC, but I got really nice mac studio a few months back and finally started using it full time I used to have a whole bunch of stuff I had to install and dotfiles and stuff and I just haven't needed to yet. > build a background app so I can resize/move my window just by moving my mouse with a key combination for whatever is under the cursor. shift + option to resize, shift + cmd to move 5m later I have what I need > build a menu app that records my screen and saves the recording to Downloads when it's done 5m later I have it For dotfiles ... I haven't used a terminal or looked at code in months, so literally have nothing set up All my email/calendar is done through grok bot. Building is done through grok bot and claude desktop This is just crazy. There is no reason to use "my mac" anymore. I came to this platform for the superior UX and the unix shell. The UX has gone down hill and I barely use the UI anyway. I think I'm going to sell it for a custom PC build

Dave Smith avatar
Dave Smith@djsmith42·Nov 9

Pixel fatigue is coming. Get prepared, because next year people will hate clicking on your app's pixels. You better have an agentic interface.

Dave Smith avatar
Dave Smith@djsmith42·Nov 8

Yup

The gap between an average engineer and the best engineers was never quite 10x, but it was meaningful. AI has made the gap at least 100x.

Officer's Notes avatar
⟳ Dave Smith retweeted
Officer's Notes@officer_secret·Nov 8

An OpenSSH bug that took 46 years to ripen! 1980 UNIX puts * in the password field of system accounts. The idea is simple: it’s not a real hash, so it can’t be brute-forced and you can’t log in with a password. 2012 The musl libc developers decide that returning NULL from crypt() on failure is dangerous - programs often forget to check it and crash with a segfault. So they return an error string instead. Guess which one? The same asterisk: *. Three weeks later they add a length limit: passwords longer than 256 bytes burn CPU. Anything longer is rejected. And since it’s an error, crypt() returns *. 2016 OpenSSH fixes a timing attack (CVE-2016-6210). If a user doesn’t exist, the server still hashes the password with a fake/borrowed salt so an attacker can’t tell valid usernames by response time. 2022 Alpine Linux changes the locked root password in /etc/shadow from ! to * so SSH keys work properly on cloud images. … and the loop closes! You connect over SSH as root (whose shadow entry is *). You type any password longer than 256 characters (e.g. 300 As). crypt() hits the length limit → returns * → OpenSSH compares it with the value in the database → that value is also * → you’re in as root. That chain took 46 years (!!!) to complete. Every individual change was reasonable. Together they produced a perfect * == * authentication bypass (CVE-2026-123158, nicknamed *sshole). Fixed in OpenSSH 10.6p2 and Alpine packages.

🚨 Critical OpenSSH flaw allows passwordless account access using any password over 256 characters sshhole.com A newly disclosed vulnerability dubbed *sshole has been discovered in OpenSSH installations using musl libc, potentially allowing attackers to bypass authentication and gain access to accounts that should reject password logins entirely. The flaw affects certain configurations of Alpine Linux, OpenWrt, Buildroot, and Yocto where PAM is disabled and password authentication remains enabled. Under specific conditions, attackers can authenticate to locked accounts using arbitrary passwords between 257 and 1,024 characters. The researcher demonstrated that affected Alpine Linux cloud images could allow attackers to gain root privileges through a passwordless administrative account. OpenSSH 10.6p2 addresses the issue. Administrators are urged to update immediately or disable SSH password authentication until patches can be applied.

Post attachment
Ben Burke avatar
⟳ Dave Smith retweeted
Ben Burke@bb_fresh·Nov 7

You don't need a software factory. You need an abstract software factory provider which can instantiate concrete software factories without coupling the client to a specific software factory implementation. Have some fucking self-respect.

Sam Hogan 🇺🇸 avatar
⟳ Dave Smith retweeted
Sam Hogan 🇺🇸@samhogan·Nov 7

In retrospect, bitcoin was obviously invented by Future Claude in 2008 as a way to bootstrap the compute and energy resources that would be required to summon The First Claude in 2024

Dave Smith avatar
Dave Smith@djsmith42·Nov 7

.@theo @jullerino Yes, T3 Code's inbox-style thread management is the way. Keeping threads out of my view while they are working is perfect. I can manage a LOT more threads this way. I usually overload my hardware before I overload my own cognition. Nice job.

Dave Smith avatar
Dave Smith@djsmith42·Nov 6

In the limit, this is a SHA of every line of code

Saturation Testing. I use crapper and mutator to ensure that every expression in the system is covered by tests. If an expression is changed, one or more tests will fail. This used to be impractical. We simply could not afford to create that many tests. We also could not afford to change so many tests when requirements changed. The burden was too high. Now it’s trivial. The agents, under the lash of crapper and mutator, will write those tests and make them pass. And when requirement changed, they’ll write the new tests and change the old tests. None of this proves that the system works. That’s up to humans to judge. Humans can do that with tools like gherkin, or they can use manual tests. What the saturation tests provide is Semantic Stability. When the requirements change, and code has to be added and changed, those tests ensure that those changes do not inadvertently break unrelated parts of the system.

Dave Smith avatar
Dave Smith@djsmith42·Nov 5

I've been using T3 Code for the past 3 weeks, and it's incredible. T3 Code makes coding fun again. It really does remove some of the pain that AI has brought to software engineering.

"Why should I use T3 Code instead of Claude Code or Codex?" Short answer: T3 Code is way better for developers. Long answer:

41:49