Technology

Redoing work is now extremely cheap. Code in the small is less important than structural patterns and organisation of the code in the large. You can also build lots of prototypes to test an idea out. For this, vibe-coding is great, as long as the prototype is thrown away and rewritten properly later.

This is fitting my better understanding of the shift in software development from vibe coding (hello Ruby on Rails would like a word) and using prompts to build design docs to THEN build software.

I think it’s actually the other way around. A truly great engineering organization is one where perfectly normal, workaday software engineers, with decent software engineering skills and an ordinary amount of expertise, can consistently move fast, ship code, respond to users, understand the systems they’ve built, and move the business forward a little bit more, day by day, week by week.

Agree completely. And besides have you ever tried to manage that many egos on one team? Too many chefs and not enough cooks is a problem too. The best restraunts in the world cannot function without the dish washer.

The IIHS came up with an easier way to repeatably measure and compare what a driver can see in a 180-degree forward-facing view out of a vehicle. The method involves a special portable camera rig that captures a driver’s view. That image is then processed to determine what percentage of the road in a specified radius is visible, and what’s blocked by the vehicle’s A-pillars, hood, and side-view mirrors. The result is an aerial view of where the driver’s vision is obstructed—the blind zone—as well as a percentage of the surrounding area that’s visible.