2 ms·
I feel like two hours for something like this is still too little if you want to actually see a ~relatively~ prod level app. The business logic is obviously str
by volkk 9y ago
I feel like two hours for something like this is still too little if you want to actually see a ~relatively~ prod level app. The business logic is obviously straight forward, but starting a new app, adding unit/integration tests, (maybe proper logging), caching etc, and basically anything showing that you're a competent dev will easily eat up 5 hours of your time in my opinion. And if you don't expect anything close to a prod level system, then why ask to build a system like this in the first place as opposed to some basic domain logic functions vs a whole e2e system? Maybe I'm just a shitty/slow dev.
- uncoder0 9y agoI think that's the test though and a perfect lead in to the interview. Build the MVP. Then in the interview explain to me what it lacks and what you think the next steps are to get it production ready... The task isn't build me a URL shortener that's ready to take bit.ly's load.
- volkk 9y agowell i never said anything about bitly's load, but the ability to write readable tests is a skill in itself. same with caching strategies, etc
- qkls 9y agoYou certainly don't need caching for an interview test. And if you want to add tests, how many do you think such an app needs? One to check that data goes in and second that urls come out should be enough to know it works.