PatrickUllrich

@karrisaarinen Almost like features was never 1:1 correlated to revenue in the first place 👀

We keep hearing about 10x or 100x productivity gains in engineering and knowledge work. But outside the model labs, I haven’t seen the corresponding 10-100x revenue growth across the market or increase in quality. So where is the productivity going?

@devagrawal09 @jbogard @jasontaylordev Totally, same reason DDD is being mentioned a lot more lately on X.

@ItsPatrickU @jbogard @jasontaylordev i'd say it's 50-50 the architecture is important to keep blast radius of changes contained to a single slice as much as possible, while the spec ensures the changes don't regress behavior also to allow agents to potentially build and test slices in parallel

Introducing: Specter Supercharge Agentic Engineering with - Typescript Framework for Specs that compile, execute, and scaffold your app - Vertical Slices that can be built, tested, and operated independently Agents can finally work on large complex codebases reliably

@devagrawal09 @jbogard @jasontaylordev But really seems like the spec is really the amazing part here. More than the architecture itself 🤘

@devagrawal09 You are probably already familiar, but I think there is a lot of great repositories & talks in the dotnet world specifically. From vertical slice arch by @jbogard and clean architecture by @jasontaylordev . Been using it a lot as inspo while implementing in TS

@devagrawal09 I hear you. Love what ya doing here, been trying to crack something similar as well. Looking forward to when it’s ready to checkout!

@ItsPatrickU yes but mostly failed experiences because i could never quite get the architecture right and no one i worked with knew better especially with event sourcing, it took a while for things to click for me

@zeeg The API feels very expected and unmagical in the best way possible. As someone only familiar in passing with Junior - it’s immediately clear what I get. Neat🫡

working on adding some determnistic behavior to Junior and could use some opinions on API design github.com/getsentry/juni… first goal is to ensure we have co-authored-by set on commits

@mitchellh AI has reduced that burden. It is definitely way easier to upgrade a project now if it has fallen behind, but tbh. I’d still stay up to date. 1-3 days min release age. The better/practical advice (your 2nd point) is to reduce dependencies and just get AI to gen the func you need

@mitchellh While I agree with the sentiment, in pre AI world letting your deps fall behind you end up paying a huge cost down the line upgrading. Keeping up to date (weekly) is a tiny amount of maintainance. Being 2-3 years behind was an absolute nightmare…

Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored). If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update! I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it. Feeling pretty swell about this mentality with all the supply chain attacks happening.

@karrisaarinen @linear Been loving it. I expected the engineering team or PMs to use the Agent the most, but our CS team is prob the biggest user. Especially now with Code integration, our CS team is asking questions against our code base resolving Qs before it hits Eng. keep cooking 🫡

👋 I run most my agent work through @linear agent these days. First about the setup: - On personal guidance I have set writing guidance (like no emojis), skills I've created to various use cases (like figure out patterns in feature requests), MCP servers (Granola, Slack, Notion). No matter where you trigger it, it will follow your guidance (like address me as white wizard) or use the MCPs. - Linear, web search, code context is built in so I don't have to add it separately. - Workspace level, and also specific instances like Slack and Teams can have their own guidance. As well other services like Gong that can automatically pull customer feedback from calls. Everything is configurable in the UI by users or by admins for the workspace.

@zeeg Genuine Q - why is public work important for the role?

if you want to come work on things like this i have open recs at Sentry $350k to $1m TC you need to have a proven track record, ample public work, be highly autonomous, 5+ years industry experience, and be based in SF or willing to relocate. if your github profile cant compare to mine, its probably not the right fit DM your credentials (or email to david at sentry)

@zeeg Bright future in consulting probably though. 😅

If your claim to fame is coming up with a term I got news for you buddy

@jaredpalmer @Xbox @asha_shar Crazy to think when I chose formik a decade ago I unbeknownst supported GitHub stacks, and now the future of Xbox 😂 congrats, excited to see the next chapter of Xbox, great pairing

Excited to share that I’m joining @Xbox as VP, Engineering & Technical Advisor to CEO @asha_shar I’ll be focused on building world-class tools, services, and experiences for developers and players across the Xbox ecosystem. Grateful for the opportunity and excited to get to work.

@MoBrowserSDK @typescript In the post: “Our current plan is to release TypeScript 7.0 within the next two months, with a release candidate available a few weeks prior.”

@typescript @typescript any ETA on when we should expect RC? 🤗

TypeScript 7.0 Beta is here! Built on a new native and parallelized foundation, it's already being used on multi-million line codebases. Read up more here and try it on your projects today! devblogs.microsoft.com/typescript/ann…

@thdxr As someone who fucking loves cleaning up code as a sweet treat… AI slop cleanup is mentally way more taxing than human slop I found. Might be because AI fundamentally gets something wrong, where humans screw up in the later stages? I m not sure.

i'm thinking about this because no matter how much you try, the existence of LLMs just makes our codebases rot more i feel like having a few people just cleaning up every day without getting pulled into feature work could be good assuming they enjoy it and don't get burnt out

are there people out there who just want to refactor every day? just wake up and find the worst code and just chip away at it and clean it up wake up the next day do it again, infinitely improving things with zero external impact?

@thdxr Yes… it’s a guilty pleasure. And I won’t let anyone take it away from me. 😤

@Netlify @vercel 👀

We just removed seat-based pricing from Netlify. Pro was $20 + $20 per additional seat. Now it's $20/month. Unlimited seats. Here's what changed and why 🧵

Funnily I don’t really care that much about @linear engineering agent. Throughput is really not the issue. Requirement gathering, answering how something should be working, communication is.

What do high velocity engineering teams on @linear use to keep knowledge base / marketing in sync? In my experience when dev team is dialed, keeping CS up to date is becoming the hardest bottleneck.

@NewsFromGoogle Now all I need is swipe / easy way to switch between profiles (like arc spaces) 🙏🙏

Today, we’re rolling out two new productivity features in Chrome. With vertical tabs, you’ll now have the option to move your tabs to the side of your browser window by selecting “Show Tabs Vertically.” We’re also introducing immersive reading mode, a new full-page interface for deep focus.