@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
@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🫡
@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…
@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 🫡
@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
@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.”
@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.
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.