160 karma · joined July 7, 2010
Here's a working version: http://jsbin.com/onevaz/1/
For what it's worth, I agree that the docs need to reflect this.
Product management is particularly important in non-software companies where the obvious product isn't software. Your e-commerce website is just as much a product as your hipster glasses. Failure to manage it results in the classic IT dept. dysfunctional relationship where everyone hates IT and IT develops a thick skin and says no a lot.
Stop creating REST APIs that are only level 1 or 2 (see http://martinfowler.com/articles/richardsonMaturityModel.htm... ).
Start writing HATEOS systems where the client is coupled to the semantic rather than the syntax.
Machine parseable interface descriptions might get rid of some boilerplate but it doesn't make for a more robust client-server relationship.
I was a little surprised at how much slower this was. I ended up creating another test where every case had a function call overhead. All three functional forms (forEach, map and reduce) were slower than the plain old loop
We've been using a HATEOAS approach for the interface between our back-end rails app and our front-end javascript rich client.
We've seen significant benefits during development because the hypermedia links allow us to DRY up the coupling between client and server.
The overall result is much less boiler plate duplication and much clearer client code. It's easier to maintain and extend.
We've judiciously identified some exceptions where the client needs to construct URLs explicitly, in our case because the URLs are tied to dates and we think it's silly to have the server construct links for next_day and previous_day let alone an entire calendar view.
I've bought dozens of audiobooks over the past year or so. Audible is promising that even after I stop "subscribing" that I'll still be able to download and listen to the books I previously bought.
This is as good as it gets with DRM. I freely admit isn't saying much and I do plan to backup my audiobook collection via http://www.opentutorial.com/Convert_audible_aa_files_to_mp3
But that's just qualifying. Racing is about so much more. Driving software will have to integrate considerably more inputs in order to avoid crashing into other cars. Let's say cars have to share telemetry. Development could probably happen in parallel with other improvements but I'd still stay 3-5 years.
Even if we assume software that can drive in a pack of cars, and algorithms for attacking and defending, there's that drive to win that makes some drivers do things that, if we're honest, aren't fair, safe or even right. The rules are different when nobody's life is at stake.
I would love to see Formula 0. No worries about driver safety. No artificial design limits to reduce cornering speed. In fact, the only design rule I would impose is the maximum height above ground and perhaps something about no laser cannons.
Does anyone remember Rogue and then Rog-O-Matic? It would be fun to create an online competition using an existing racing simulator.
This will let us manage those settings under source code control.
See http://stackoverflow.com/questions/4443476/optimal-bcrypt-wo...
Perhaps you're worried about your technical reputation. All you're doing is moving the blame to some part of your code to the decision you made to host on Heroku.
Down is down. Unavailable is unavailable. To your customers that's all that matters.
For what it's worth I think hosting on Heroku makes plenty of sense and I'm actually moving my app (Crisply) to Heroku so that my technical team spends less time writing chef scripts, less time managing database clusters and more time adding value. But when Heroku goes down my customers will be just as screwed.
The article links to the description of the patents http://paidcontent.org/article/419-meet-the-10-patents-yahoo... and tries to summarize each one in "plain English."
> Control for enabling a user to preview display of selected > content based on another user’s authorization level (Filed > 2005, Issued 2009) > In plain English: Share an item only with selected friends
This is actually about a preview of what a given user (friend) would see.
The reason software patents suck so hard is because for every 10,000 totally bogus patents there's one that when you read it makes you think, wow, that really is an invention.
Semicolons are not optional. They are inserted for you as a convenience when the parser can figure out what you meant.
This situation wasn't a big deal in the early days. But the patterns of coding that have emerged to deal with Javascript's scoping problems have brought this from a curiosity to something profoundly crazy.
Using an operator (i.e. !) to fool the parser is hilarious but really not OK.
Writing code is an exercise in communication. You are communicating with other programmers (including your future self) and the parser. The zero semicolon style espoused by @fat is problematic for both other programmers and the parser. Perhaps one day @fat will win and his style of communication will be sufficiently accepted to be valid but this is not that day.
The relevant section of the ECMAScript spec is included for your convenience:
7.9 Automatic Semicolon Insertion Certain ECMAScript statements (empty statement, variable statement, expression statement, do-while statement, continue statement, break statement, return statement, and throw statement) must be terminated with semicolons. Such semicolons may always appear explicitly in the source text. For convenience, however, such semicolons may be omitted from the source text in certain situations. These situations are described by saying that semicolons are automatically inserted into the source code token stream in those situations.
http://www.ecma-international.org/publications/standards/Ecm...
We've always prided ourselves on better quality timesheets. Some of us would keep a journal during the day, others review emails, commits, tickets at the end. No matter what it sucked and was always a bit like fictional archeology. It sounds right but the bones might have been re-arranged a bit and something is always missing.
Commit logs, or task lists are only a small part of the story. Lots of work gets lost in meetings, emails, phone calls and the like. Real work happens across multiple dimensions (no matter where ya go, there y'are) and it's a pain to go find it at the end of the day (or week). The more clients you have the worse this is.
We built http://www.crisply.com to aggregate everything we do into a journal automatically organized by project. We also roll up time when we can. The results are a more accurate (rather than precise) timesheet with rich supporting evidence. You also get great analytics at the time and activity level. Crisply integrates with almost any system. Mention HN if you signup and I'll make sure you get in.
Select some text. Click "Create Pad" and give it a name. The new pad is created with the selected text and the name links to it. This was a little disconcerting at first but it's absolutely the right thing.
I got the @User stuff to work. I think it matches contacts from my google contacts against other users who have signed up for HackPad. That's reasonable.
A long time ago in a startup far far away a friend and I built something like this. Ours was nowhere near as elegant. We would look for CamelCaseWords to kick off the autocomplete but your use of @ is much better.
Delightful moments: pasting an image url embeds the image. Consider letting me backspace the image to get back to the url.
The multi-user edit seemed very smooth. Better than collabedit to this user.
The task list is nice. I'd love to have a title to the task list and be able to query for and surface all task lists across pages.
Please consider supporting #hashtags if only so you can show a tag cloud. The built-in search is great.
I couldn't figure out how to link to a person.
Finally, for users who login with their own email address, please consider letting them in right away. At most have the confirmation step be something they can complete later. Eliminate friction at every turn.
All in all a really nice product.
This wikipedia article is certainly relevant http://en.wikipedia.org/wiki/Critical_engine but I'm still not sure how the Boomerang can be so stable that it requires no rudder input during takeoff.
My guess is that by having one engine further back he creates the equivalent of the dihedral effect. If the plane starts to yaw in one direction. I have nothing but intuition to support this idea :)
I would love to see a detailed explanation of how this plane is so stable.
Pastebin or mailinator.com I guess :)
I can see it now, datafrontporch.com, an escrow service for data. Sign up now for protection when, not if, your account is cancelled.
The cost of storing that data for 60 days after the account is terminated would be minor.
In general I don't care about this guy. More interesting is the issue of "my data" and "your service." I see this as equivalent to a landlord and a tenant (no matter how little rent paid). The landlord can, under certain circumstances, kick the tenant out. The landlord cannot under, any circumstances, hold or destroy the tenant's possessions.
Longer post here https://plus.google.com/115878613002809583306/posts/WsWj4CEh...
Clickable PDFs, simple text markup for control data, story boarding and eclipse integration. No real time collaboration but that hasn't been an issue for me.
The free version nags you a bit but the price was so low I just paid for it.
I cut my teeth doing Z80 ASM hacking on a Timex Sinclair and had no patience for this required class.
I wrote all my assignments in C and dumped the intermediate output. The grader always gave me nice comments like "well structured code."