3 ms·
It's an open ended question with lots of jumping off points to talk about implementation details and design. And as far as the backend being trivial (it may wel
by bzalasky 12y ago
It's an open ended question with lots of jumping off points to talk about implementation details and design. And as far as the backend being trivial (it may well be), if a candidate said that in an interview, I'd ask them to walk through how they'd roll their own WebSocket solution. With a different candidate it could jump off into a UI focused discussion. Lots of possibilities.
- taurath 12y agoIts "trivial" in the sense that with almost all the logic on the client (think of something made like a flash game) you'd need only a few core elements (auth, page hosting, user identities or not) on the server, while the majority of the work would be for the client. There's lots of features you might want such as matchmaking, valid move checking and tracking, but it depends on the scope of the project to begin with of course!