56 karma · joined August 14, 2016
I don't know. In my experience, estimation is one of the most difficult aspects of software engineering. A black swan event or some unknown unknown will blow apart your thoughtful estimate (especially near the end of a development cycle) - no matter how good you are at it. I'd much rather have a crystal ball at hand, and let the chips fall where they may, than engage in a herculean struggle to accurately predict the future.
edit:formatting
Real wages have effectively flat-lined over the past 50+ years.
What you think of this graph? https://www.epi.org/productivity-pay-gap/
Because by my reading, it looks like the average American is not reaping the gains of this country's GDP output by a significant margin.
Some background - I've been working on this for several months now, experimenting with various CNNs (settling on a modified LeNet), hyperparameters and parameters. The bulk of the experiments have been failures - a typical scenario is the loss function decreasing in the training phase, but winding up unable to correctly predict labels in the test phase. There has been a progression however - from predicting either label A or B (but not both), to predicting both (but no better than chance), to doing a little bit better than chance. Maybe I'm fooling myself - I don't know. That's why I've been scouring the Internet for similar kinds of work (and not finding anything truly useful) and now reaching out to HN. If there's work out there that definitively rules out working in this space, I'm all ears. Otherwise I'm going to keep on experimenting. (edit:formatting)