61–64 of 64 posts
Earlier quoted context omitted.
I would not call these last ones dream jobs. More like dream-crushing jobs...
That post sound sounds like it was written by someone who dreams of getting power and status. If power us your dream, working for a 3 letter is one way of getting it.
Earlier quoted context omitted.
That post sound sounds like it was written by someone who dreams of getting power and status. If power us your dream, working for a 3 letter is one way of getting it.
But you don't normally blurt it out like that :-) I suspect that jobs in a TLA are closer to the Laundry files than James Bond.
Earlier quoted context omitted.
This is a fantastic representation of how developers should present themselves and work to get their dream jobs. It's hard work up front, but the dividends yield. Kudos
This guy is an elite researcher, so this approach works for him. Try doing that as a regular backend guy and you'll get a puzzled look from management, followed by a boot to the posterior.
My dream job was to be an MD. I went to a grade deflationary undergrad, UChicago, and was too interested in music, social life, and sleeping to achieve a high GPA. I scored 90th percentile on the MCAT and had choruses, piano, humanities, and research in my background, but merely having a 3.35 GPA meant I got 0 interviews after 11 applications to medical school. How devastating is that: you dream to be an MD for a dec…
> I fell into programming for healthcare. I'm not good at it. I struggle to understand basic SQL joins, intermediate R, and intermediate statistics. Maybe you're just overwhelmed and don't allocate enough time to learn each of those concepted? Joins in particular are a very simple concept that could be understood in a weekend of reading tutorials and playing with them. Honestly, the worst thing about them is probably…