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.
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.