Comment by locknitpicker

Comment by locknitpicker 10 hours ago

5 replies

> It also has TypeScript which pairs well with agentic coding loops, (...)

I've heard that TypeScript is pretty rough on agentic coding loops because the idiomatic static type assertion code ends up requiring huge amounts of context to handle in a meaningful way. Is there any truth to it?

miguelspizza 8 hours ago

Not sure where you heard this but general sentiment is the opposite.

There was recently a conference which was themed around the idea that typescript monorepos are the best way to build with AI

  • locknitpicker 4 hours ago

    > Not sure where you heard this but general sentiment is the opposite.

    My personal experience and anecdotal evidence is in line with this hypothesis. Using the likes of Microsoft's own Copilot with small simple greenfield TypeScript 5 projects results in surprisingly poor results the minute you start leaning heavily on type safety and idiomatic techniques such as branded types.

    > There was recently a conference which was themed around the idea that typescript monorepos are the best way to build with AI

    There are also flat earth conferences.

    • conartist6 3 hours ago

      It's especially tricky since monorepos are an obvious antipattern to begin with. They're a de-separation of concerns: an encouragement to blur the unit boundaries, not write docs, create unstable APIs (updating all usages at once when they change), and generally to let complexity spread unchecked.

aizk 5 hours ago

I think this is contingent on the skill of the human reviewing the AI's code.

[removed] 9 hours ago
[deleted]