m25n

I was an engineer on Tracker from 2013 to 2020. I’m sad to see it go.

Yeah, you definitely shouldn’t buy Bitcoin because it’s going to crash: https://youtu.be/XbZ8zDpX2Mg?si=PyP8bPAOUftVyAcS

This is likely going to be for certain large institutional funds where there are many restrictions on what can be bought. Buying an ETF is often the easiest path for them. Also, retail folks that like the idea of the SEC signing off on it (I think this is a silly reason but I can empathize with why that might be comforting for some).

Sounds very similar to time preference: https://en.wikipedia.org/wiki/Time_preference

Since HN is an entrepreneurial group, this feels like a business opportunity. Probably not a Y-combinator unicorn darling, mind you. Figure out how to help libraries help their patrons get secure reliable access to email and other internet services.

I’m definitely gonna try this out. Thanks for bringing it up!

I’ve reached an interesting point in my career. I started out truly in love with “sitting around and dreaming up new architectural diagrams that can comfortably sit inside [my head].” However, I don’t derive any pleasure from that anymore. Possibly because I’ve had to face the hard reality of what happens when the architecture “outgrow[s] the size of any one person’s head.” I’ve come to be very interested in two things: figuring out how to delay that as long as possible and what to do when you can’t delay anymore. The first seems to be bringing in as little software (in any form) as possible. Dig and dig to find the actual problem and then solve that using as few tools and abstractions that the team can possibly tolerate. The second seems to be about process and Conway’s law. Figure out communication structures to distribute the management of complexity.

I have found that as I gain experience with rust, I spend less and less time “upfront to compile and fix all warnings”. I think rust requires a different design philosophy. It just takes time to adopt it into your mind.