71–80 of 181 posts
That README hits all my “this is authored by an LLM” instincts. I presume the codebase is also written by an LLM?
Be advised that the firm behind it ("sqliteai") had a nasty history of using non-open source licenses, e.g. Elastic License. I advise against using anything by them for this reason even if this project currently has an open license.
Are these the sqlite developers..?
Claude might as well be .5 tok/s. I end up waiting several minutes and what it tells me could usually be summarized in under 100 words. So I could potentially live with this if it was concise.
Claude might as well be .5 tok/s. I end up waiting several minutes and what it tells me could usually be summarized in under 100 words. So I could potentially live with this if it was concise.
So if this Mac uses 30-50W, that's 40-60 tok/Wh...vs maybe 80k for a modern GPU cluster? So that's about 1000-2000x more power for the SSD streaming, unfortunately.
Claude might as well be .5 tok/s. I end up waiting several minutes and what it tells me could usually be summarized in under 100 words. So I could potentially live with this if it was concise.
This is not how thinking works. Claude uses tens of thousands of thinking tokens to get to 100 words. Kimi is no different.
Claude might as well be .5 tok/s. I end up waiting several minutes and what it tells me could usually be summarized in under 100 words. So I could potentially live with this if it was concise.
This is not how thinking works. Claude uses tens of thousands of thinking tokens to get to 100 words. Kimi is no different.
Earlier quoted context omitted.
Then have it summarise the meeting transcription over the entire week for the report next week . ftfy.
If we estimate a meeting with pauses between speakers as 2.25 words per second, and .75 words per token, then a meeting generates 3 tokens per second. This says prefill and decode are both .5 tokens per second? Then each hour of meeting turns into 6 hours to read and 1 hour to output a summary. You could summarize two hours of meeting overnight, not too bad.
That README hits all my “this is authored by an LLM” instincts. I presume the codebase is also written by an LLM?
i thought, here on HN, we were past the "oooh it's written by a LLM it's bad!". I care about the craft, well designed systems, good clean architecture and code, etc... But i also care about reaching goals. Whether i do it working on my own, or with human coworkers or with AI coworkers doesn't matter that much to me. Yes, the result is sometimes the most important thing.
Lately I've been landing on a couple of different reasons but I don’t think it’s one size fits all:
- Ego/identity - “I am the crafter of code. That is what I do.” If someone has their identity deeply wrapped up in the concept of being a “software engineer” or “programmer” then LLMs are a direct threat to that. People don’t tend to do well with this. Think about dogmatically religious people, pseudoscience followers etc who are confronted with evidence directly contradicting their beliefs. Their entire world view revolves around that identity and if you threaten that, you threaten the foundations of their self-perception.
- Career - you can take a lot of what I said above but also map it to threatening someone’s career. What if crafting software by hand becomes a niche, artisanal craft but most software is industrially generated? A lot of people will experience hardship if so and if they can’t find a way to be flexible into the future.
- Passion - the ones who love software purely for the craft see this change as robbing them of the one thing they enjoyed in their career. Work is a big part of our life and if you kill the joy for a large group of people, that’s tough to deal with.
- Lack of understanding their current purpose in role - I often see software engineers who don’t realize why they were hired. It was never to “write good clean code”, that was a means to an end. The end is generating business value for the company that hired you. That’s really it. It’s banal but it’s just a job like bagging groceries only it has required specialized knowledge so it pays well. Only very niche roles have actually hired for the craftsmanship. If someone is working for Groupon and they believe perfectly elegant systems are the value they provide, they are a bit deluded IMO. They build a platform that peddles coupons. That’s hardly comparable to building software that allows a surgeon to remotely operate a robot that does open heart surgery. Most of us do not work on truly mission critical software like that.
Most importantly though, I think this topic needs to be approached with empathy. This is truly a seismic shift in how we, as software developers, work. Change is not easy to cope with especially when it threatens physical safety and identity. Will this change be here to stay and are we in for the extinction of software creation as we have known it? I don’t know. I do know that the world’s financial and governmental systems do seem to be betting on that outcome, however.