Writing code is a small part of everyday's job of a software engineer. The article's table reflects this fairly well. AI compresses implementation time for an individual engineer, but architecture decisions, design…
Such headlines sell well, but it's the same marketing mantra about ever more powerful models. And what does it say about the company engineering practices of performing tests?
How do you solve multi-device sync and conflict resolution? The model seems simple, but may leak Git semantics to the surface. How does it keep the high-frequency history useful: does it squash it periodically? Durable…
[flagged]
[dead]
Writing code is a small part of everyday's job of a software engineer. The article's table reflects this fairly well. AI compresses implementation time for an individual engineer, but architecture decisions, design…
Such headlines sell well, but it's the same marketing mantra about ever more powerful models. And what does it say about the company engineering practices of performing tests?
How do you solve multi-device sync and conflict resolution? The model seems simple, but may leak Git semantics to the surface. How does it keep the high-frequency history useful: does it squash it periodically? Durable…
[flagged]
[dead]