A non-technical manager can add value by serving as an abstraction layer that encapsulates non-technical stuff (such as budgeting, marketing, and political tackling) and interfaces between technical and non-technical groups. This requires leaving the technical stuff to the right people, which may lead to a technical guru as second-in-command. The biggest challenge to a non-technical manager is long-term planning! After all, how can you see ahead when you cannot fully understand the current picture? The manager of a technical unit must have technical knowledge at least on overview level of enterprise architecture...

Nice neighbor!!! Is P2P allowed too?

It's no fun when the neighbors don't provide free wireless. Where is the goodness in people? If you are using WPA/WPA2, you better off hiding the SSID too, otherwise you are just showing off.

So, no need to watch the news at 11 anymore. Well then, just do some coding...

"and others recently got together in San Francisco". So, others are still behind the throne, like always... Isn't it nice to play puppet master? Ninja in the shadows? Plus, a good developer's name just come out if he (maybe she!?) screwed up big time (definitely she!!).

College: Turbo Pascal -> Java -> C/C++ -> Python , Haskell, FP, LISP, Prolog -> Objective-C -> C# -> ... Work: JavaScript, PHP, SQL -> ... -> SAP ABAP

The rule of thumb is to simply avoid lack or excess of any thing! Maybe an ideal life is based on average...