[williamdclt]

> Most people have still written code for school or a hobby project

School was years and years ago, and has nothing to do with my current skills.

From the people i personally know, most do _not_ have a hobby project, even fewer have hobby projects that showcases their technical skills. Nor should they be expected to. Most people have non-programming hobbies.

> I cannot understand how some developers have no code to show.

It's really not that deep, I'm worried if you really cannot understand. I don't code outside of work, I'm not interested in doing it. I'm good at software engineering, not passionate about it. I have a bunch of other hobbies. There's no reason I'd have any code to show now or at any point in the future.

> let them make a small project over the weekend and then do another interview where you ask stuff about what they've made

If I'm paid for it, sure why not I could do that. I won't love it but hey I'm looking for a job, I'll put the legwork in. But if this is the only or the "preferred" interview process for a company, I need to point out that it is deeply discriminatory as it advantages people who have the time to do a weekend project: for example it benefits males disproportionally (women do most of the care work in any country, also the most house work, also have a higher chance to be a single parent, all of which impacts the time they can put in a "weekend project" if they can do it at all).

[ryandrake]

> It's really not that deep, I'm worried if you really cannot understand. I don't code outside of work, I'm not interested in doing it. I'm good at software engineering, not passionate about it. I have a bunch of other hobbies. There's no reason I'd have any code to show now or at any point in the future.

It's like asking a dentist interview candidate to show you examples of fillings and crowns they did at home as a hobby. I don't understand why there is this automatic assumption that people who program at work also do it outside of work.

[cess11]

I ask for code, and if they have none prepared I ask that they spend at most two hours building something they enjoy.

I expect a decent developer to be able to bootstrap and write most of a fun toy project in a domain they know well or at worst some kata from the Internet within half an hour. Then we spend some time screen sharing and talking about it, similar to pair programming but less problem focused.

If you can't do it you'll likely struggle a lot when working with us because we commonly use throwaway prototypes.

[pjmlp]

Which is fine, you don't have to take in every candidate, nor do we need to apply to every company.

[cess11]

Sure. A bigger organisation with more layers in their technology department could treat candidates better that would struggle with a hiring process like mine. More detailed tickets, more mentors available, bigger cashflow, things like that.

In such settings it's also somewhat common to hire consultants in bulk, like 5-10 at a time, try them out for six months and keep the ones that enjoy the work and fit well in the organisation, and over time try to employ some of them directly.

[mixmastamyk]

If you're not interested, you're not interested. Not even about "passion" at that point, but the bare minimum interest in your industry. I said it better previously: https://news.ycombinator.com/item?id=15553482

[adastra22]

If you have literally never written a line of code outside of your work in the last decade, you are not a culture fit. This itself is a filter.