We got china for our wedding and at some point we just decided to use it regularly like our other dishes. So far it’s been more durable than our crate and barrel stuff that we also got for our wedding, and we put it in the dishwasher too!
That said we also have some china that’s been in my wife’s family for generations and we’re afraid to put that in the dishwasher. That effectively makes it decorative in our case.
I’m mid 40s, had mainframe on my resume from probably 15 years in financial services (not the exciting, high paying kind either). I moved into tech in my mid 30s and am now in a fairly senior leadership role. But that person that gave me a shot in tech, at a YC company that pretty much everyone here has heard of, was in their 20s! I tell you this to encourage you to do interesting things, whatever you think those are. You wouldn’t want to work with a founder or manager who dismisses you because your keywords don’t overlap theirs. You want to work with the founder or manager who asks questions and wants to understand what you learned and how that experience helps you now.
Mainframes may not be what you’d work on at a startup today, but they’re complicated pieces of engineering, and writing software for them requires you to understand a lot about how they work. Updating or rewriting their software further requires you to understand how the people before you _thought_ they worked. That’s how I tell that story.
Google’s APIs are all kind of challenging to ramp up on. I’m not sure if it’s the API itself or the docs just feeling really fragmented. It’s hard to find what you’re looking for even if you use their own search engine.
The problem I've had is not that the APIs are complicated but that there are so darn many of them.
I agree the API docs are not high on the usability scale. No examples, just reference information with pointers to types, which embed other types, which use abstract descriptions. Figuring out what sort of json payload you need to send, can take...a bunch of effort.
The Google Cloud API library is meant to be pretty dead simple. While there are bugs, there's a good chance if something's not working it's because of overthinking or providing too many args. Alternatively, doing more advanced stuff and straying from the happy path may lead to dragons.
I live in Seattle and I was originally going to go with batteries. However, the half of the year when our power is most likely to go out is also the half of the year where there is very little sun. So for a prolonged outage I’d either need a lot of battery or a generator. For short outages, a battery made sense, but the cost was a lot higher.
I ended up with a 6.5kW portable tri-fuel generator instead. It cost me $1300 and I spent a little more for a plumber to add a gas stub to connect it to. I did my own electrical work which saved some money, but wouldn’t have been much more for an electrician. It can run my whole house indefinitely (obviously with some maintenance - it’s a small engine), except for the A/C which generally isn’t needed most of the year, and with some manual load shedding we can run the hot water too.
I live in the city and shouldn’t need any of this, but Seattle is poorly run so we have lots of outages from trees hitting things. Often a different transformer on the same block because the city will repair them but not take the time to trim the trees near the lines on the same block. I’ve had to throw some food away the last two outages (both in the last 6 months) so this won’t take long to pay for itself!
This is great. I like the idea of it just showing up in your editor, rather than having to go look for it (presuming you spend enough time in an editor, which is likely here). One step removed from a, "leave a note on the keyboard so I know they'll see it!" I was also trying a calendar.txt for a while and ended up overengineering my solution to the problem of wanting to have it available on multiple devices: https://txtcal.app/ (naturally I haven't even added search yet, which was probably the reason I switched to a text calendar in the first place!)
I had posted a Show HN about it last night, so it was really cool to see another approach posted today.
I hash them using werkzeug's builtin utility. "Encrypt passwords" sounded more readable to someone who isn't technical and may not know what hashing is. But you're correct - I should update that. Hashing isn't encryption. Thanks for the feedback.
If you happen to see this, has it resolved? And what browser are you using? I couldn't actually reproduce an issue. I added preload to the header just now though.
I don’t think you should be embarrassed or apologize. You still did a thing that improved performance - in the near term it worked around a bug that you weren’t even aware of, and long term there are still gains even with that bug fixed. But even if that weren’t the case, the only way anything gets done in software is to rely on abstractions. You can either get things done or know exactly how every last bit of your stack is implemented, but probably not both. It’s a very reasonable trade off.
Smart people go and build things. Other smart people find problems. Nothings broken with that.
