Live data from Hacker News

CodeCombat in Y Combinator

blog.nickwinter.net

81–85 of 85 posts

Re: CodeCombat in Y Combinator

#81
post #21
post #17

Congrats Nick, Scott, and George! I can't wait to see where you guys go with this.

Thanks kgodey, we are (understandably) extremely excited to be a part of YC and have the opportunity to really push this project to reach it's full potential.

Please forgive the pedantry, but I'm on a one-man quest: s/it's full potential/its full potential/. P.S. Congrats on getting into YC!

Re: CodeCombat in Y Combinator

#84
post #52

So happy for these guys! I let my kids play this and they love the game!

Thanks for the kind words pla3rhat3r, we're hoping to release a bunch of new content soon as well as open up the level editor so folks can contribute their own levels, so please do check back! Also, if you kids find anything we can improve, please let us know.

Will do.

Re: CodeCombat in Y Combinator

#85
post #66
post #58

Earlier quoted context omitted.

Don't forget that in addition to code and art, you have data. Even if someone clones your codebase and invests time in recreating visual assets, they won't be able to draw on the player experiences you've been collecting. With data, you're able to identify trends and test new approaches smartly in order to maintain the edge; your would-be competitors wouldn't have much more to go on than their own intuition. I won't…

Hey Cyranix, yeah the db will definitely be an asset, especially when it comes time to test the business model of recruiting. Sam Altman's comment on stage about recruiters being sorts sleazy is definitely true, and so casts some doubt on our business model research, but we really do want to try the viral method before putting up a paywall. We did in fact speak with Sam at startup school, pretty small world I guess.…

I know I'm quite late to the party, but I actually keep 100% of the source code open. The only parts I keep in a secret repo are tied to keys, hostnames and addresses, and certificates. But, just having a secret repo where sensitive information (including proprietary algorithms) was enough to satisfy the few investors I talked to.

Mind you, my next project is closed source, as I plan to open-source reusable pieces that will actually help people instead of a massive codebase that few have the means to run.

Post reply on HN