4 ms·

Edge cases are relevant for some definitions of "production ready" but not for all. I mean it's not like someone dies if the search just mostly works. To put

Edge cases are relevant for some definitions of "production ready" but not for all. I mean it's not like someone dies if the search just mostly works. To put it another way, an engineering constraint is a three hour budget and part of the test is can the candidate accept the cost-benefit implications of such a constraint?

bryanrasmussen 4y ago
yeah, but production ready is what is checked against, since you have 6 days and 23 hours to compete the code test that should take approximately 3 maybe 4 hours I assume the actual time is 6 days and 23 hours if that's what it takes to make it 'production ready'. >Edge cases are relevant for some definitions of "production ready" but not for all. yes sure, if all your platform looks like shit on mobile then when your new component looks like shit on mobile it is production ready, however when all you have is that one component and nothing else pretty sure people will resize etc. and say hey it is not production ready! Also production ready also refers to code quality of course, did you turn everything that should be module into a module even though doing so of course adds a little more time. >To put it another way, an engineering constraint is a three hour budget this is not what they say they want however, I would be willing to deliver as much as I can in 3 hours and say how's that? But then I wouldn't get the job so in the same time I know, well it's not worth doing. I mean it's not worth doing since I am just as far along with 3 other companies, one which gave me a 1 hour test which took 1 hour and probably will pay better and have better benefits. So obviously there is just no scenario in which I would do this test, but what I'm wondering is how close is my estimation to how much other people think it would take.
- brudgers 4y ago
  As I said elsewhere, I might be able to do it in a month —I’d have to StackOverflow enough React — but can imagine someone who can knock it out in an hour. That’s a perfect candidate vs the don’t call us we’ll call you I would be. If you can’t deliver what they expect in the time window, then the simplest explanation is you are not able to provide what they are looking for. This makes it a useful and relevant assignment for both parties. A test that most candidates can pass is a waste of everyone’s time. —— Crappy on mobile may be good enough because production is a business process not an engineering theory. Low initial cost may be preferable to lowering operational cost. The bottom line and cash flow are legitimate measures of code quality.

bryanrasmussen 4y ago

yeah, but production ready is what is checked against, since you have 6 days and 23 hours to compete the code test that should take approximately 3 maybe 4 hours I assume the actual time is 6 days and 23 hours if that's what it takes to make it 'production ready'. >Edge cases are relevant for some definitions of "production ready" but not for all. yes sure, if all your platform looks like shit on mobile then when your new component looks like shit on mobile it is production ready, however when all you have is that one component and nothing else pretty sure people will resize etc. and say hey it is not production ready! Also production ready also refers to code quality of course, did you turn everything that should be module into a module even though doing so of course adds a little more time. >To put it another way, an engineering constraint is a three hour budget this is not what they say they want however, I would be willing to deliver as much as I can in 3 hours and say how's that? But then I wouldn't get the job so in the same time I know, well it's not worth doing. I mean it's not worth doing since I am just as far along with 3 other companies, one which gave me a 1 hour test which took 1 hour and probably will pay better and have better benefits. So obviously there is just no scenario in which I would do this test, but what I'm wondering is how close is my estimation to how much other people think it would take.

brudgers 4y ago
As I said elsewhere, I might be able to do it in a month —I’d have to StackOverflow enough React — but can imagine someone who can knock it out in an hour. That’s a perfect candidate vs the don’t call us we’ll call you I would be. If you can’t deliver what they expect in the time window, then the simplest explanation is you are not able to provide what they are looking for. This makes it a useful and relevant assignment for both parties. A test that most candidates can pass is a waste of everyone’s time. —— Crappy on mobile may be good enough because production is a business process not an engineering theory. Low initial cost may be preferable to lowering operational cost. The bottom line and cash flow are legitimate measures of code quality.