Or this: imagine seeking an estimate on when a house will be built, trimmed, painted, furnished, decorated, and filled with every item needed practically and for comfort by the homeowner.
It’s a living process that requires continuous reassessment of priorities and scope, and in fact never finishes when you consider the life of the home.
>No one exceeds their potential. If they did, it would mean we did not accurately gauge their potential in the first place.
50% of people pull the lever?!?
I hereby declare that if I'm ever going to be stuck in a trolley for my entire life, I do NOT want the lever pulled. Toss me a smartphone charger and my life wouldn't even be that different, day to day.
My suspicion is that staring at objects closely and under dimly lit conditions causes pseusdo-myopia which is later exacerbated by wearing glasses, causing actual axial elongation in the eyeballs through hormesis. Especially since this is what seems to happen in other animals when we dissect them.
Are you implying that cell phones could be a factor?
Anybody ever do something like that? How effective it would be probably depends on unit test coverage.
You could also probably just do the same thing in prod with a dummy user.
Our tests would set up the app's full context, get a hook into the logging framework to watch for log statements, then make requests to the service containing a set of dummy credentials, like { username: "foo", password: "bar" }. If a log statement containing "foo" or "bar" was detected the test failed.
It's not going to catch every type of issue, but at least some potential footguns can be preventing this way.
This seems like it would be great for rapid prototyping.