My wife traded in her Macbook for a laptop. I couldn't believe anybody could live without a proper desktop computer but she proved me wrong. Aced some pretty intense physiology classes just using an iPad + touch pen.
Just got Kimi to use Weave to merge an official update with my (agent) modded installation (kimi-cli is open source!) and it worked a treat … kimi-cli is mostly Python (I think?!)
School ends at 3pm so that the teachers, who work a 9-5 like you, get two hours after class to grade homework and prepare lessons for the next school day.
One of the most depressing days of the year in B.C. is when daylight savings ends, and clocks are switched back an hour in November. The sun goes from setting at ~6pm to ~5pm, and you officially end work with it dark out. I'm very happy we are switching to permanent daylight time.
There's nothing more glorious than those late summer solstice sunsets w/ daylight time, where the sun doesn't set until 10pm. Great for festivals and planning outdoor activities with friends.
The Fourier transform audio examples fooled me. The example sounds and slider for them appeared consistent as far as I could tell... but then again I don't know much about Fourier transforms.
Maybe I'm out of the loop but have to say this is the first time I have seen an LLM generate a webpage with working audio widgets.
Claude Code does empower developers to do deep higher level work. It's easier to generate advanced changes now.
E.g. database optimisations a Senior Engineer might do, such as designing a database partition or creating a complex composite index. The problem? When Claude recommends more advanced solutions without a deep understanding it is easy to miss where the foot guns lie or if Claude got it outright wrong.
It's like being handed a chainsaw when you had an axe. Without good judgement, it's easy to cut down the wrong trees.
You are right, but the responsibility of the final artifact must fall on the human.
Think about what we did before if we didn't have another human around to ask and think together about a problem.
We searched for solutions or more info on Stack Overflow, Reddit , random blogs or HN even. The we tried to evaluate the pros and cons of each possible solution and then decide what to do.
Now we should use the LLM to get that info from the internet (be it from its lossy memorized or better fresh from its search tool). Then try to ask the LLM for pros and cons and follow the links it provided if you don't trust its "judgement".
That assumes the problem is a common one others have encountered, which the examples I gave above certainly were. When you're wrangling with poorly documented legacy code operating under the context of its own internal domain logic (e.g. arcane country specific banking regulations), often the only source of good "judgement" (that's the commonwealth spelling btw) are those in the past who wrote the code the way they did.
This is an area where Claude Code is both valuable and dangerous. It can propose sweeping (correct) changes based on inconsistencies it finds within the codebase. The developer, in situations where nobody more senior is around to answer those design questions, is left making a judgement call based on vibes and what logic they can piece together about Claude's changes.
I can't think of anything scarier than a military planner making life or death decisions with a non-empathetic sycophantic AI. "You're absolutely right!"
reply