51stpage

I have spent many happy hours listening to Aaron talk about his experiences serving on submarines on YouTube and Twitch. He used to go by JiveTurkey then rebranded to SubBrief.

Watching him play Cold Waters is a delight.

There is also Marginalia https://search.marginalia.nu/ which I don't see on your list.

This is so deliciously recursive. A post to HN about a tool that lets you query HN with SQL. Nice!

This is a tool that I found recently. In the 0.2.0 release, there's support for multi-region queries which I've been really excited about. Now I can do a single query without having to doing merges in post-processing.

SQL joins across different APIs has been really handy too. I can do comparisons of my AWS, Azure and GCP compute resources in a single query.

I too don't need any of the features that cryptocurrency brings. However, cryptocurrencies are making substantial headway on solving the hardest class of problems that humans face: coordination problems. Common examples include the Tragedy of the Commons and collusion [1].

Vitalik has written some surprisingly approachable pieces on the various problems that cryptocurrencies face. It's not too much of a leap to see how these problems appear in non-cryptocurrency contexts. The value I see in cryptocurrencies is that they must develop robust/antifragile solutions to the coordination problems that have plagued society forever. Even if some problems can't be solved, then there are mental tools for making sense of what's going on.

[1]: https://vitalik.ca/general/2019/04/03/collusion.html [2]: https://vitalik.ca/general/2020/08/20/trust.html

All I can see is uneducated investors taking highly leveraged positions and feeling the inevitable pain when they didn't cover the possible downside.

A lesson to us all, absolutely. Know damn well what you're doing (and prepare accordingly) before you start trading with someone else's money.

Your assertion about generalist ~= founder is pretty spot on. I've spent decades working lots of different job titles that interest me (or as the needs of the organization dictated). Putting all that down on my resume hasn't helped me much.

I was heading the direction of very focused resumes. I've also landed a low pressure founder role too, so that's nice.

Mike Monteiro has an excellent talk[1] on contract negotiation and where to get lawyers involved. The pertinent point for me was the following:

Contract negotiation makes them fair. If you just sign whatever people put in front of you, you give up your rights to have a fair contract.

Also: The contract given to you probably represents the opposing lawyers wish list of all the things they wish they could have. Most/some of these things will be extremely disadvantageous to you. Just signing anything they give you means you submit to their wish list, not your own.

[1] https://www.youtube.com/watch?v=jVkLVRt6c1U

SQL injection attacks are an excellent example where code and data are mixed. One solution is to do a lot of clever escaping of 'attackable' characters that instruct the DBMS to stop treating a character string as data and start executing things [1]. Escaping attackable characters attempts to partition data from code. This usually works but not perfectly.

Or, run your data through stored procedures instead. It took me a while to figure out why stored procedures were so much more secure than regular queries. I finally figured out it was because a stored procedure does exactly what the grandparent post says: It treats all inputs as data with no possibility to run as code.

[1] https://xkcd.com/327/

I'd try https://mbasic.facebook.com

It's mobile centric, browser based and gives you access to Messenger. Also, doesnt require the "hack" of requesting the desktop site (which may or may not work.) The trade-off is that lots of automatic Javascripty things don't work the same way.

It's worked well for me.

What about the opposite? What if every team department had a pool of tokens representing their services that they had to give away in a certain time period. I suppose tokens are the same thing as money but I like the shift from "Gimme, Gimme" to "Hey, I've got plenty, let me give you some." Each department would also be accountable for how many tokens they collected from other teams.

I'm not sure how you would work out how many tokens a department has to give. My hope is that there would be a way to incentivize going outside your team/department to get help.

I really appreciate your insight that different political structures work better for different scales and different situations. I suppose that's intuitively obvious but I hadn't ever considered it.