I’m starting a new company with few good people and an exciting idea. I appreciate all the support. More updates, summaries, feels, etc will follow. https://t.co/6Ls5sTQXZq
it's made The Pragmatic Engineer search 100x better than the current Substack search
I'm a massive, massive fan
Also had an epic session with @CompleteSkeptic + 700 folks at The Pragmatic Engineer Unplugged in SF, video will be releasing ~next week
https://t.co/R4eO36j2JZ
QConSF highlights the general state of confusion in the industry.
Half the speakers advocate to give agents work in smallish chunks, to avoid them latching into a minor requirement and creating a lot of complexity early just for this minor bit (that could be easily added later). Fleshing out features iteratively.
Half the speakers recommend fleshing out a complete spec with all the edge cases and complexities, and giving this long deep spec to the agent to build, test and ship.
Today we’re launching a new Netlify. New brand, new website, new app experience, rebuilt from first principles.
It’s the biggest change in our decade-long history, and it comes from a bet we made on ourselves.
This is just the beginning.
https://t.co/DpuU1WAIu0
in this post the Claude-Code dev team boast that 90% of claude-code code is written and verified by agents, without a human review. and then they provide some generic tips about what are good tests etc.
but my take is that the real reason they can pull it off is not their amazing auto-testing skills, but the fact that claude-code is essentially a very simple piece of software, they don't have almost any efficiency concerns, no competitors, very little potential of actually harmful bugs or data corruption due to claude code itself, and that many bugs just got swallowed and compensated for by the underlying LLM being so freaking good.
I really enjoyed my talk with @thegeeknarrator last week -- I got to go deep on query execution, and discuss many great things happening in the ecosystem. The intro / info overlays add value, rather than distract, and his voice adds a touch of gravitas https://t.co/y2wiFa3s10
From @almoggavra at @QConSF :
Using S3 as your storage layer gives you a “pick 2 of 3 tradeoff” between:
- latency
- durability
- cost
Because the way to reduce cost is to buffer writes into larger batches. Larger batches are cheaper. If you ack writes when they reach S3, they have higher latency. If you don’t, you have lower durability (you can lose writes when the buffer is lost).
Great concept to have when reasoning about systems!
@qianl_cs@almoggavra@QConSF Yes! As usual, the speakers are next level. I even sat fascinated by a talk on transpiling. Which is as far as it gets from my professional interests…