Happened twice to me now: weak product team and product definition. Engineering optimistically forges ahead and ultimately gets flogged for not delivering results. Long work hours, micromanaging, and unpleasant work culture.
First time experiencing it was a learning lesson early in my career. Second time I recognized red flags but had other reasons to keep the job. Ended up just as painful as I expected.
2 best years of my 20s were spent getting away from computers altogether. I quit programming in that time and got back in with help from some old coworkers offering me a job. This was after I had a) finished my degree, b) travelled south america, and c) rode around the US on a motorcycle. Get away from computers is my advice.
All very good points. I had worked some years ago on a prediction market site which attempted to merge 3 mechanisms for gaining collective intelligence: Polling, paramutual betting, and full buy/sell market. It was motived by the fact that full blown market simulations are a steep learning curve for the non-investor, but that person has a valuable opinion nonetheless. Never did much with it.
In this chain of forbidden places is also Gardiner's Island in New York at the end of Long Island. Apparently gifted to the Gardiner family by the Queen before the US existed. Signs surround it warning the public that they're not welcome. I guess it's not forbidden so much as privately owned.
I can't help but have a little CueCat-ish response to Glass. I don't wear glasses and don't care to. So Glass saves me from having to take my smart device out of my pocket by having something on my face all day?
NB: I've seen plenty of these around but haven't actually played with one.
Musician, Spotify user, and Radiohead fan here. Spotify fulfills my dream of working in a record store so I can spend all day discovering music. This argument is behind the scenes paperwork between the service and the content owners. They should figure it out without bothering me the end user. If they can't, then they're both at fault.
Even better than git for publishing, I like the "fork" concept as applied to the more general web. Forget copyright issues for a moment... if you could fork sites here it would allow for really fast site creation where you can build off others' creations.
Ward Cunningham's Smallest Federated Wiki[1] is basically what you describe. To edit a wiki page you have to fork it into your own wiki, which I think automatically creates links and things. It's interesting but I haven't explored it nearly as much as I'm sure it deserves.
Just one data point. I'm 35. I did startups in my early 20's, took 2 years off to travel and finish school. Opportunities were still there once I was done. You could say that no work history is the same whether it was due to traveling or because you're only 19.
That is definitely another way to do it. You do lose the significance of the HTTP verb, though. One reason i've come to the dedign i proposed is that a web form usually isn't creating and deleting in a single operation, so I used that to justify different entry points.
