There is a big gap between a book and informal notes, docs, comments though. At least big enough to drive several tools into, or they wouldn’t exist.
12,701 karma · joined August 13, 2009
There is a big gap between a book and informal notes, docs, comments though. At least big enough to drive several tools into, or they wouldn’t exist.
All music recommendation engines at this time still aspire to be mediocre, they aren’t even playing the S.A.,e game as a human who is good at it.
Unfortunately, such humans are unevenly distributed.
1) Be better than the overwhelming majority of your peers, and be noticed for this. You are quite likely to find interesting opportunities come your way. I do mean overwhelming though - small fraction of a percent.
2) Specialize in something most people can’t or won’t do. This includes difficult, obscure, and unpleasant work.
In both cases some of the biggest $ comes from independent consulting, once you’ve built up a network and a reputation for fixing a particular pain point corporations have (bill for value, of course).
If it’s coming from a peer, especially one whose been round a few more blocks than you, may just be an observation about life.
This isn’t just aesthetic. Although probability is one of the oldest areas of mathematical thought, dating back millennia, it took measure theory to put it on a really solid basis, several decades ago. These approaches are powerful and useful, but some of the corners are certainly counterintuitive.
In most places I've lived, streets are objectively less dangerous than they were a few decades ago in all aspects except traffic density, which is a mixed bag. In places with poor urban design, I can see the argument that street (crossing, particular) is high risk for say 6-8 year olds. In places with better design, the idea that a 8 year old, let alone a 14 year old, shouldn't be able to navigate a reasonable distance by themselves seems pretty crazy.
FAST is an algorithm for efficiently looking for "interesting" parts (basically, corners) of an image, so you can safely (in theory) ignore the rest of it. The output from a feature detector may end up contributing to an energy function later, directly or indirectly.
And do the harder exercises. Really do them, not just read and tell yourself you understand how to do that one and move on.
Most companies don’t constrain an individual employee from providing a recommendation. People might not want to do it, but that’s a different issue.
You absolutely will be a better engineering leader if you a) understand deeply the system your team is working on (though perhaps not all the corners) and b) maintain enough technical knowledge to keep up with changes.
To my mind though micromanagement, on the other hand, is the art of making decisions for people when they don't need it, and leaving your team unable to progress without you hovering over the work.
In this view micromanagement is always a poor choice, even worse if you don't know enough to make good choices for those team members.
I suppose the steel man version is that in an effort to avoid making that mistake, inexperienced managers back off too far and don't understand enough about the work anymore. This is in my experience a real problem, but needs a different name.
It's often the case where a good senior technical leader/manager could do the work most or all of the team members, and in the case of more junior ones, probably do it much more efficiently also. But they can't do that and be effective at their own role. Group velocity of the team is highest when they mostly coach from the sidelines.
Get a decent mattress and pillows. Replace your pot from college with the handle that falls off. Paint the room you hate the color of. The ROI on such things is huge.
I've approved or started (or both) this sort of thing on company time before, at more than one place.
For context, this was typically early stage R&D, and many/most of the employees had some academic background, though that ranged from "decades ago" to "we just hired you after a masters degree".
In this setting, it's a pretty natural continuation of the common "journal club" approach in academic research groups. It spreads the effort around, helps the team stay on top of new work, and generally improves professional development - if done well. It does take a bit of effort to keep fresh.