5,859 karma · joined March 2, 2016
Currently @VRO (Vera Rubin Observatory, the only Observatory named after a woman!).
Founder @TimesliceLabs. Former @SpaceX, @Blizzard_Ent, @Microsoft.
Feel free to email me, it's my HN name at Google's email reading service.
Now sometimes you just need things to work, but at least set up a proper on call rotation, shifts, or whatever. But most people honestly don't need this.
I agree that an accretion of kludges is bad. The problem here comes down to usually the skill of the programmer when the new work comes up. To people who don't understand the code, they are more likely to make what they think is a simple kludge than actually refactor to solve the problem "correctly", which usually involves more thought and creativity.
Whereas extra functionality usually increases the code surface area, and once published as a public interface to a library, is very costly and painful to delete. Then it festers as complications to new code that is added have to assume this extra functionality is used rather than not.
Don't try to solve future problems. You'll have the problem that the problem you solved isn't the problem that needs solving, and then the problem that needs solving.
If anything, overly simplistic solutions sometimes make me feel like I'm repeating myself, but really since the code is so easy it always feels possible to refactor it. That's a good place to be, much better than afraid to change something because it's too generic to know if you'll break something.
Everyone has an opinion on an interface that is easy to understand, and not over-engineered (bikeshedding).
Two words: flight heritage.
Successful concepts are very often reused. For example, heat shields, parachute landings, sea landings, air bags for landings on hard land, etc.
Now, let me try to explain this in something similar: cars.
Cars are all pretty much the same. They have a steering wheel, 4 tires, transmission, engine, etc. The parts all do the same thing in different cars, but we don't always use the same engine, or the same tires, or the same frame for every car.
After making cars for so long, why do car companies still have recalls?
New models of cars usually either start from scratch or start based on a different vehicle already in production (new model year). But if you're starting from scratch, you've lost all the "little fixes" that go into making a car good. Like the difference from a new model EV car to a Toyota Corolla that's been in production for basically 10 years has a very different failure/recall rate. After many years of producing the same car, you fix all the little things and get your supply chains working well.
Now back to space ships. It's the same thing. You have made a new capsule and although the concepts are the same, think about all the little things: wiring, plumbing, controls, software. These are all new and basically untested. They lack "flight heritage" (proven working in space).
For the question as why can't we make Apollo ships or Saturn V's anymore, a lot of plans and drawings were lost. Key people making decisions, testing, or even building parts on an assembly line weren't there. Companies making specialized parts folded or went under, or just stopped making those parts.
Sometimes these can be small issues. Like for the Mars Climate Orbiter there was a problem where two different companies thought they were using the same units when they were not. Or when an accelerometer was installed backward on a different ship, making the chute not deploy.
Now compare this to the Soyuz, which is more like a Toyota Corolla of space ships. It's not the fanciest or has the most space or efficiency, but it has a lot of flight heritage and operational history. And from there, you can make small changes relatively safely.
This is true for all companies making space ships. Really it comes down to how well you test things and a good helping of luck on getting it to work the first time, or fixing it quickly.
I worked on Windows Mobile at the time the iPhone came out. We were all shitting ourselves.
“I’m going to do Windows and then I’m going to do Windows Mobile and I’m going to do Windows embedded.” (all on intel x86)
As someone who worked on Windows Mobile and Windows Embedded, it's funny because that's what management was hoping, but it was so different. I don't think any of the phones had an x86 chip in them, although that was our debugging setup so we could use vastly more powerful desktop machines as devkits (although we still had devices to). Having to port parts of Windows to ARM and even MIPS was a giant PITA.
Windows Embedded is closer since it was based on XP, but also a completely different branch from what I remember from Win Mobile.
A lot of people think it's easy to port things, and hard to write things. With really, really complicated software, it's still really hard just to port things.
I'll try to "turn the table" early on in the interview. Ask what they are building, ask questions, say how you might design it (or have designed it in the past). All the fluffy stuff people can lie about, but getting into a good technical discussion can I think prove that both people are on the same level and can work well together.
The other question I like to ask is "why are you hiring for this job?" This can be a real teller. Is it a group expanding due to new responsibilities? Did the last person leave in a huff? Figuring that out can really help explain the org you're about to go into.
My fitbit wifi scale, which I love and has been doing a great job for the last 10 years has now lost support to pair it with the new fitbit app, thanks Google!
A couple of weeks ago my AC blower fan stopped working, the compressor would run. I went up and found out that the capacitor was bad, and took a picture of it, buying a replacement. Took about 15 minutes to replace and I probably saved myself at least $400 (no AC is an emergency in the desert, and they will charge you accordingly).
Fixing household appliances can be fun too!
Why not just listen to the news? You can listen to BBC on Alexa, along with almost any other news radio station you please. If you want short summaries, just look at the AP.
AI summaries might not be correct or might miss out on important context: in the news, the details are everything. And I doubt Amazon will be paying for the news services they scrape.
Are AI summaries of news really that much better than just listening to the news? Does the AI part mean it's going to try and figure out what news stories I listen to? Or will it just be the same for everyone, and then you might just say Alexa give me the news, and you can program it to give you news summaries from a huge list of available sources, which are not AI generated.
This seems like a stupid product idea, akin to subscription mouse. And I actually like and use my Alexa devices quite a bit (nest thermostat, smart water heater, smart lights, timer, weather, use as a speaker for my laptop), so I think I'd be their target market.
I'd say the market should decide, eventually, but this article actually proves the opposite, and it's at every level.
It is what it is I guess. But I also wouldn't want to work for such shallow people either. Note, the person was found on the HN who's hiring, so it's not just random people but also what I'd consider more thoughtful people who should know better as well.