joshstrange
Straight informational websites with rare/few edits can much better be handled with LLM-coded websites deployed to something like Cloudflare or just static hosting.
My first EN05 board had a problem with the battery and I just got the replacement a few days ago and haven't had time set it up or do long-term tests. I also was blown away by the WiFi vs BTLE power usage. I love ESP32 but for battery powered I'm looking closer at BTLE. I actually have 3 ESP32's around the house to act as BTLE proxies for Home Assistant which I can use with OpenDisplay as well.
And yes, it's a great form factor, it looks great, and just makes me smile when I walk by one. Once I can solve the "more updates, less recharging" I plan to frame a number of these to hang on the wall.
OpenRouter could so 90/10 split and it still wouldn't mean open models are beating (in usage) closed models.
Currently I have a handful of the all-in-on seeed studio reTerminal E1001's that rotate book quotes I've highlighted on my kindle (jailbroken, KOReader+BookOrbit) once a day so they can last months on a battery charge. But with BTLE you can go years on a single charge, update more often, and push to the device to force an update (all things not possible when deep-sleeping wifi for 23.99 hours out of the day).
e-ink displays are so nice and once I get the BTLE+OpenDisplay setup perfected I'll probably grab ~10 more boards/displays for other places around the house.
I want to be clear, the ability to speak English is not what I took issue with. That doesn't bother me and I'm fine with just showing the phone screen, no conversation. The issue I had was cutting the line and essentially demanding they be helped immediately. Wait in line like everyone else. This is a small food stall in a food hall with often just 1 person working the front. If they are actively helping another customer and have a line, I find it unacceptable to think you can cut to the front and immediately demand attention. What message does that send to the customers in line? "You're less important than delivery orders", and I can tell you that isn't the case due to the large chunk that DD takes.
My family member has even considered shutting down DD orders temporarily if/when the drivers act this way and publishing on social media about it. According to them, the loss in sales (and overall profit, which is minor on DD orders) wouldn't matter compared to the publicity/engagement (I don't know, that's not my world).
> to Help Local Stores Win
Any local store will tell you DD is a necessary evil they put up with but strongly dislike overall. From the % of sales they take to the incredibly rude delivery drivers, DD is not well liked.
On multiple occasions a family member's employees (or they, themselves) have had a DD delivery driver cut to the front of the line, interrupt the cashier, and shove their phone in their face. No words, no anything, just "here is the code/screen/whatever I need to show you to pick up the order". DD doesn't let stores rate delivery drivers so there isn't any recourse.
Then again, it really doesn't matter to me at all what the screen looks like or what features it has, I use my MBP docked 99% of the time with the screen closed, to the point that my next computer will almost certainly be a Mac Studio and I'll just use my MBP on the rare occasions I need it on the go.
Sort of? Yes, OpenAI has been bad about slow rolling but Anthropic's last few models have been available essentially at the same time as they announced it. In most cases I updated Claude Code and was using the new model right away.
Compare that to OpenAI who sometimes says "Available to all Plus/Pro/etc plans" without saying anything about "rolling out" and then it's a crap-shoot on when access will actually roll out. That said, they have gotten better, it used to be 1-3 weeks sometimes to get a new model/feature they announced was available for your plan.
And then there is Google... Who loves to talk about models like this and then give no timeline for release. Even when they do release the models it's miserable to find out how to even use it. Is it in the API? Which API? Google Cloud/Vertex/Gemini Cloud? Whatever it's called this week? Coding plan?
No, what Google does (or rather fails to do) in its rollouts does not compare to OpenAI/Anthropic.
As for the AA page, it's just embarrassing. Any smaller company doing that would get roasted, Google doesn't get a pass, learn how to coordinate or wait for something to actually be true/live before posting.
Clicks link
Carbon isn't anywhere on the page and you can't toggle it on either. I'm sure it's just timing and it will be there soon but still just look amateur, which is about how I feel about Google and AI overall. I know the models have improved but I still have a bad taste in my mouth from testing Gemini in the past and I still feel that Google has an overly complicated "how to use our models" that changes way too often. That coupled with "you could lose access to your google account if we don't like what you do with Gemini" means I have little desire to test it out.
On top of all of that I'm completely over announcing a new model that we can't actually play with or try out. I don't think Google is lying about how well their model scored exactly but it still has big "my girlfriend goes to another school, you don't know her"-energy.
The objection in the article is specifically about offloading thinking to technology, which is something we've been doing for decades, or depending on your definition, since we first started using tools.
If offloading cognitive labor is the core problem, then what makes AI fundamentally different from the countless other technological advances that have allowed us to offload cognitive labor?
Personally I have an agent review the feedback and break down each item so it’s easier to review (helps remove some of the jargon/short-hand that agents use sometimes). Then I decide what to have an agent address and what to push back on. Like I said, I’m working on finding a way to automate part of that but haven’t settled on one I like yet.
> Is it still a controversy nowadays?
Reading HN would leave one with the conclusion that yes, it is still very controversial. We still have plenty of people who swear they will never use AI, who say it's trash, it only produces slop, that a reckoning is coming, etc.
See this post from today: https://news.ycombinator.com/item?id=50256738
We also settled on a custom solution for reviews. We started with reviewers that claude/codex on GH actions and those were "ok" but kind of dumb and hard to tweak (GH Actions is just miserable to debug/iterate on). We still use them occasionally (@tag them to kick off a review) but we've shifted to a piece of software that we wrote that watches GH PRs and once certain labels have been added and the ticket in our ticket tracker (not GH issues) is marked as "Ready for Review" it kicks off a review and it reviews _all_ the PRs connected to the ticket. We don't have a monorepo, yet, so a new feature might span 3-4 repos (server, client1, client2, ...) and we want that work reviewed together.
We are close to having our review code spin up a fully isolated devstack running all our, many, services so it can poke around in the UI and write custom playwright scripts to test the new functionality. We have the devstack VMs working, just gluing the last of it together, it's pretty cool to see it all come together.
- Slow PR review
- Nitpicks on style, not substance
- Async waiting for review or re-review after making changes, harder to stay in what passes for a "flow state" nowadays
- A lot of a ceremony around straightforward changes
We use LLM reviews at my company and it's caught things human reviews have not (as in in the early days we human-reviewed code and then did tests running the LLM afterwards and it caught things we didn't). It can review code at any time of the day and re-review it just as quickly as you can address the feedback.
I predict we (my company) are less than a year out from having a fully automated pipeline for reviews with only humans getting called in when it touches certain parts of the code. We already have a crude system for detecting certain file paths that we want a human to review if touched and we tweak that list over time as needed.
Being completely engrossed in the new trends is probably not necessary, but keeping abreast of what’s possible and trying new things is. People who have an ignored/avoided LLMs completely are not able to just pick them up today and be as productive as people who have been learning the best ways to use them over the last couple years.
Many of the “skills” are not new, it’s the same skills you’ve been using throughout your career, just with a new tool. But any new tool requires practice and learning what it’s capable of.
I’m constantly experimenting around the edges of what LLMs are good at because it keeps changing and just because an LLM wasn’t good at X task 6 months ago doesn’t mean it still isn’t good at it today. The only way you can know is by testing and trying out things.
I work with a number of smart people, but their LLM proficiency is a wide spectrum. LLMs might/are a leveling factor, but there is still skill in getting what you want out of an LLM. This is most apparent to me when I interact with people who aren’t developers or aren’t as technically savvy. They just aren’t able to produce or get the same things out of an LLM that a developer or more technical person can.
Look, I know it’s a huge shift but there is no way around it, 6-12mo ago LLM usage might have been optional or up to each employee but the models and harnesses have improved to a point that not using them is just cutting off your nose to spite your face.
I’ve reviewed plenty of code pre and post-LLM and while LLM code is not perfect, neither was the human-created code (mine included, obviously). Missing/no tests, issues that are minor but you don’t want to send it back _another round_, coworkers/employees that don’t make the changes you ask for or do it in a hacky/quick way, and generally accepting code at a level under what you wish because you can’t wait for the code to be perfect.
Now the ability to write solid code is available to all your employees and so the desired skills shifts. It makes sense to re-evaluate your workforce when that happens.
If an employee/coworker wasn’t using LLMs today I’d tell them to either start or consider finding another job because they’d be dragging down the company.
Writing code by hand is dead. It just is. In a couple years this won’t be controversial, just accepted fact.
The downside to jailbreaking was often the instability but that was also back when the phones were way less powerful. Today, armed with LLMs, I would love to have root on my iPhone again. I'd love to rip out Siri and replace it with Claude Code or something like that.