111–120 of 391 posts
i envy dimitri's ambition and capabilities. i want to be able to dedicate that much effort and more into something I'm passionate about. mostly personal discipline/skill issues but MAJOR props to dimitri and this awesome project.
Doom compiled to just 177 TB (terabytes) of TypeScript types. Amazing on many levels.
In TypeScript types, everything is possible, but nothing of interest is easy.
Honestly every time I worked on TypeScript codebase and the type definition "any" started popping out more and more often, I felt I'm starring into the abyss.
There are valid use cases for any (such as type constraints). Playground with example here: https://tinyurl.com/5ahs366a
type Values> = T[keyof T]Earlier quoted context omitted.
> But if he was being considered for a mid level generalist role, yeah, none of this would’ve mattered. And why should it? As someone who has been on the hiring manager side, I'll state the obvious: because it demonstrates insanely good problem-solving skills that would transfer to nearly any challenge.
Would he have made it past your recruiter screen though?
One of the top comments in the video: > If this guy goes for a big tech interview they're still going to ask him how to invert a binary tree The industry's hiring process is so messed up that this is completely believable. "We've decided to prioritize other candidates, as you are strong in the fundamentals but lack the kind of experience in Vue that we're looking for."
By now there is more than one story how some open source developer wasn't hired because their skills with the project they created was not sufficient for the job.
One of the top comments in the video: > If this guy goes for a big tech interview they're still going to ask him how to invert a binary tree The industry's hiring process is so messed up that this is completely believable. "We've decided to prioritize other candidates, as you are strong in the fundamentals but lack the kind of experience in Vue that we're looking for."
Faced with the immutable fact that the chief executive cannot watch everything, that there will be pockets within the organization where people will sell access to a $300k job, and where others will hire from their family, their tribe, or so on: you make a system that is meant to prove some minimum standard while constraining your interviewers.
One thing that is not immediately obvious is that the Big Tech hiring process is to constrain your hiring team in who they bring on.
Startup executives are close to the road so they can tell if the rubber’s good much more easily.
The hiring process is designed around the constraint of executive attention. As are most things in firms.
Earlier quoted context omitted.
By now there is more than one story how some open source developer wasn't hired because their skills with the project they created was not sufficient for the job.
I go back and forth on my opinion for this one. You wouldn’t necessarily want a mechanic or engineer to drive a race car, for example.
A short explanation or link to a resource would really be helpful. :)
One of the top comments in the video: > If this guy goes for a big tech interview they're still going to ask him how to invert a binary tree The industry's hiring process is so messed up that this is completely believable. "We've decided to prioritize other candidates, as you are strong in the fundamentals but lack the kind of experience in Vue that we're looking for."
Earlier quoted context omitted.
There are valid use cases for any (such as type constraints). Playground with example here: https://tinyurl.com/5ahs366a
Seems to also work without any: type Values > = T[keyof T]
But in my case it's not widening anything, in Record, B can already be `any`thing.
People tend to see it as an unsafe escape hatch (which is how it is abused), but it's just a set of all possible types.