 |
|
|
|
|
 |
|
|
|
|
The Magpie Developer
Jeff Atwood is one of the best programmer/writers around. I love reading his stuff, some I agree wholeheartedly with, other stuff we disagree, but this post is about a dead-on as they come. This idea has been floating in my head for a long time, but it is hard for me to conceptualize it in words, Atwood does a brilliant job at it. Must read for any developer. |
|
|
|
Andy Olmsted's Last Blog Entry.
(Warning: Pretty rough) No matter how you feel politically about the war, this reminds you that each number people throw around as statistics is a human life. This is extremely well written, and pretty rough on your soul towards the end, but something everyone should read. Its a shitty situation all around, but there is always a human face behind the statistics and I want to make sure I never forget that. |
|
|
|
|
|
|
|
|
|
Drinking stories that put yours to shame
Via Keith
To preserve his body during the voyage home, the second-in-command stored Nelson's body in the ship's vat of rum and halted all liquor rations to the crew. Not a bad idea, but when the ship reached port, officials went to retrieve Nelson's body and found the vat dry.
Disregarding good taste (in every sense), the crew had been secretly drinking from it the entire way home. After that, naval rum was referred to as Nelson's Blood. |
|
|
|
making vodka pills in 24 hours
Recently, Chef Fabian was experimenting further with the Adria/Torreblanca technique of making 'vodka pills.' I use this word to describe the process of making liquid-filled candies by pouring flavored alcohol syrups into cornstarch and letting it set until a hard outer shell forms. |
|
|
|
Strategy Letter VI - joelonsoftware.com
As a programmer, thanks to plummeting memory prices, and CPU speeds doubling every year, you had a choice. You could spend six months rewriting your inner loops in Assembler, or take six months off to play drums in a rock and roll band, and in either case, your program would run faster. Assembler programmers don’t have groupies.
Entire Article is Dead On. A must read for anyone in the software biz. |
|
|
|
 |
| |
| |
| |
| |
 |
|
 |
 |
|
(Monday, November 21)
The Next RSS
The Next RSS.
I have been using RSS for about 2 years now. It honeslty has made my day much more productive and also the passing of objects *unsecure* in my apps a little less tedious than throwing business objects and proxies around. It was so light weight that it is a breeze to implement in different apps as both provider and subscribers.
To my delight MS came out with a pretty sweet spec today about what I belive is the future of RSS or atleast a good direction. It is called SSE (wasn't there a processor instructure set with this handle before?). Simple Sharing Extensions for RSS and OPML. It is basically and addition add on to the extremely simple RSS form factor that will give basic queue redundancy via the Publisher/Subscriber model.
1 Overview
The objective of Simple Sharing Extensions (SSE) is to define the minimum extensions necessary to enable loosely-cooperating apps
1. to use RSS as the basis for item sharing � that is, the bi-directional, asynchronous replication of new and changed items amongst two or more cross-subscribed feeds.
2. to use OPML as the basis for outline sharing � that is, the bi-directional, asynchronous replication of outlines, such as RSS aggregators subscription lists
The first thing I thought of was with a Pub/Sub model who gets to be the winner in conflict (ie who has override powers the Pub or the Sub?) Well I have not really studied it in depth, but it looks like the Pub always wins (which makes sense) but the neat thing is that the Sub keeps a history on conflict resolution, which is a neat method for what I call "keeping up with the Joneses" when somthing has changed in the past few RSS items previous in a feed and must be updated and accounted for (if you have an rss reader, you may see this problem when people go back in and change a misspelling (I do a lot) on their feed title and it alters the feed entry title, and without a GUID or ID the reader has to only belive that the entry was updated and marks it as unread. Where as you sit there thinking it is a new article, when only it was a corrected mistake.
The REALLY interesting thing about this is that it comes out with a semi-familiar licence:
Microsoft's copyrights in this specification are licensed under the Creative Commons Attribution-ShareAlike License (version 2.5). To view a copy of this license, please visit http://creativecommons.org/licenses/by-sa/2.5/.
I think it is great that they did it like this, but also you gotta think MS was long to embrace RSS (its just really comming with Vista/Longhorn) and to be fair, Google had the "ATOM" which both tried to capitalize on a proprietary format. It is good to see strides from MS that are keeping things open for everyone.
Simple Sharing Extensions for RSS and OPML
|
|
 |
|
 |
 |
| |
Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.
© Copyright 2003-2007, Eric Thompson |
|
| |
 |
|
|
|
