3 ms·
Definitely second this. Taking risks like this is the only way I've kept the job interesting, and managed to make the projects actually good. The downside is
by stuaxo 9y ago
Definitely second this. Taking risks like this is the only way I've kept the job interesting, and managed to make the projects actually good.
The downside is when it doesn't pan out, you can have a bit of catching up to do.
- jmartrican 9y ago> The downside is when it doesn't pan out, you can have a bit of catching up to do. That is so true as I am catching up now on a Saturday. You also learn to not roll your own solutions and check a second or third time for a solution on Github or open source community.... and check again if you don't find it.
- vbezhenar 9y agoI'm doing that too and I'm always extending my estimation of work to include those potential researches. Smart people said, estimate work to be done and multiply it to Pi. If I'm feeling uncertain, I'm additionally multiplying it to E. Result estimation might be a bit pessimistic, but I've found that it's better than wrong estimate resulting in missed deadlines and work at nights.