Forget all the reasons why it won't work and believe the one reason why it will.

Israel
Joined April 2022
רמה גבוהה AIG, רמה גבוהה נראה ש *אתם* שכחת להוסיף ערכים, לא אני.... @aigisrael
1
1
22
#ADHD and #AI are a great combo. Because of the way my brain is wired, throughout my life, I had to build systems that would help me accomplish things. You must be able to work in cause while maintaining order. And that's exactly how I write software. And by taming AI to the way I work, I'm able to do a lot of very different things on a single branch without worrying about collisions. Applying the same principles in dev teams is straightforward. This is a huge win that companies could benefit from today.
1
2
159
Alex Raihelgaus retweeted
the rewrite of the TypeScript compiler into Go is going well 🫠
35
22
12
1,165
139,663
Your LLM should write the script. Not BE the script. Most teams have it backwards. They pay the model to redo the same task over and over.  Same prompt. Fresh bill. Every time. Here's what fixes it: Need to convert 2,000 rows of CSV? Don't paste them into the chat and pay per row. Have the model write the script once, then run it for free. On 2,000 rows or 2,000,000. Opening PRs? Scaffolding the same component for the tenth time? Renaming a pattern across 80 files? Same rule. Spend the model once to build the tool. Then the tool runs on its own, the same way every time. That's the whole idea: use the expensive, unpredictable part once to manufacture something cheap, predictable, and reusable. And here's the part that's actually about money: the token bill is the cheap part. The expensive part is ten engineers each using AI a different way. Different cost, different quality, no shared standard. Turn those scripts into something your team's AI assistant reaches for automatically, and even the dev who's never heard of it ends up doing it right. That's not a tip. That's a standard. Getting an engineering org to actually work this way, one standard instead of ten, is most of what I do now. I wrote the whole thing up: the examples, the honest nuance, and the one mistake that quietly cancels the savings. Link's in the first comment. #AI #SoftwareEngineering #LLM #EngineeringLeadership #SDLC #DevProductivity
2
2
67
In private conversations I have with Founders and tech leads, they share similar insights.
Notes on 100+ Recent Technical Interviews I interview a ton of engineers. Recruiting is the single most important technical CEO activity. Here are a bunch of impressions 1. There is a severe ZIRP engineering overhang that is currently washing out. They're getting laid off, managed out, etc. after having been massively overhired around 2020-2022. This is worst for Tier-2 big tech (think PayPal, Bill, etc.) but also FAANGs. These are overwhelmingly bad engineers. 2. This flood of unqualified but good-on-paper candidates makes this the hardest SF hiring market I have ever seen, due to the amount of nominally strong-looking candidates that you need to grind through. 3. I am highly skeptical of "AI as a cause for engineering layoffs". I think this is a large-scale polite fiction -- the companies don't want to admit they overhired, the engineers don't want to admit they are bad at their jobs. Everyone's blaming AI when it's really just the market rectifying itself. 4. Many of these engineers appear never to have had a real engineering function at their corporations. They're sitting in meetings, "making decisions about technology" but are unable to write software. I leave many interviews baffled by what exactly they were doing for so many years, let alone what their manager was doing. 5. I have interviewed some engineers from FAANG companies so shockingly nontechnical that I am forced to conclude that there is either (1) a lot of resume fraud going on or (2) that there are kickback grifts within those organizations -- people hiring their cousins and splitting the pay, that kind of thing. I have no other explanation. 6. There's a fun side-effect where after interviewing 20+ people from certain small but public companies, I actually feel like I am gaining a short sellers' advantage: there are financial technology companies out there that, knowing what I now know, I would never deposit a single dollar into. 8. Based on this "exhaust" data, and extrapolating a little bit, maybe aggressively so: I think folks like @pmarca are basically right when they say that ~every tech company is overstaffed by a factor of 2-4x. Whatever the reason -- staffing ahead of need, monopolizing certain engineer types (Google-style), headcount-driven promotion incentives, the reality is that a lot of these companies are not being run for the shareholders. The aggregate SBC expense is insane, and I expect this is going to get rectified eventually. I'm sure that AI will play a role in rectifying this -- but I fear that people are going to blame AI for taking people's jobs when the reality is that the jobs were already long-gone, possibly always useless, but the highly-paid butts-in-seats remained. People will be mad at AI for taking away their lucrative sinecures. Maybe that's the same effect from a public policy perspective, but it feels different morally.
17
You wouldn't hire a senior engineer, hand them a laptop, and say, "go build whatever, no specs, no review, no standards." But that's exactly how most teams are deploying AI right now. The result, >>>
🤖 Made with AI
1
14
in most orgs I've walked through in the past year: 6x more code, 2-3x more bugs, 0 ownership of the workflow. AI doesn't need more capability. It needs the same boring infrastructure you'd give any senior hire - a spec, a review gate, a quality bar, and a named owner. Until that exists, the speed isn't speed. It's compounding rework.
9
Forget anything you know about anything
7
seriously, F you @Google . I want to sign in, my ipad is not near me, my phone is, my computer, my everything is, just not the bloody ipad, why won't you let me in!!!!! How can you be so awful at that.
73
Noticed that the terminal takes forever to start up recently? Installed openclaw recently? Check it out - thesashka.com/blog/posts/ai-…
50
And the classic "You got a sex?", to a female.
Been there, done that! 😂
39
Was the API on port 4323 or 4321?" I got tired of this mental arithmetic every time I switched projects. Now I just type sashka-api.dev.localhost. No ports. No guessing. Green padlock. The trick: Caddy + *.dev.localhost wildcard routing. 5 minutes to set up. Never think about ports again.
1
30
Cursor gave us the VS Code experience we know plus AI superpowers. Then reality hit. I wrote a blog post on why the tool that exploded AI coding adoption also killed developer trust—and what actually works better. thesashka.com/blog/posts/tec…
30
On the one hand, it committed a .env without asking me and that's not good. On the other, how cool is that that he responds properly?
26
Awesome evolution found on @bunjavascript docs website. Them giving direct access to their docs via different tooling is plain awesome, saves so much time. I hope more projects would adopd that.
25