In any case, both platforms are here to stay for quite some time.
504 karma · joined January 22, 2008
In any case, both platforms are here to stay for quite some time.
You mention "trust", "steal", "juiciest parts (of ideas)". You seem to imply that ideas (without execution) have a huge value and so must be protected somehow like a treasure. I think this is the fear that a hacker might listen, secretly record the conversation and swiftly run home to implement your idea before you. This is unlikely to happen. Chances are that if your idea is so good to get a hacker inspired to do something about it, a truly brilliant hacker might actually ask you if he can join you instead of going on his own. If he decides to "steal" it, chances are that he is not such a great hacker after all.
But anyway. An idea without execution is close to nothing. I don't think you have anything to fear to talk about it with anyone: non-tech people might help you to think outside-the-box and provide a different perspective; your peers might become interested, give implementation advice, or even join you. And you might as well talk about your idea at least to understand it's not shit.
If you keep your idea to yourself, it's just you and your brilliant, closed, lonely idea. :)
I find the East Bay much more livable, in particular the nice parts of Oakland and Berkeley. Streets seem to be designed for pedestrians (or bicyclists) instead of cars. Plus the weather rarely gets in the 90s, which is invaluable for me.
Is twitter search that important? I think the value of twitter is in the instant, not in the history.
- The UI design is visually distracting, bulky, complicated. There's too much going on at the top, 3 differently colored bars with the powerset logo, tab(s) and huge search bar. The search bar is omnipresent, even in the individual Wikipedia page you chose. Ironically, Google has a similar structure in its result pages, but feels completely different because the background is all white and less invasive.
- The Factz are often distracting and presenting useless stuff. E.g.: http://www.powerset.com/explore/semhtml/Simple_DirectMedia_L... presents around 25 factz. I counted 3 or 4 factz that are actually useful. The meaning of the other factz in the context is either obscure ("parameters": which ones?), deceiving or incomplete ("functionality", "ports", "operations", etc), useless ("needs" (??), "SDL", "The Video"), or all of the above.
- The way you actually use the Factz is terrible. First you clik on one fact, then after being flashed with the fade-out bling on the right column you actually have to move the mouse pointer all the way there, then the animation scroll, then probably move the pointer to the left to click on something actually useful or go back up to select another fact because the one you chose was wrong anyway (why? see above). After 5 minutes of this I feel dizzy. Who designed this stuff?
- massive waste of screen real estate with large white space on the right column, either entirely (results page) or partially (actual wikipedia result page you selected).
I do think there are some cool things, but so far it seems hard to use IMO.
For STL, I recommend Josuttis's "The C++ Standard Library". It's a STL reference book, very complete and easy to browse. There are also brief examples on own to use the classes and templates. http://www.josuttis.com/libbook/
Often these mysterious company policies are not explained in the first place, yet I'm supposed to adhere to them. So I find myself pondering, "Is it ok to do this?" Engineering-wise (and by common sense) it would be a no-brainer. Then I waste time and energy asking approval. Sometimes I get denied and so I wasted my whole train of thoughts related to an otherwise obvious choice. What bothers me the most is that the majority of people seem numb to these problems.
Why did you hire me if basically you're questioning my trust, and why are you blocking me from doing what I'm supposed to do? Then why you invite me to "fun" events afterwards?
2. RMS reflections about morals in software programming (I may not wholly agree, but he taught me a whole new way of thinking about software)
3. Prolog declarative approach (instead of describing how to solve a problem, just describe the problem)