250 karma · joined July 2, 2015
For me, changes were the key. Burnout melts away. But you can burn out in any role. If you have the skills to do tech work, try to keep them alive. Coming back to hands on tech work is incredibly refreshing. So is leaving it behind for awhile when you've reached the burn-out point.
Corporate culture embraces the notion of management as a profession. I think programming would benefit greatly from more of a tradecraft model, where leadership is provided by the master practitioner rather than the professional manager. In the alternate universe that's how we do it. The bottom line productivity boost is awesome. I don't know if it scales, but I don't care to scale.
-- 63-year-old full-stack web and machine learning programmer...living the dream
Here's how I think it works. Skilled interviewers are biased toward rejecting candidates based on any negative impression. Structured interviewing has the same effect. It's the precision versus recall tradeoff. For this use case only precision matters. Extremely low recall is fine.
Also, in the GPA prediction example, the interviewer is penalized for predicting a low GPA for a person who performed well. But in hiring, there is no penalty for failing to hire someone who would have performed adequately.
(Yes, I understand there is an implicit assumption in my argument that candidates are not in short supply, but that's usually true, certainly at Google)
If you're hiring: Get the above out of your pathetic small minds and start hiring the smartest people you can find. Look for successes in any industry. Your business isn't that unique. The best people can learn it much faster than you did.
So include the social graphs of people who are on antidepressant discussion boards and pick up on friends, family, socioeconomic features ...
I so want to use ML tools on medical treatment data, but it's so hard to come by. Have toyed with a couple of startup ideas based on the tendency of people who share a condition to establish ties. Crohn's disease, cutaneous lymphoma. But the groups are too small. Mood disorders on the other hand...
But for some people the results are miraculous. They solve real problems with few if any side effects. For others, they either don't work at all or have intolerable side effects.
The situation would be a whole lot better if we could predict likely efficacy and side effects in advance, especially cases where treatment is more likely to do harm that to help.
Interestingly, I've read a lot (not so much recently) on the subject and taken several SSRIs myself (with good short term experience, minor sides), but I learned a lot from the discussion here. So many people take these drugs — the data necessary to understand and perhaps to predict ... is out there. Not easy to get at, but really plentiful. Reading this made me think about the feasibility of mining message boards for first person accounts of SSRI experience.
Use another tool to create each slide. Photoshop if that's your thing. I use omnigraffle on my mac a lot. Each slide should consist of a single jpg or png.
So you don't have to learn anything about PPT, which is a worthless tool, but unfortunately ubiquitous. Make your content and use PPT only to share and present.
It struck me at the time that the qualities that were expressed most strongly were the ones that ended up having names in our language. But there were others for which I would say to myself, there is something about this group (e.g. those with the greatest expressed value of F124) that I recognize, but can't quite put my finger on.
Of course, I was looking at people through a keyhole, their TV viewing preferences being the only information I had.
Also, I noticed that these "came into focus" most clearly at a certain level of compression (rank).
FWIW
Methodologies are useful as tools used by developers to organize their work and make themselves more productive.
When methodologists enter the picture, the benefits are lost, because methodologists serve the methodology, not the developers' product.
All methodologies are eventually hijacked by methodologists. Some dev orgs are smart enough to avoid them or at least limit their influence. Mahmoud is clearly not working in one of them.