The majority of work I do, as a programmer who wears a shirt and tie, involves databases. And I try to keep things nice and simple when working with databases. What I mean by simple is, extra tables in a database is fine, even triple the “minimum number” (whatever that is), if they all mostly follow some pattern. Constructing a database schema is then a simple application of the rules devised when designing the pattern, and means there’s not much to think about or have go wrong.
Things I learned today: Applied Queuing Theory. The outside queue to WWDC at about 5:30 AM Queues in Practice and Principle. Another shot of the queue Queues and You: A lesson in hidden opportunities. The queue inside Starbucks Queue Participation for Fun and Profit Internal queue friends Time and Distance: A queue-theoretic case study Are we there yet? Escalating Queues to the Next Level Skilled "escalatio" practitioners on the way up Go go go!