2 ms·

Me saying "mock startup" was probably a bad term to use, plus I'm probably missing the use case of hacker school. What I really meant was to work on something l

Me saying "mock startup" was probably a bad term to use, plus I'm probably missing the use case of hacker school. What I really meant was to work on something larger scale as a team. For an example make a clone of hn or reddit, do a web app and mobile, maybe even build multiple versions in different languages. From Dave and Nick's reply it sounds like they tried something along those lines, but learned that people got a lot more value out of working on a number of various smaller sized projects, which is great.

zemo 15y ago
clone of hn or reddit ah ok, I understand. Yes, that's totally something we would do. Cloning, rewriting in a new language, or forking would be appropriate. It wouldn't make much sense to clone Reddit because it's already open source, but forking it and modifying it would be very appropriate. We wrote four chat servers reminiscent of chat.nodejs.org in batch[1]; one with Brubeck (python), one with Chicago Boss (erlang), one with node.js, and then the Brubeck chat program was rewritten to work inside of a Spotify App, so yes we clone existing projects. But typically with a project like that, there's a lot of cool stuff in the beginning and you eschew some more tedious aspects that you would need for a real-world project, like, say... IE compatibility. Once you're housekeeping and your new work doesn't teach you much and doesn't give you cool things to show the rest of the group, it gets really boring really fast, and the environment naturally encourages you to do something more dynamic.
zemo 15y ago
to work on something larger scale as a team oh right, I left this out: we had a period in batch[1] where we all did team work. A number of Hacker Schoolers contributed to the async Python web framework, Brubeck (http://brubeck.io/ http://brubeck.io/), which was a batch[0] project. Perhaps batch[2] will contribute a bit to it, too.

zemo 15y ago

clone of hn or reddit ah ok, I understand. Yes, that's totally something we would do. Cloning, rewriting in a new language, or forking would be appropriate. It wouldn't make much sense to clone Reddit because it's already open source, but forking it and modifying it would be very appropriate. We wrote four chat servers reminiscent of chat.nodejs.org in batch[1]; one with Brubeck (python), one with Chicago Boss (erlang), one with node.js, and then the Brubeck chat program was rewritten to work inside of a Spotify App, so yes we clone existing projects. But typically with a project like that, there's a lot of cool stuff in the beginning and you eschew some more tedious aspects that you would need for a real-world project, like, say... IE compatibility. Once you're housekeeping and your new work doesn't teach you much and doesn't give you cool things to show the rest of the group, it gets really boring really fast, and the environment naturally encourages you to do something more dynamic.

zemo 15y ago

to work on something larger scale as a team oh right, I left this out: we had a period in batch[1] where we all did team work. A number of Hacker Schoolers contributed to the async Python web framework, Brubeck (http://brubeck.io/ http://brubeck.io/), which was a batch[0] project. Perhaps batch[2] will contribute a bit to it, too.