February 2009
10 posts
The tree stations of a database engineer: Normalization is the key At the beginning you try to normalize as much as possible. Clean Database layouts are cool and nobody really works with this databases. Normalization matters After working on the first small application you realize that its sometimes faster and better if you drop some of the rules. Normalization sucks With lots of experience you start to work on applications like Facebook or Digg. You forget all about normalization and use key value tables like MemcacheDB.
Tonight I shaved 250 lines off of my biggest controller’s code. It’s fun making progress in negative lines of code.
Know this very good. Cleaned my user controller a few days ago. Really like it.
Talked to two girls today, who don’t know Guantanamo Bay. Scared.
To each his own
I totally just schooled Marco in Illustrator. He then proceeded to completely blow my mind with PHP.
Want to get schooled in Illustrator, too. I actually understand the Photoshop paths better.
CSS vs. Tables
Wonder why only people who recently failed designing their page complain about CSS and advise others to use tables. Why not moving forward? I don’t see any problems.
This is how you feel, if you talk to nerds
- me: ha: http://julia.nonsociety.com/post/72444444
- Jacob: 72 44444444444
- me: huh?
- Jacob: the post ID is cooler than the post
