1. Double-count your startup as coursework. Enroll only in project-based classes. Spin off each module in your startup as a project -- e.g. Distributed Systems? Write the EC2 part. Databases? Write the Lucene part.
2. Many EE/CS departments offer bschool classes at the 400/500/700 levels. Use these to get startup advice / stay motivated.
3. Take research credits, have entrepreneurship-friendly faculty guide you through the research parts of your startup.
4. Take a semester off, work on things, come back. You'll miss out on social life, but that's a tradeoff you're making.
5. Concentrate your startup work towards the beginning of the semester, switch to coursework at the end.
6. Be hyper-vigilant about course-performance. Since you're technically constantly slacking off, you will often need to perform disaster recovery; e.g. shoot for extra credit, to make up for a midterm you didnt study for, etc.
After turning Grayscale on, it took me 2x the time to go back and disable it, because i was looking for the "blue" icon and had a hard time distinguishing between all the icons.
Color helps in _saving_ me time as well -- so let's not forget that :)
You bring up an interesting point. Having controls that stand out and grab attention is good when you don't regularly use them. But while working, in most cases you'll already know the interface well, and don't need it to stick out in order to use it efficiently.
Reading the article, it seems hard to find anything that does not suck (or at least, is not counter-intuitive) in JS.
So many trivialities have to be taken into account.
- You have to store the array length in advance before a loop? wtf?
- "for in" loops are inherently dangerous. wtf?
Every language has pitfalls but javascript seems king above even C++...
No. "for-in" loops that iterate through the properties of an object, and do something with them, without checking to ensure that the property is specific to that object, as opposed to something another library added to the Object.prototype, are dangerous.
The article did a poor job in that section of pointing out _what_ exactly is dangerous. It's not _every_ for-in loop. It's that one in particular, really.
1. Double-count your startup as coursework. Enroll only in project-based classes. Spin off each module in your startup as a project -- e.g. Distributed Systems? Write the EC2 part. Databases? Write the Lucene part.
2. Many EE/CS departments offer bschool classes at the 400/500/700 levels. Use these to get startup advice / stay motivated.
3. Take research credits, have entrepreneurship-friendly faculty guide you through the research parts of your startup.
4. Take a semester off, work on things, come back. You'll miss out on social life, but that's a tradeoff you're making.
5. Concentrate your startup work towards the beginning of the semester, switch to coursework at the end.
6. Be hyper-vigilant about course-performance. Since you're technically constantly slacking off, you will often need to perform disaster recovery; e.g. shoot for extra credit, to make up for a midterm you didnt study for, etc.