Should make this clear. I don’t think there’s anything wrong with it, just that Silicon Valley rarely represents the rest of software development.
Jfc I worked with “senior devs” (especially consultants) where I was happy they could open an IDE let alone ship usable code.
The other huge difference is, while there’s truly some incredible engineers in SF, there’s just as many entrepreneurs. Again, nothing wrong with that, just keep the context in mind when evaluating people’s tech takes / opinions.
2
702
Not to pick on Thorsten here, but this (and much of the current discourse) is a great reminder that SF companies building dev tooling, where their own team is the customer, aren't representative of the rest of the industry. The context these teams and people work in is so inherently different that it's tricky to have a fruitful conversation. 160 characters aren't enough to agree on a framing first.
Sure sounds like a lot of people don't trust their colleagues to work like this was their own project.
6
2
110
7,803
Been a professional @AirCanada hater for a while. While I am still salty of their questionable business practices during COVID, I gotta admit they really stepped it up over the last while. The app is easily the best airline app there currently is. And service seems like it has improved as well. 🫡
1
201
Missing from the whole AI conversation: what does the career path for junior engineers look like now?
For senior devs this is heaven. We finally get to build all the things we had in our heads.
But we only had those in our heads because we ran into the problems before.
Juniors never experienced that part. I've watched a lot of people's growth stall after 3-6 months, and their output with the models hit a ceiling.
So how does a junior become a senior without coding?
Reminds me of math in grades 1-4. Calculators always existed, but we had to do by hand for a reason.🤷♂️
1
2
163
Why can ChatGPT/Claude generate outfits, but then can’t find me the clothes online for me to check out? 🙃
2
288
Most important part missing. Switch to @useblacksmith 🫡
Agents were shipping code faster than our CI pipeline could keep up.
Our team optimized our pipeline, leading to a roughly 15% faster test suite and 50% reduction in runner-time spent per test, all while our test suite grew 4x in size.
@moofeez explains how:
linear.app/now/ci-bottleneck…
1
2
7
1,027
Now that some features have been added (and things like cmd + f work), I can finally play with some ideas I've had around making PR reviews more effective - yes, i still read code.
A few experiments 🧵
Was thinking about a few enhancements to codiff. But @t3dotcodes had some of them already. So I downloaded t3code today, and brought my favourite part of codiff - walkthrough into t3.
Not loving the idea of t3code yet, but maybe it will grow on me with this.
2
133
5. Funny enough, the more I look for ways to understand a change beyond just reading the diff - given I don’t fully trust an AI agent to do the review for me yet - the more I keep finding ways to give the agent better context.
And at some point, that might actually make it better at reviewing the PR than I am. 😅
1
17
And another s/o to @t3dotcodes for being open source (and easy to fork locally).
Every one of these experiments is basically a prompt away, and the product is already good enough that I can use it in my actual day-to-day work while trying these ideas as a POC.
That makes it a pretty fun place to test out what a better PR review workflow could look like.
16
Was thinking about a few enhancements to codiff. But @t3dotcodes had some of them already. So I downloaded t3code today, and brought my favourite part of codiff - walkthrough into t3.
Not loving the idea of t3code yet, but maybe it will grow on me with this.
1
1
2
268
