Brain Dump
This doesn't interest you! it's me, thinking out loud.
I’m sure you’ve heard the term “law of leaky abstraction”, apparently put forth by Joel Spolsky (if you’re unfamiliar, please go read it – it’s worth your time). Lots of people have blogged about what leaks, what doesn’t leak, why things leak and so on.
To deal with this, people often are in search of creating a “cleaner” abstraction layer that doesn’t leak. And how many times have you seen an internal framework that took way too long to create – time spent refactoring to keep it “clean” by hiding the underlying system ? I think this is a big mistake…
Let’s...
This post will go nowhere, and has no point. In a blatant case of “blogging for myself“, I'm thinking out loud for my own reference.
After a brief email conversation with Kent Tegels a few days ago where he discussed his liking the “push” aspect of SMTP, and the “pull” aspect of RSS, I got to wondering - what really makes these push or pull?
Let's boil down email. One user (say, Alice) sends another user (Bob) an email. She writes it, and sends it to a server. Bob then runs software (email client) to pull that content from the server and...