Putting aside all the politics involved in this merger, I kind of agree with you... My first thought when reading about Netflix acquiring WB was that a whole lot of IP was going go down the drain thanks to how hard they try to push an agenda in their content.
My opinion is mostly based on old interviews with Coppola when he was asked why he would make Godfather with Paramount and not United Artists. He said Paramount doesn't care about movies, they are bankers and only care about money. They would not interfere at all with his artistic direction. And they didn't.
Now that we have the Ellison, I don't know anymore. His daughter is excellent, but with a different studio. His son has no idea. Maybe it's good, maybe it's bad. We'll see.
My European colleagues are mostly worried about more MAGA nonsense in the media with the Ellisons
I don't like doing the leetcode grind, but all of the alternatives are strictly worse.
* Take home projects filter out people with busy lives. Wastes 100 people's time to hire 1 person. Can't be sure they didn't cheat. No incentives to stop company from giving you a 10 hour assignment and then not looking at it. The candidate with the most time to waste wins.
* Relying on academic credentials unfairly favors people from privileged backgrounds and doesn't necessarily correlate with skill as an engineer.
* Skipping the tech interview and just talking about the candidate's experience is prone to favoring bullshitters, plus you'll miss smart people who haven't had their lucky break yet.
* Asking "practical" questions tends to eliminate people without familiarity with your problem domain or tech stack.
* We all know how asking riddles and brainteasers worked out.
With leetcode, the curriculum is known up front and I have some assurance that the company has at least has some skin in the game when they schedule an engineer to evaluate me. It also tests your general knowledge and in some part intelligence as opposed to testing that you have some very narrow experience that happens to overlap with the job description.
I've spent a heck of a lot more time grinding leetcode than I have working on take-home projects. I always enjoyed doing take-home's because I could really spend time on it and make it something worth showing off - if anything it always felt like the perfect low-stress way to show what you can do. It's amazing how many candidates don't take the time to make it look good (or even meet the objectives in many cases).
Haven't done one since pre-LLM era though and that path seems like it might be completely infeasible for employers now.
That said, the most productive interviews I've been a part of as both employee and employer have always been with the technical people that you'll actually work with and conversational in nature. You can learn a lot about what someone knows by listening to their experiences and opinions (but this depends greatly on the quality of the interviewer)
Any company still using LeetCode at all during interviews is signaling that either they are run like a frat house, or are so dim/indifferent that they're unwittingly cargo-culting one.
Used to be in the same camp here until I had to interview for a specialist role. I'd happily swap Leetcode rounds and doing away with the highly subjective - design a class hierarchy nonsense.
They clip the tails when lamb marking, don't they... I don't think I've ever seen an adult sheep with its tail other than pet sheep, and you can see why they would want to cut the tail, since the wool get all messy...
It’s honestly a little weird to see lambs with tails because they are typically docked so early after they are born. The tails are long and legit look like a 5th leg on some of them.
I think I would also ad to the mix that young folk these days are incredibly overconfident and averse to criticism. A few years back they got a junior dev in here, and I was supposed to help him get on our stack, and ultimately mentor him.
This kid would not accept seniority, would constantly and publicly try to divert from the stack we worked with, he would not take any input on his work without actively fighting the process and will crowd the conversation at team meetings with never-ending Reddit-tier takes that contributed to nothing other than fill his ego.
In the end I managed to convince my boss to get him out, and he now works in Cyber, which will probably cause even more damage in the long run, but at least I can now say "not my problem".
You should have stopped to think about why such a person was hired in the first place, while there are an endless supply of very talented, hard working, and honest young people who would never be given a chance at all.
But if I guess right, hiring is not seen as the responsibility of your company. And that's the core of the problem.
Sometimes people who are able to talk a lot do quite well in interviews - and University students need to be exposed to a wide variety of topics, but rarely support large projects for a long time, so that wouldn't be something that would come up in an interview.
well yes. the people who are really hiring are not the ones who will be working with them. It's a reflection of the MBA optimized culture we live in, so no wonder those who speak the language get in... even if they can't actually work with their immediate teammates.
> You should have stopped to think about why such a person was hired in the first place
The hiring process is probably barely better than random, and, probably even closer to random for a junior hire.
Junior hires mostly don't know anything. So, you're pretty much hiring on "seems smart, curious, and enthusiastic" and praying a lot that you can train them. You're simply going to get misses.
This is one of the advantages that you get running "cooperative engineering" programs. You get to vet juniors before they get welded into your pipelines.
Godspeed. Seems like a good pairing. Bun is sort of the only part of the JS ecosystem I like, and Code has become such an important tool for my work, that I think good things will come out of this match. Go Bundler as well.
I miss running Slackware, if for no other reason that the weird look you get.
For a decade I was running Slackware and a weird "package manager"(1). It was an incredible cool learning environment, but people though it was pretty strange.
I had a colleague once that was an absolute anthropomorphic distro. This man was Linux personified, and he literally walked around town with a Slackware live CD at all times. This man refused to use any other operating system, or any other programming language outside D or Erlang. He was pretty fun.
You can still use it. In fact it has never been easier because flatpak (available as a slackbuild) allows you to easily install apps you would have had to compile yourself many years ago.
reply