1,136 karma · joined March 25, 2007
jsjenkins168 at google's email
I use 2 6500k lamps as a bias lights (reference white) when coding and also for watching movies. The light will appear a bit "blue" at first (compared to most other lights), but you will get used to it. Color temp is like you are always working outside in the midday sun, its great.
I'll agree that its not about how long you work, but how productive you are while you are working. While there is no substitute for genuine, hard work, I'd advocate that a polyphasic sleep schedule can help some people with long hours of intense work.
The nice thing about everyman is you can make it work at a day job, IF you can take a nap during your lunch break. Its very ideal for moonlighters as you still feel fresh after work and can code late into the night without suffering the consequences the next day.
The biggest benefit of polyphasic is not squeezing every possible minute of awake time. Its the improved concentration and mood. If you want to leave 3-4hrs of core sleep at night thats perfectly fine.
He switched back to monophasic several months later so that he could spend more time with his family during their traditional awake hours. He also simply got bored of being awake when no one else was...
If you are very very serious about reducing total sleep time, you can attempt polyphasic sleep: http://en.wikipedia.org/wiki/Polyphasic_sleep
I recommend trying to find Why We Nap by Dr. Stampi. Its the only detailed research on the subject. Basically, dont trust much of the info about polyphasic sleep around the net as much of it is false.
Austin has all the ingredients to be a great place for startups, with maybe the exception of a good investor climate. VC money seems dried up except for Austin Ventures, and the angels are conservative by SV standards. But regardless, its just about my favorite place.
Please shoot me an email if you'd ever like to chat startups (email in my profile)
A very important article for any aspiring young man.
I only reason I know about it is because it uses similar technology to my site (GWT). Don't know of any schools using it though.
Popular I would say it is not, probably because it is java based and just about everyone hates Java. Once you get over the learning curve and negative Java bias I think most will discover it is worth it though.
GWT 1.5 is stable enough in the trunk, I actually recommend using that even though the RC is not out yet (probably late summer at the earliest I've read). There are instructions on how to build it on the GWT site, its very easy. And then you can use Java 5 syntax which helps out greatly when dealing a lot with RPCs.
Also check out gwt-dnd, its a fantastic library which enables drag and drop. Its leaps and bounds ahead any of the other drag drop libraries, definitely recommend it. Fred is the guy in charge of it and he is a great resource: http://code.google.com/p/gwt-dnd/
I've been using GWT Widget Library for animations. Its just a simple wrapper around Scriptaculous libraries. It has some other functionality too which I have not explored. Animations of existing widgets are super easy though, and can make your UI far more dynamic.
Haven't visited GWT-Ext in a while, but last I checked it was coming along pretty well. As far as drag/drop functionality goes though, you will be able to build more custom implementations with gwt-dnd. GWT-Ext just seemed a bit "vanilla" to me since it looks a lot like a lot of other Ext sites out there. We just preferred something that felt more custom, but I guess thats just a matter of preference.
If you code in Eclipse, I'd recommend checking out GWT Designer plugin from Instantiations. Unfortunately its like $30, but if you end up doing lots of coding it will be well worth it. I use it to mock up layouts initially, and its also great at handling RPC code generation. There is a new free GWT plugin for netbeans 6, but its not quite the level of GWT Designer yet.
GWT is great though because it is so modular. As new libraries come out you can just mix and match to get the widgets you want. Try that in native javascript on a large scale and you can quickly get a headache..
But then I guess that is all part of exploratory programming.