Sounds like insurance in Canada is very cheap. Here in California we pay about $400/month. This is for a couple with no accidents in 30 years, in the sweet spot of old enough to have plenty of driving record with zero accidents but not too old to have any age-based penalties, so that's about as cheap as it gets.
Apparently when our child reaches driving age we should expect to be paying about $1000/month for insurace. We'll see when the time comes.
In most places it is not, which is a big drawback. Every week I hear on the news how the train shut down some stations or got massively delayed for random reasons. I couldn't possibly rely on that if I need to be at work at a specific time.
Completely irrelevant. I'm not interested in public transport across vast areas from city to city, I can drive or fly for those (very rare) occasions.
Public transport is most useful for the hyper-local day-to-day movement. I'd just want good reliable public transport within my town and neighboring areas.
(Actually I'd prefer to just bike, which requires secure bike parking in all destinations. I can already bike anywhere in town, but my bike will get stolen if I stop anywhere to shop or eat, so I can't do that.)
> Auto insurers don't face a "catastrophic liability" bankrupting scenario like home insurers might in the case of a natural disaster or fire.
This changes with self-driving. Push a buggy update and potentially all the same model cars could crash on the same day.
This is not a threat model regular car insurers need to deal with since it'll never happen that all of their customers decide to drive drunk the same day, but that's effectively what a buggy software update would be like.
Far be it from me to tell automakers how to roll out software but I would expect them to have relatively slow and gradual rollouts, segmented by region and environment (e.g., Phoenix might be first while downtown London might be last).
IME vibe coding works spectacularly for simple one-off scripts that do a fairly simple thing. I can describe the work in ~10 minutes and save 2-4 hours of scripting.
Just last weekend I wanted a script to process a csv file and produce some reports and graphs out of that. I think it would've taken me the 2-4 hours to write it myself. Instead, I had cursor write it while waiting for boarding at the airport, probably no more than 10 minutes.
For codebases anything more complex than that, it starts to fall apart pretty quickly.
In that scenario it works ok only if I do all the work of designing the system and the functions and only let it type in the code for individual strictly-defined functions. So it does save some work which is nice, but it's not a huge win.
Yeah, that matches my experience: LLMs are amazing “script interns” and shaky “systems engineers.” One trick that helps on bigger stuff: force it into a tight loop of (1) write a failing test for a single behavior, (2) implement smallest change, (3) run tests, (4) refactor. When you make the unit of work “one green test,” the model’s tendency to wander gets way less destructive.
Outside of work I've been running a pure vibe-coding experiment where I don't look at the code at all, ever. I'm using this approach of telling it a specific scenario has to work in a certain way (the software relates to financial and tax planning).
The AI bot is very creative at creating a mess even with such tight guardrails. Many days into it I discovered that it had implemented four completely separate tax computation routines. All of them buggy in different ways. All of them addressed specific scenarios I had specified as part of the spec. But it never occurred to the bot to have a single centralized tax function! It is very good at satisfying specific scenarios I give, but absolutely terrible at any kind of system-wide planning.
Let's elaborate to: Cap condominiums and detached houses to 0. Apartment complexes is how people should rent.
It is, of course, an extreme scenario. As I said, this is absent good data. If we get a sense of the impact one would have if we limit it to 1, supported by data, sure - cap it to 1.
Some people like to rent single family homes. Some because they have a large family. Some because that's just what they want. It's not ok to tell them they can't do that and must be forced to live in an apartment.
Cassettes were always a pain, but LPs are an awesome medium even today.
While it's convenient to just listen to anything with a click, the joy of the experience is gone. Purposefully pulling out an LP and setting it on the turntable, sitting on the couch to meaningfully listen while reading the album cover is a much more engaging musical experience.
Yes, I don't have time to do that much anymore either. But when possible, it is much more enjoyable.
Just a couple months ago I converted to mp3 some cassettes I recorded in the very early 80s of a local band. Not perfect audio, but sounded quite good still. Not bad for a ~45 year old tape.
Brakes will always overpower the engine unless the braking system is severly damaged. This is simple physics. Cars decelerate far faster than they accelerate, which is to say, the brakes can generate far more horsepower than the engine can.
(Apparently the Rimac Nevera, with about 2000hp, can accelerate faster than it brakes. So that one might be the only exception. So unless you're driving a 2000hp car, the brakes will always overpower the engine, that is not debatable.)
Brake fade is irrelevant here. Brakes fade when overheated beyond their operating range, either due to fluid boiling and/or the pads overheating. This is nearly impossible to achieve in street driving, but can be experienced on the race track. None of the claimed acceleration accidents involved extreme repeated braking prior to the incident.
Apparently when our child reaches driving age we should expect to be paying about $1000/month for insurace. We'll see when the time comes.
reply