-
- https://www.hackathon.io for general events.
- GroupMe was actually started at a hackathon.
- I’ve read site reliability engineering before but google just released a new SRE book, Secure and Reliable Systems: https://landing.google.com/sre/books.
- https://netgames.io/games/ for these remote times.
- The actor who played the bipolar brother in ozark did a phenomenal job.
- Few items on db schema design:
- Always separate the address, don’t store in a single column. State, city, zip, street, number.
- First and last name separate. Of course.
- Dates and times stored together in ISO format.
- Store money as cents. Usually lean toward the finest resolution.
- Database normalization, reminder:
- 1NF: Each value is atomic. Can’t have a col with a list of phone numbers for an employee. Create a separate table with phone numbers and FK to/from it.
- 2NF: No PK combinations. Can’t have a table with a primary key of employeeID + buildingID, and then a col for name or a col for location. Each only depends on half the PK. You’re mashing tables together when they should be distinct.
- 3NF. Every col in a table directly depends on the primary key. No attributes just get thrown in the table as metadata. If it’s transitively related, make another table for the transitive part.
- Each form requires the previous. 2NF requires 1NF + the additions. It gets more restrictive as you go up. 3NF is the best.
- Denormalization is faster, but riskier. It’s redundant. Data updates must know all the locations to update. You can break all these rules if you want to optimize for specific common queries.
- Thuringer summer sausage obviously comes fully cooked. Remove casing, slice, eat.
- Adenosine is the chemical that accumulates throughout the day that makes you feel sleepy. During sleep, your body removes it properly. Caffeine binds to your adenosine receptors instead, so you don’t feel sleepy. But once it wears off, that adenosine didn’t go anyway – that’s why you crash. Caffeine just temporarily bypasses a sleepy feeling.
