ENTRIES TAGGED "rest"
REST Interfaces, Browser History, Crappy Textbooks, and Wireless Babies
- Designing RESTful Interfaces (Slideshare) — extremely good presentation on how to build HTTP APIs.
- Manipulating History for Fun and Profit — if you want to make websites that are AJAX-responsive but without breaking the back button or preventing links, read this.
- Why Textbooks Are So Broken (Salon) — Let’s say a publisher hires a developer for a certain low-bid fee to produce seven supplemental math books for grades 3-8. The product specs call for each student book and teacher guide to have page counts of roughly 100 pages and 80 pages, respectively. The publisher wants these seven books ready for press in five weeks—over 1,400 pages. To put this in perspective, in the not too recent past at least six months would be allotted for a project of this size. But publishers customarily shrink their deadlines to get a jump on the competition, especially in today’s math market. Unreasonable turnaround times are part of the new normal, something that almost guarantees a lack of quality right out of the gate.
- exmobaby — wireless biosensor baby pyjamas send ECG, skin temperature, and movement data via Zigbee. (via Jo Komisarczuk)
Implementing REST, Teaching Exploration, reMAKEing the Enterprise, and Printing Titanium
- Implementing REST — This is a place for exploring aspects of implementing applications using the REST architectural style. This may include statements about existing frameworks and libraries, general discussions about the nature of the style and how it may be expressed and/or encouraged via a programming framework, etc.
- When Teaching Restrains Discovery — read about this research (short story: the more specific the skills taught, the less exploratory students were) and think about how we teach people to program, how we teach them the company culture, how we teach them to succeed.
- The Maker Generation in the Enterprise (JP Rangaswami) — We have to get away from the idea that knowledge work is smooth and stable and uniform and assembly-line in structure and characteristic. Knowledge work is lumpy. Period. There will be peaks. And there will be troughs. The current thinking appears to go something like this: “If we have troughs it will look like we don’t have enough work to do, so we need to pretend to work. Let’s fill our days up in advance with things that don’t depend on market or customer stimulus, things we can plan well in advance. And let’s call these things meetings. Then we can look busy all the time.” Such thinking has produced some unworthwhile consequences.
- i.materialise 3D Printing in Titanium — Titanium’s high heat resistance, high accuracy and unparalleled strength lets designers now make things that before now could only be made by the research and development departments of only the largest corporations in the world. By putting this technology in the public’s hands were democratizing manufacturing and giving you the opportunity to, design and order something this is exactly as you want it to be. (via Chris Anderson on Twitter)
Web of Data, Wrong Open Source, Cloud Spot Market, REST
- Predictable Web of Data — a chapter of a book that never happened, this chapter covering the wonderful YQL.
- Symbian: A Lesson on the Wrong Way to Use Open Source (GigaOm) — Open source can be used to inspire and complement successful products. It can accelerate momentum. What it can’t do is resurrect dying technology products.
- SpotCloud — a spot market for cloud capacity. (via John Clegg on Twitter)
- Richardson Maturity Model for REST — A model (developed by Leonard Richardson) that breaks down the principal elements of a REST approach into three steps. These introduce resources, http verbs, and hypermedia controls. A very good introduction to REST for those who haven’t thought hard about it yet.
REST Data, Copyright Hell, iPhone Web Apps, HTML5 Quake
- OData — REST protocol for accessing datasets, based on Atom, JSON, and some XML formats for metadata.
- Thinking about Monkeys and Engineers and Copyright — short read, but makes you realise how tortuous the current remix possibilities make copyright law.
- How to Make an HTML5 iPhone App — walks and talks like an iPhone app, but is made entirely of HTML. (via Hacker News)
- Quake 2 for HTML5 — In the port, we use WebGL, the Canvas API, HTML 5 <audio> elements, the local storage API, and WebSockets to demonstrate the possibilities of pure web applications in modern browsers such as Safari and Chrome. (via waxy)