12,400 karma · joined July 22, 2012
I tracked it down to a folder with thousands of C++ files called things like uint_to_int.cc and inch_to_cm.cc and cm_to_m.cc. Basically the developer in charge of writing the conversion library took our typed units library and autogenerated a C++ file for every possible conversion the application might need to make.
Every time we added a new typed unit it would create another couple of dozen files to be compiled.
I think this is my entire problem with most of these conversations. When they say "The walled garden has to end." ... they mean "YOUR walled garden has to end.".
I also like the Walled Garden. Do I think Apple should be able to charge more than Stripe? No.
I wish they would stop conflating the gate keeping price to enter the walled garden being too high with the wall garden and the gate being a moral wrong.
We did start small with all of those things. We developed rigorous disciplines around engineering, architecture, material sciences. And people died along the way in the thousands[0][1]
People are still dying from those failures; The Boeing 737 MAX 9 crash was only two years ago.
> Incremental makes less sense to me when you want to go to mars.
This is yet another reason why a manned Mars mission will be exceedingly dangerous NOT a strike against incremental development and deployment.
[0] https://en.wikipedia.org/wiki/List_of_building_and_structure...
[1] https://en.wikipedia.org/wiki/List_of_accidents_and_incident...
A lot of the discussion here is that the cost of the in-house team is less than people think.
For instance: at a former gig, we used a service in the EU that handled weekends, holidays and night time issues and escalated to our team as needed. It was pretty cheap, approximately $10K monthly fee for availability and hourly rate when there were any issues to be resolved. There were a few mornings I had an email with a post-mortem report and an invoice for a hundred euros or so. We came pretty close to 5 9's uptime but we didn't have to worry about SLA's or anything.
What AI does is replace most of the junior engineers, some of the intermediate engineers and speed up your senior engineers. That's why you are seeing massive layoffs across the industry.
I see that as the difference and when it becomes complaining and toxic.
Often there isn't actually a fire, they're complaining about trivialities. Everybody already knows about the fire because they've complaining about at every meeting for three months. Or the thing they are complaining about can't be changed. They're actually getting sidelined because they interrupt company allhands to ask the CEO irrelevant questions, wasting the time of 50 people and no one likes them anymore.
I view dealing with chronic complainers as mentoring them to stop self-sabotaging themselves.
Also, we are up in arms about the introduction of government tracking is 1) it's not JUST government tracking, the age restricted sites will also get your PII and 2) most people get concerned when governments start getting involved in things regarded as private, like sex, porn, etc. 3) What will require verification is unclear "age restricted content" is pretty open.
How do you not follow the argument that there are problems with this?
(1) https://www.pewresearch.org/short-reads/2024/02/28/who-likes...
Invoking the "slippery slope" fallacy when the country with the greatest military in the world is abusing public records to grab people off the street and out of court rooms is an interesting choice.
In this case you are criticizing an analogy meant to convey understanding of "weakest link" for not also imparting an understanding of "levels of severity".
This is my experience: at some point the AI isn't converging to a final solution and it's time to finish the rest by hand.