6 ms·

Me personally, I'd unplug from everything and only allow myself like 30 minutes each day to check for any critical emails (like oh shit type emails, ignore the

Me personally, I'd unplug from everything and only allow myself like 30 minutes each day to check for any critical emails (like oh shit type emails, ignore the normal ones). Then I'd spend my time talking to real people and find things where people are frustrated where I might be able to make an impact. Basically, spend the time learning from them and spending time understanding problems they have (not Dr Phil style of course, but everyday crap). People hacking (for learning) in a sense. But assuming you don't need/like that then here are another few ideas: 1. Learn the basics of how to architect a small distributed system that is fault tolerant, resilient and reliable. You can't learn it all in 11 days, but man you can make a big dent and it is to me one of the most fun and challenging problems to solve. And there is still so much to learn. You can build and test little systems in AWS for nearly nothing using t2 instances. 2. Do as iqonik suggested, find a simple need some group of people have and solve it with an MVP and start marketing and playing with it. If it goes nowhere but you solved an interesting problem for even a small group of people you will still feel good and have had some fun. 3. Write an Android app. From the looks of it you haven't done that but it seems basically up your overall skill set and something you could have fun with. Even if you "hate" Android learning how it works and the good/bad sides might help you in other places.

Hortinstein 11y ago
> 1. Learn the basics of how to architect a small distributed system that is fault tolerant, resilient and reliable. You can't learn it all in 11 days, but man you can make a big dent and it is to me one of the most fun and challenging problems to solve. There was a great tutorial for something like this that google published last month using kubernetes and docker that involves setting up several minecraft servers in a cluster. Would be a great into to docker/kubernetes http://googlecloudplatform.blogspot.com/2015/11/containerizing-in-the-real-world-of-Minecraft.html http://googlecloudplatform.blogspot.com/2015/11/containerizi...
- joshavant 11y ago
  I've been wanting to setup a small distributed system like this as a project for a long time, but struggle to find something that would be useful to build (even to a small degree). Personally, I don't play Minecraft (and, thusly, couldn't really appreciate what I just did by setting up a super duper Minecraft server system). Could anyone think of some more general purpose distributed systems projects that would be a little more generally useful?
  - Hortinstein 11y ago
    I dont play minecraft all that much either, but you could probably replace mincraft with some other networked service, maybe a database simple web server? Database roulette sounds less than useless but still would be a good way to learn
rajathagasthya 11y ago
> Learn the basics of how to architect a small distributed system that is fault tolerant, resilient and reliable. You can't learn it all in 11 days, but man you can make a big dent and it is to me one of the most fun and challenging problems to solve. And there is still so much to learn. You can build and test little systems in AWS for nearly nothing using t2 instances. Learning about distributed systems of late and been wanting to do this for a while now. Do you have any project ideas? I can think of implementing a key-value store.
- davismwfl 11y ago
  Some project ideas: 1. Implement a leader election algorithm and play with the fault tolerance. 2. Implement Raft and learn about it, good and bad. 3. Implement a logging application that has to meet all the requirements for a good distributed system. e.g. log from anywhere, always available, etc. This sounds easy until you actually do it. Alternatively, study code from memcached, redis or some other open source distributed software where there are known good and bad things. Cassandra is another one you could study.

Hortinstein 11y ago

> 1. Learn the basics of how to architect a small distributed system that is fault tolerant, resilient and reliable. You can't learn it all in 11 days, but man you can make a big dent and it is to me one of the most fun and challenging problems to solve. There was a great tutorial for something like this that google published last month using kubernetes and docker that involves setting up several minecraft servers in a cluster. Would be a great into to docker/kubernetes http://googlecloudplatform.blogspot.com/2015/11/containerizing-in-the-real-world-of-Minecraft.html http://googlecloudplatform.blogspot.com/2015/11/containerizi...

joshavant 11y ago
I've been wanting to setup a small distributed system like this as a project for a long time, but struggle to find something that would be useful to build (even to a small degree). Personally, I don't play Minecraft (and, thusly, couldn't really appreciate what I just did by setting up a super duper Minecraft server system). Could anyone think of some more general purpose distributed systems projects that would be a little more generally useful?
- Hortinstein 11y ago
  I dont play minecraft all that much either, but you could probably replace mincraft with some other networked service, maybe a database simple web server? Database roulette sounds less than useless but still would be a good way to learn

rajathagasthya 11y ago

> Learn the basics of how to architect a small distributed system that is fault tolerant, resilient and reliable. You can't learn it all in 11 days, but man you can make a big dent and it is to me one of the most fun and challenging problems to solve. And there is still so much to learn. You can build and test little systems in AWS for nearly nothing using t2 instances. Learning about distributed systems of late and been wanting to do this for a while now. Do you have any project ideas? I can think of implementing a key-value store.

davismwfl 11y ago
Some project ideas: 1. Implement a leader election algorithm and play with the fault tolerance. 2. Implement Raft and learn about it, good and bad. 3. Implement a logging application that has to meet all the requirements for a good distributed system. e.g. log from anywhere, always available, etc. This sounds easy until you actually do it. Alternatively, study code from memcached, redis or some other open source distributed software where there are known good and bad things. Cassandra is another one you could study.