I was a REST purist for a while and the purer I got the more unhappy I was. Hypermedia standards like Siren and HAL just made things miserable no matter how hard I tried to make them work.
I think the REST Architectural Pattern is great but I don't use it anymore. Instead I create ROUSED services.
Resource Oriented because the very best thing about REST is the tendency to focus on resources and collections of resources and how you can interact with them sensibly.
Unconstrained because I don't let some specification control how I work.
Sensible because things still need to be internaly consistent and well thought out.
Enterprise because the fact is I'm always making these services for some 'boring' business use case.
Services that provide some specific set of bounded capabilities within the usual messy ecosystem present at a SaaS software company.
I think we owe a lot to Roy Fielding for the potent ideas but as others have argued eloquently, reality sets in and you have to adapt to circumstances.
This is basically a fluff piece about Lego with a side helping of climate and sustainability topics. It’s not a particularly good article in my opinion.
I think the most fundamental question facing Lego is that clone brick makers are now able to deliver excellent sets at significantly lower cost. The article doesn’t mention that at all.
Agreed. Plus I expected photos of some sort of in-house reference product archive given the title, and instead there was none of that. It's at the level of blogspam.
Is it? All the clones have been garbage to whoever used to use lego extensively.
Some bricks have incompatible vertical/horizontal measurements, many bricks don't stick in places, others are too small to be able to easily fit with hands.
My dental practice has only one significant improvement that I’ve noticed in the last 30 years, which is to use a sonic scaler to remove plaque instead of manual scraping with an implement. Somebody in the field would certainly be able to provide a better and more informative answer.
I find it curious that the Lockheed Vega is chosen as “Amelia Earhart’s plane” since most people would probably associate her with the Lockheed Electra, the plane she was flying when she disappeared.
It’s analogous to saying that Ernest Shackleton’s ship was the Nimrod…not wrong, just odd.
I am also bad at mini Metro but the thing that makes me crazy is that when the game ends it says something like “your city shut down.” That makes absolutely no sense and the endgame message should’ve been “you were fired!” Such a missed opportunity!
Serves this city right for putting all its eggs into one basket.
Where are the alternate forms transport: the bike paths and bike shares, LRTs/buses, and yes, roads? What about other upstream policy levers such as WFH mandates, and a decentralized urban core?
My condolences on your loss. I used QModem in the early 90s downloading shareware and the like. I just looked through my floppy disk holder and found a 3 1/2 inch floppy from 1992 with QModem on it :)
Your dad’s contribution to the BBS scene was huge and it was an important part of my own journey into computing.
Add me to the list of early 90s QModem users! Just looked it up now and was reminded of the various download protocols like ZModem and Kermit. I haven't thought of those for years! When I used them, I don't think I even knew what a protocol was!
Meta discussion:
The article is brilliant (my fridge hassles me too!) but makes two small word usage “errors” by using the phrase “dawn it’s Freon cap”
The first “error” (I’m mostly a descriptivist) is incredibly common: using “it’s” when “its” is “correct”.
The second “error” is much less common: using “dawn” when “don” is “correct”.
Is this just a case of autocorrect being “helpful”? :D
I seem to recall that some drawbridges could be counter weighted and have supports that could be removed quickly that would then free the counterweight and close the bridge immediately.
I think the REST Architectural Pattern is great but I don't use it anymore. Instead I create ROUSED services.
Resource Oriented because the very best thing about REST is the tendency to focus on resources and collections of resources and how you can interact with them sensibly.Unconstrained because I don't let some specification control how I work.
Sensible because things still need to be internaly consistent and well thought out.
Enterprise because the fact is I'm always making these services for some 'boring' business use case.
Services that provide some specific set of bounded capabilities within the usual messy ecosystem present at a SaaS software company.
I think we owe a lot to Roy Fielding for the potent ideas but as others have argued eloquently, reality sets in and you have to adapt to circumstances.
reply