2,117 karma · joined July 20, 2011
Kids these days sure don't have it so lucky, and if they do, well then they probably already hit the jackpot at birth.
How many fewer pgs will we have tomorrow because of the financial burdens and inefficiencies of higher education today?
I emailed patio11 about it. He brought their head of recruiting into the conversation to remedy the situation. Their head of recruitment suggested we hop on a call to discuss.
I can't make this shit up, but guess what the head of recruitment did? Didn't show up to the call.
It's hard to imagine why recruiters get a bad shake /s
Given 10 positions you need to fill anticipating these hires will stick around for 3-5 years each.
Pick one:
- [ ] 10 "less experienced" developers for 3-5 years
- [ ] 9 "very experienced" developers for 3-5 years + 1 "no experience" developer for a few months which you'll then have a 90% chance of replacing with a "very experienced" developer
I’ve been kicking around the idea of moving my stuff off DO. This might be the push that does it.
SO is simply going the same route as Experts Exchange (if you're old enough to remember it). It has amassed a significant amount of knowledge (for free!) that they'll some day hide behind a paywall and sell to desperate seekers of that information.
Every CRUD webapp startup thinks they need FAANG-like hiring processes and fucking suck at it.
I ended up taking a job that was mostly a no-interview process. Two calls to talk about the fit.
They looked at my job history (gasp!) talked to some references (double gasp!) verified my ability to code with my github contributes (omfg I can't breathe!) and offered me a position.
Less money, but definitely less bullshit. It was a good choice for me.
Employers are so focused on the well shared "the worst hire is a bad hire!" that they implement obtuse and ineffective hoops candidates must jump through in attempt to weed out "bad" candidates. This results in hiring those who survive the process, not those that will do the best work.
The biggest gain I've found in using Crystal vs Ruby is reduced memory usage.
Most often my code isn't slow because of the language, but the data access behind it, so counting CPU cycles is less of a priority for me.
Also, COVID-19 remote work is not normal remote work. Lots of other stressors and distractions. So the taste might not be a good one.
There is a whole other world of bootstrapped/profitable businesses out there where these things aren't a focus or problem. You might not even have to take much of a pay cut.
Be wary of this. HR exists to protect the company and void litigation, not necessarily to protect the employee or the employee's work environment.
These technologies can be leveraged to improve usability. Unfortunately, advertisers and 3rd party trackers make it so we can't have nice things.
Yup. If you’re a fixer, knowing this beforehand is going to save you a lot of pain.
There is a general fear in the backcountry Skiing community that any RF devices might impede or negatively impact the use of search and recovery beacons to locate buried partners in the event of an avalanche. Any documentation/speculation on any potential interference?
Location: US, Mountain Time
Remote: Yes
Willing to relocate: No
Technologies: ruby, rails, modern javascript, and many other languages/frameworks
Résumé/CV: Email me
Github: https://github.com/danielwestendorf
Email: daniel@prowestech.com