I remember telling Theo's brother my review at an NYPHP post-meeting bar gathering. The look on his face was classic. Like he tasted bitter beer.
148 karma · joined November 18, 2008
I remember telling Theo's brother my review at an NYPHP post-meeting bar gathering. The look on his face was classic. Like he tasted bitter beer.
Often times hospitals receive $0 for something they should be getting $10 million per year for, just because nobody ever contests the NOPAY response. Finding that sort of error isn't easy.
This Fallacy was first described to me in Brenda Laurel's Computers as Theatre. http://c2.com/cgi/wiki?BrendaLaurel
For example, I work at a healthcare services start-up, and we have one person full-time researching our competitors and figuring out how to differentiate us in the marketplace, as well as figure out what keywords someone might search for to find this kind of product. We're mainly mathematicians and smart programmers who found a way to break into the market initially, not marketers, so our terminology doesn't match domain experts well.
Anecdotally, I think most users are VERY bad at ranking how valuable information is. For example, we'll get paid $100,000/year for something that takes 1 week and provides zero insight into their business, and then they will refuse to pay us at all for something that makes them $30,000,000 a year! This is so common that I am wondering if its more a symptom of human nature than our customers.
Sorry if it came across that way. I really don't check who reads my blog, there is no comment mechanism, and I do not like linking it anywhere except to friends. Even then, I prefer they not read it directly. My blog is mainly a personal thought dump and collection of links.
Am I the right audience for this book?
If I am not the right audience, can I gain a new perspective by reading this book?
Who is recommending I read this book?
Am I buying this book just because I lack expertise in an area? If so, why am I not asking an expert what book to read and what to look for in a good book? See, for example, Victor A. Wagner Jr's guide to reading C++ books: http://www.rudbek.com/books.html On IRC chat, Victor usually repeats the advice in Peter Norvig's essay Teach Yourself Programming in 10 Years
If I am reading Lambda the Ultimate, and somebody with seniority on that site (e.g. Allan McInnes) says read Franklyn Turbak's book on programming languages, then I generally follow that advice. Smart people tend not to read nor recommend crap.
Most really awesome apps being written these days, that use HTML, are using the CANVAS tag and doing stuff like building terrain maps of buildings and showing people holding 4.5" smart phones where in the building druglords are. Crazy stuff like that.
The model for writing drivers, and plugging in drivers, in ODBC, is R. E. T. A. R. D. E. D.
Edit: I forgot to mention that using the drivers suck, too. The ODBC transaction interface is basically RPC, and is becoming out-moded with recent language research on remote batch execution.
Usually, you have a custom transport protocol for client/server, like the Microsoft SQL Server Tabular Data Stream protocol. It is ultimately not very extensible. Imagine something like LINQ today. Would be nice to just send that expression tree to SQL Server, and not have a client-side or middle-tier ORM tool have to transform the tree into SQL.
Are you referring to HTML and CSS?
RE: You don't have to keep state with a stateless protocol.
You are referring to HTTP.
RE: Now you get a nice (mostly) standardized interface and you get to build a lighting fast native GUI for your app.
What are you referring to?
Stuff like how to process a REST request is simply details. I don't understand why you are focusing so much on this aspect, but I have seen this anti-pattern so often that it repulses me; most examples of RESTful APIs are bullshit, written by people who did not take the time to actually understand REST principles. A good example I documented on my blog is how awful and stupid the ThreeSharp Amazon S3 library is for C#. And writing it in the same style in F# would be just as ugly and stupid! I also discuss why it is a joke that S3 itself is called a REST API, and point out how the language examples in Amazon's documentation is COMPLETELY inconsistent from language to language -- there is no correctness-preservation across language implementations!!!
Incidentally, when people say "web development", they can mean many things, with True REST being just one of them. Most people are actually referring to corporate intranet applications, such as data entry forms and stock analysis tools that chart trends, provide real-time data feeds, etc.
But comparing .NET to anything other than Mono is apples to oranges.
I won't promise performance comparable to Redgate's Reflector, but my rule of thumb is Correct. Clear. Fast. In that order.
Cheers, Z-Bo
I don't know of any definitive text that covers a wide range of practical examples that I've been totally satisfied with, though. Even Safonov waives his hand a little, saying the parser is the one part of the compiler to be written by the most experienced and best compiler engineer on the team, because it influences the performance of everything after.
For more information on this, you should probably look at what Seymour Papert has been doing in Maine lately.
All the build systems he was thinking of are not even worth criticizing, including make.
Check out Vesta, created about 25 years ago...
make is a complete mess. Trying to put lipstick on it and dress it in a champagne gown doesn't change the fact you got stuck with the ugly girl for the prom.
Your ideas on how to make it better seem produced by having your head down typing away at the monitor, rather than seeing the big picture.
Read a visionary system like Vesta. Then re-write this article, and forget about Make.
Who is swalling the snake oil?
Back in the early DirectX days (1996), Microsoft was working on a technology called Chrome Effects that was intended to compete with VRML as the world's ultimate "Networkable Graphics" format. This history is covered in books such as <em>Renegades of the Empire</em>. This was stuff from back when Michael Abrash worked at Microsoft!
For our company, we would have loved to use Google for all our web API needs for addresses, but we can't, due to corporate firewall restrictions and the map display restriction mentioned by a reader's comment on that blog entry. Also, don't mistake this for true address validation, which is expensive.
For good food at reasonable prices, try The Barking Crab.
Larry also owns a beach house in the mansions area of Newport, Rhode Island, aka sailing capital of the world (the main street connecting to the dwarfs is called America's Cup Avenue).
I pointed out that there is nothing innovative about Stylebot. This idea has existed for years under the name SiteMesh. The difference is where in the software pipeline you are putting the SiteMesh/Stylebot logic. SiteMesh is actually more general, in that it is not tied to Chrome.
I don't understand why my comment was moderated out. It was not offensive, just pointing out the fact that there is no innovation here.