- 0 Posts
- 11 Comments
FYI, leetcode is not a “learn to code” website it is a “practice problems that will be asked at tech interviews” site. A lot of these problems are inspired by (or maybe are even literally from) interviews at “top companies” like Google, Facebook, etc. They are almost completely algorithmic or data structure problems, i.e. “unrelated to your actual work” (well, most of your actual work for most people).
Wouldn’t you argue that putting hard restrictions would have the benefit of shrinkjng your recruitment team? To be clear, I’m coming from an extremely anecdotal point of view, but to me it seems like tech is full of imposters jumping from job to job, playing up their experience. Recruiters cannot spot these people, because they know all the jargon despite having none of the skills. This is why these technical interviews exist, but now those are even being gamed by people by studying leetcode. I’d be really curious what a high quality tech recruiter does vs the average.
We do require a BS in computer science
The only scenarios where I’d think I wouldn’t require one are
- I want cheaper labor
- I am really desperate to fill a position
- The skills I need in a candidate are incredibly niche, thus I want to widen the applicant pool.
#1 and #2 are indicative of other problems in your company. I get that you can be a good dev without a degree, but from an employer perspective, it seems like an easy way to save time and money on hiring. I am convinced that a lot of money is wasted on recruiters who throw everyone under the sun into the hiring process just so they can justify their existence.
Build your own locally hosted cloud!
This is the hard part to sell people. I feel like for self-hosting to become popular, there would need to be a “plug ‘n’ play” device that essentially has everything you need to set up a small server on your home network. If you could set up a home server as easily as you can set up a Google Home device, that would be amazing.
Does it execute both, or does it execute the branch that is more likely to be valid? Branch prediction seems like it’d be way more performant than executing both branches until the result of the branch condition is available. If you think about it, what you’re proposing will cause the CPU to always execute instructions that are not meant to be executed when confronted with a branch whereas branch prediction will only execute these “useless” instructions in the unlikely scenario where the prediction is incorrect.
This is such a high level description that it is a meaningless comparison. The fact that Fallout doesn’t take itself nearly as seriously as Westworld is already a huge difference. Sometimes the implementation is what is valuable, not the idea.