This has been my experience on a recent small project for a client. I took effort to understand and prepare the spec before feeding it to Claude Opus. Yet, the result was slop full of defects, and one that I did not understand well at that. I just did not have a mental model of it. I just thought, there's no way I could ever feel confident about this code, something is missing. It did not take me long to write the important parts myself, from scratch and develop that mental model.
Then I would use Claude to make a small fix, write a unit test (write a unit test, not suggest what they unit test should be) or write some less important UI code. It just felt like old school development, with some assistance. I think we may see a shift back to a "copilot" mode and by the way, I still use GitHub Copilot. The $19 subscription includes $30 worth of credits and the autocomplete in VS code that uses some cheap model is completely free. This autocomplete is very good and I would like the market to focus more on IDE integrations. The agentic thing is either ahead of its time or it will never have time. Time will tell. I think the LLM can only be as good as the training data, so it will always excel at small chunks, but to implement entire projects of which there's such variety, I would question that. And also, how using it to implement entire projects means the developer does not hold the program model in the mind, which leads to more issues long term.
By the way, in this way of working, I see no difference between Sonnet and Opus. Sonnet is good enough to use as an aid.
> I just assumed that readonly properties will always be pretty performant in general.
This is also the case for variables. var is faster than const, because for const (and let) the engine must do additional work (related to enforcing block-level scope, if I am not mistaken).
To my understanding today it depends on the JS engine and more importantly what JIT stage that code is in. JITs optimize const/let in ways that they can't optimize var now.
Which is to say that if someone tells you that you should in general never use const/let for "performance" they are probably wrong, but yes there probably are still edge cases and microbenchmarks that make var look faster on some engines.
15 square cm box? Wow. Are there similar size, but less powered (and cheaper) workstations? I need a box that can build chromium reasonably fast and I would rather have something portable like this than a PC tower, but this is an overkill at $4k.
It's 195 x 190 x 60mm and takes a standard ITX board. You'll need to relocate the hole for the fan depending on your motherboard, but CAD files are available and you only need to change 2 parameters (X,Y of the hole center).
BTW mine was upgraded to 64GB RAM and a 5700G (zen 3 APU) but it died and I'm still trying to bring up a newer board - still socket AM4.
BTW to get the center coordinates of the hole, measure from the edges of the board to the top and bottom of the metal plate under the CPU socket and take their average distance. That plate is symmetric and centered under the hole.
Bedrock does not have GLM 5.2 and likely will not for quite some time. It seems like they are doing that on purpose due to pressure from Anthropic. DigitalOcean has it though.
reply