The main difference could be that you have an existing code base (probably quite extensive and a bit legacy?). If the llm can start from scratch it will write code “in its own way”, that it can probably grasp and extend better than what is already there. I even have the impression that Claude can struggle with code that GPT-5 wrote sometimes.
An interesting fact about the early GTA games is that they owe their success to a bug. The cop cars were supposed to behave nicely like in every other game, but due to a bug in pathfinding they just drive straight into the players car. So at least to some extend the whole billion dollar franchise owes its success to a bug:
https://medium.com/@bdunn313/the-psycho-cop-bug-de9121335cf9
After reading through the other comments about bending spoons and reading yours again: the bending spoons CEO is technically telling the truth! They intend to run the acquired companies forever. After cutting most of the staff, but he didn’t say that part of course.
I wouldn't even say it's "technically" the truth. It's just the truth. Nothing in the statement even comes close to implying that there wouldn't be layoffs. Hell, one of the quotes even mentions "focus", which if anything is a euphemism or hint for downsizing in these kinds of statements, not the opposite.
"excited about this partnership, which we believe will unlock even greater focus for our team and customers as we continue to strive towards our global mission to be the most innovative and trusted video platform in the world for businesses"
There's no hint of laying off all the staff here though. Now it sounds like they "were" excited to lay off people to maximize profits.
Maybe "unlock even greater focus for our team" means to unlock their focus to find other jobs but it's quite perverse. I agree with the OP, that "Words no longer appear to mean things"
> There's no hint of laying off all the staff here though. Now it sounds like they "were" excited to lay off people to maximize profits.
What? Just because a statement says "we're excited to do X" doesn't mean they're not also planning to do A, B, C, Y and Z.
I'm not defending the layoff. It just seems weird to interpret the statement itself as somehow being misleading about a subject that it literally didn't mention.
There's letter and spirit of the word. You're arguing against the spirit of the word because the letter of the word is technically impossible to prove as a lie right now.
We call this lawful evil logic for a reason. It's how you empower stuff like Jim Crow laws (or the current US administration in general. "Well he isn't going to actually invade a NATO ally, he's just saying he wants Greenland. I want a Ferrari!")
You want the truth? You can't handle the truth! :-)
Those words weren't truth. Truth would have been to state the intent to fire employees in order to maximise profit. This was always going to be the outcome, and it was expected, why not just state it clearly?
Again, when truth becomes a grey area that is to be manipulated for maximising profits that benefit a minority of privileged individuals, we should be concerned and at the least, not normalise it with "its just business".
I don't like layoffs, but if the statement in September said "we are going to lay off most of our talent in January for blah blah blah corporate mumbo jumbo", it'd suck but I'd see nothing wrong with it. The employees get a 3 month warning to plan around, and the company can do whatever it wants from there.
A reasonable person, when told "Company A is buying and will operate Company B," would interpret that as "all of Company B" including its assets, liabilities, cash, property, patents, AND employees. They would not think "Well, ackshually, they're just buying the corporate entity itself, which doesn't technically involve keeping the employees..."
If "reasonable person" means "someone with literally zero experience reading any business or acquisition news whatsoever" then I agree with you. Hell, the OP literally begins the announcement with, "As expected."
if corporations only exist to make the rich richer, maybe it's time to eat the rich. Corporations' outward goals used to be to satisfy their customers. That may have never been the internal case, but it isn't even pretended to be so nowadays.
Severely downsizing the company isnt a good vibe to a customer. I'd definitely be migrating off Vimeo if I did any serious business with them.
Any reasonable person who has paid attention to business news over their lifetime would not be surprised to see layoffs following a corporate acquisition.
It might be 1), being an early adopter doesn’t help much with AI. So much is changing constantly. If you put a good description of your architecture and coding guidelines in the right .md files and work on your prompts the output should be much better. In the other hand your project being legacy code probably also doesn’t help.
We find across our team different people are able to use these things at different levels. Unsurprisingly, more senior coders with both more experience in general and more experience in ai coding are able to do more with ai and get more ambitious things done more quickly.
A bummer is that we have a genai team (louie.ai) and a gpu/viz/graph analytics team (graphistry), and those who have spent the last 2-3 years doing genai daily have a higher uptake rate here than those who aren't. I wouldn't say team 1 is better than team 2 in general: these are tools, and different people have different engineering skill and ai coding skill, including different amounts of time doing both.
What was a revelation for me personally was taking 1-2mo early in claude code's release was to go full cold turkey on manual coding, similar to getting immersed in a foreign language. That forced eliminating a lot of bad habits wrt effective ai coding both personally and in state of our repo tooling. Since then, it's been steady work to accelerate and smooth that loop, eg, moving from vibe coding/engineering to now more eval-driven ai coding loops: https://media.ccc.de/v/39c3-breaking-bots-cheating-at-blue-t... . That takes a LOT of buildout.
I don't have any links but you can start with CLAUDE.md and/or AGENTS.md and put the basic instructions in there ( you can also google these filenames for examples and recommendations). I also put README.md's in every subfolder to describe which file does what, etc.
Probably depends on where you are, but here in Europe I always joke that you should prepare for the exact opposite of what apple weather tells you. A lot of times I’m literary standing in the rain and Apple tells me the chance for rain is 0%
Right, but Dark Sky had that issue too. When precipitation has hyperlocal variation, you're always going to have that problem.
The Doppler radar that "live" precipitation comes from takes 4-6 min to complete a scan, and then obviously it takes a few minutes for that all to be ingested, update models, and push to devices.
The "live" weather from Apple (and when it was Dark Sky) has always been a prediction from about 10 min ago. And if it's raining where you are but dry six blocks to the north (as happens all the time), it's understandable why it gets it wrong.
Dark Sky almost always over predicted rain for my area. I think that was kind of their strategy. That said, I very much miss Dark Sky on android.
Also I really like a tool called Forecast Advisor. https://www.forecastadvisor.com/ . It shows you the accuracy of various forecasting services for your area.
I use it whenever I travel. I don't stick with one forecast site because depending on the terrain/location their accuracy changes drastically.
Certain models are better for certain geographical features depending on the location. I tend to hangout around a lot of mountains and the difference in forecast models makes a huge difference.
That is basically my impression here in the US PNW. If it tells me rain is about to start at my location, the one thing I know with 100% certainty is that rain is not about to start any time soon.
A second phone market has never been a thing. History is filled with failed attempts.
They should focus on the largest potential market: parents who buy a phone like this to text with their kids without allowing them to have a completely internet connected phone.
From my experience as a parent, that market is also very small, because the time between “child is old enough to text and be away from parents for long enough” to “child wants to have a real phone” is not that long.
Is there any potential market of parents like this: "my child wants a real phone, but I won't give them one because they'll melt their brain with tiktok and instagram"? I'm not a parent, but I imagine I'd feel something like this.
The problem is other kids will get real phones and use them to talk to each other and your kid will be left out. And unlike the old days, kids can't just ring up the house line to chat.
kinda comes across as building what they want personally, what resonated with me was the potential for just a simple merging of modern stuff with older styles, the beloved blackberry, paired with headphone jack, and sd card, toss in a removable battery? already a fairly viable product with stock android and no other changes.
the curated display or whatever... its just push notifications in the order they were delivered.. is this not just what modern push notifications already do? my default is to immediately have push notifications off, unless its a vital app. i assume anyone serious about using their phone as a tool rather than an entertainment device is operating similarly, and they'd be the target market if im reading into this correctly.
Hope that simple idea for the colored button based on what your notification is will catch on, thats pretty neat design.
This is 100% the reason. I watched BlackBerry fail from the inside and there’s always been an extremely vocal minority of former BB users who want to go back to a physical keyboard. This is a niche product for that audience at best, it will never have mass market appeal as a primary device. I don’t think it will have mass market appeal as a secondary device for the same reasons as others have pointed out in this thread either, but I respect them shooting their shot I guess.
Blackberry made regular slab phones too and they were massively outsold by the keyboard ones. Why would anyone buy a slab phone running an obscure OS that lacked any major apps, when Android and iPhone were available? The keyboard was always the selling point.
The fact of the matter is that the smartphone market could not support more than a few players. Blackberry was just one of several vendors without vertically integrated supply chains that disappeared: HTC, Nokia, LG and Sony all abandoned the market as well.
You’re operating with massive hindsight bias here. It wasn’t a foregone conclusion in 2007 that iOS and Android were going to win. BlackBerry (and indeed many of the players you listed) had a chance to compete and they simply didn’t. Also I’m not sure where you got the idea that BlackBerry didn’t have a vertically integrated supply chain. They absolutely did. I worked there in the mid-2000s and the hardware was manufactured literally down the street from where the OS and apps were built.
I recently build a small framework to create JavaScript apps that use this kind of URL sharing and therefore don’t require a backend: https://github.com/grothkopp/lost.js
I think this is most likely what happened. The update/review process for extensions is broken. Apparently you can add any malicious functionality after you’re in and also keep any badges and recommendations.
Lost.js is a lightweight, zero-dependency framework for building shareable "vibe coding" apps and prototypes.
A week ago my wife asked me for a "wheel-of-fortune"-style app as a fun way to choose random climbing routes.
I thought that's something I could "vibe-code" myself in a few minutes. But then, as always, comes the user-management, db setup, backend development, etc.
So this time I thought I'll do it differently and the result is lost.js: a framework (or toolkit, or maybe just template? I can't decide) that is small, has zero dependencies and no need for any backend.
The data/objects are stored in local storage in the users browser. But they are shareable, via special URLs containing the whole data in compressed form in the URL hash. The lost-apps are all PWAs by design and work offline once they're cached.
So if you want to code a small tool, that lives in a browser lost.js can be your starting point and allow you to focus on the tool itself without worrying about backends or user-management or sharing.
I have multiple devices with lithium batteries plugged in 24/7. A kindle that I use as a display for example. So far nothing exploded. If exploding kindles were a thing I guess I would have heard.
I have not had anything explode, but I have had Macbook batteries expand on me on two separate occasions to the point where the case was visibly warped. Both times I was away from home, so it was extremely inconvenient.
I flashed it. Don’t know if always on works with the browser. But jailbreaking is easy and I think even reversible. Then you can ssh into it and even setup a cron to download a picture and refresh the screen.
reply