48,108 karma · joined December 14, 2014
As a UIUC student used to be fond of reminding me, part of the University of Illinois’ contribution to the old Internet was in a building that, if it were to collapse, would fall outward and not crush the basement. Officially that building was designed so every office has natural light, like a collapsible water cup, but it’s a very interesting coincidence that it (the basement) is bomb proof.
SpaceX being their own customer, and a lower priority one, lets them levellize their revenue, which also helps retain staff. And if anyone commoditizes launch systems, they have a hedge against that. However if demand for starlink ever does exceed capacity, the launch side could find their schedules being much more variable.
In software, you see this with priority queues all the time if you know where to look. Someone makes a “low priority” system that soaks up spare capacity. Internal customers become dependent on these systems and then become delay-averse. Meanwhile, other teams also start soaking up that spare capacity, by improved design or feature creep or both. That low priority system becomes starved of resources, and the internal customers start saber rattling. That system gets its own dedicated resources, and now stranded resources climb back to the original levels, if not worse.
Starlink will eventually become the same thing. And I wonder if they will spin it off when that situation arises.
To be fair to NASA and the astronauts, NASA needed humans who behave like military test pilots. In physiology, in reaction time, in crisis management, in following chain of command. And the armed forces were willing to give them access to known quantities.
We didn’t know how control systems would evolve over the next three decades, but the pilots wanted to pilot, and did not trust the control systems. And the irony of it all is that the Space Race was a proxy war for nuclear armament, so control systems needed to be made autonomous anyway.
Better control systems, wider telemetry, and not worrying about incinerating employees let current generation rocketry iterate faster, and do more fucking around and finding out. We found out twice with the shuttle and it killed the program.
It’s curious how much the upper stage now resembles a space shuttle on a ballistic trajectory instead of a glide angle. Very different landing strategies for those two modes of descent…
Seems that the heavier the rocket the more ground clearance to need to self-land, and so you can’t scale up the dragon’s landing system. I don’t think there’s anywhere near enough weight to shave off of the next rocket or enough specific impulse to add to bring the size back down.
Example, got a feature with a new required field? Add empty field, synthesize a default value for existing rows, start accepting data, validate that data, require the data, use the data.
If you’re doing deployments once a week, you end up juggling two stories so you’re not sitting on your hands the whole time, and two stories divided your attention, so the odds of fucking it up go up anyway even though you’re being careful on paper.
Meanwhile one of your coworkers is doing the same dance on another feature, so you start tripping over each other as team size increases.
The whole point of WLB is that we don’t live like monks.
I’ve worked with several people who either confessed to or were accused of having taken up pastimes that would guarantee they weren’t available during times they shouldn’t be expected to be available.
Management gets rewarded for getting more work out of us and there’s always someone pushing boundaries trying to leach a little more work out of the staff they have. These same people seem to think burnout is a big mystery, because to admit they caused the problem would be to admit they did something wrong.
I don’t think most people fully appreciated how much work a handful of us did to make sign off faster and deployment less error prone.
For the FAA it sure as fuck doesn’t.
Software is effectively contract law, and if one were solvable the other would be too. The fact that we have so many lawyers, and loopholes are a constant issue is the same reason we have so many programmers and so many bugs.
We cannot nail down what is and isn’t acceptable input, acceptable output, and acceptable intermediate states all at the same time. And that’s what you need for correct software.
If you’ve ever don’t consulting work, you know how dangerous it is when the majority of your revenue comes from a single customer. You stop being independent, you stop having your own set of values, and if anything happens to that company, you’ve already proven you lack the ability to court as large a contract from other customers.
It always ends in a loss of identity and huge layoffs.
Making vendors product triple their current production rate for the next five years isn’t even possible to start this year, because they have to build facilities and train employees. Nobody runs businesses at 50% capacity anymore. That’s considered wasteful, even stealing profits from your shareholders.
They can’t even get memory chip companies on board with their koolaid.
Someone hit on the notion that it’s Stockholm Syndrome. You bond with people you go through shit with. You don’t bond with people who prevent the shit. That was a super awkward conversation. The asshole in charge quit shortly after it, but 2 years later we still occasionally called each other out for making plans that accounted for a toxic chain of command that was no longer toxic.
It took us 200 years to break it, we'll probably be 300 years fixing it, at which point the ocean will have likely absorbed all it can and started giving it back to us.
Particularly because all the CO2 we dump into the ocean will return to the surface in ocean upwellings once the currents have run a full cycle.
Be the change.
That’s not how sacrifice works.
If you want to stop rewarding bad actors you often have to give up something in return. Such as Amazon Prime. Or McDonald’s French fries.