@danmactough@mastodon.social Engineer • he/him

Washington, DC, US
Joined March 2007
I mean, sure, sometimes I'm not eating chips and guacamole, and I feel pretty happy. But if I really think about it, if I just had some chips and guacamole to eat, I'd be even happier.
1
12
Dan MacTough retweeted
Oof. See, this is why I’m not worried about “pure” LLMs in the long run. There’s new evidence that the human brain doesn’t use natural language centers for logical reasoning at all. Study just came out where stroke patients with complete aphasia (near-chance on written comprehension) performed….great on pure logic tasks! Even in healthy adults, fMRI showed language area activation didn’t scale with logical difficulty. tl;dr words are too ambiguous for formal thought and our brain doesn’t use language symbols for logic
321
539
163
5,665
292,813
Dan MacTough retweeted
A short story about deferring tech choices to thought leaders: Early days at Disqus (~2010-2012), we made several frontend choices based largely on what thought leaders were promoting at the time. One example: there was a big movement toward "micro-frameworks." Instead of larger, well-tested libraries like jQuery, you'd stitch together tiny interoperable micro libraries (Ender.js was one). Disqus was an embeddable JavaScript app, so file size mattered. It fit our use case, so we went with it. Then it went live, and we were serving millions of users. The reality of those choices became clear. Micro libraries meant that instead of one good semi-bloated library, you ran 6-7 smaller, less-tested, crappier ones. We burned a ton of cycles fixing bugs and covering corner cases when we could've been shipping product. We made a few choices like this. At conferences, I'd track down those same thought leaders and ask for advice. "I'm hitting problem X, Y, Z. How did you solve this?" That's when I learned my lesson: they rarely had answers, because they'd never reached our scale. Their energy went into promoting new stuff, not running it. You should know this has never stopped. It's happening right now with AI. It'll happen again with whatever comes next. Do your own homework. Test a lot. Don't just go with what somebody tells you.
31
59
15
598
34,548
way happier about this hallucination than actually being intheweights.com #goflyers
2
10
Dan MacTough retweeted
Meta reached to interview me for a principal role the same week they decided to layoff 8,000 people! I’m sure there was at least 1 out of those 8,000 people who got let go who would’ve been a good fit for the role they wanted to hire me for. A few of my staff engineer friends got let go so I know this is true. Instead they: - axe everybody - treat them like a cost - rehire where there’s pain What ever happened to employee retention? Why do companies expect us to be loyal to them if they don’t even try to retain us when they have hundreds of billions of dollars? It would be cheaper financially for them to retain one of those 8,000 people. It would be cheaper emotionally for the people who got let go too How do these big tech companies expect people to put their blood, sweat and tears into work while also saying, “yeah we’ll cut you at any moment.” I don’t know. The culture around AI and layoffs has gotten unbelievably toxic
208
326
49
4,022
1,122,646
Dan MacTough retweeted
Been insane working on this with the team every day. This team is made up with the smartest people i have ever been around We've built a git storage infrastructure layer from scratch, available via an sdk Are standing up single tenant clusters for codegen platforms that want to store large amounts of code And already doing it at insane scale DM me f you have a codegen tool and want the best place to store all the code your users generate
Code[dot]Storage A new Git provider for machines by @pierrecomputer. In Oct, Github shared they were averaging ~230 new repos per minute. Last week we hit a sustained peak of > 15,000 repos per minute for 3 hours. And in the last 30 days customers have created > 9m repos🧵
4
37
9,207
Dan MacTough retweeted
This is what it feels like when Claude is also writing all the code
Replying to @claudeai
Code Review optimizes for depth and may be more expensive than other solutions, like our open source GitHub Action. Reviews generally average $15–25, billed on token usage, and they scale based on PR complexity.
48
213
22
4,470
348,621
Dan MacTough retweeted
15-25 usd per review my lord.
Introducing Code Review, a new feature for Claude Code. When a PR opens, Claude dispatches a team of agents to hunt for bugs.
32
3
7
199
50,910
Dan MacTough retweeted
TIL (thanks to my husband) that there’s a second Slack app you can download. (Slack for EMM) Now I have my work Slack separated from my community Slack workspaces and can use Slack without stressing about unread work notifications during off-hours.
20
15
5
713
130,678
Dan MacTough retweeted
I FUCKING HATE YOU CONSERVATIVE AND NEOLIBERAL PIECES OF SHIT WHO WANT LIFE AND DEATH SERVICES TO BE RUN "EFFICIENTLY." FUCK YOU ALL. WE SHOULD ALWAYS HAVE MORE AIR FUCKING TRAFFIC CONTROLLERS THAN WE "NEED." PEOPLE ARE IN THE FUCKING SKY. GOD DAMN YOU MOTHERFUCKERS TO HELL.
1,152
6,415
134
74,121
1,925,624
🎯 Once You're Laid Off, You'll Never Be the Same Again mact.me/8g
58
People have to implement those inventions. Your company wants implementers to be efficient so they can move on to the next invention. This is not a hard concept. Besides, everyone innovating all the time is chaos, not to mention delusional to expect.
Replying to @scarletinked
But if tech workers are adding huge value - invention their company (or the world) hasn't seen, then their work is hard/impossible to measure. They can guess, but not predict their work. For more on why, read on in one of my more popular articles. buff.ly/4hZSH7R
86
This is honestly what turns a lot of people off TypeScript. Eejits set it up so that it blocks your dev server when there's a type error. JUST LET ME BUILD
💡Dev tooling is a lot friendlier to work with when "fail the build" is not the same as "fail CI". Linting, testing, type checking, etc. - none of these things should stop your ability to build & test locally in most setups. But blocking merging a PR is a different story.
14
9
1
130
38,933
If you want to have a solid and coherent API, you really need a few opinionated API designers. Anything else is often counterproductive.
12
22
3
256
44,350