4 ms·

You don’t really sound like a person who writes code for fun. Just because you don’t or cant do it doesn’t mean that others should follow. side projects’ inten

by pm90 4y ago

You don’t really sound like a person who writes code for fun. Just because you don’t or cant do it doesn’t mean that others should follow. side projects’ intended audience isn’t future employers. It can be anything the creator wants to hack on just because. > Most people's public repos are examples of very bad quick hacks, starter projects with no additional work, or things so poorly documented I can't even tell what they are. lol ok. Having worked at several corps generating hundreds of millions of dollars of revenue, most of them have been powered by the gnarliest of hacks duck taped together and kept alive by armies of pitiable engineers with a pager. Your expectations are wildly out of touch with how most software companies operate.

librish 4y ago
I think you've interpreted the post incorrectly. It's not saying "don't do side projects for fun". It's saying "don't do side projects as a means to get hired" which I agree with.
onion2k 4y ago
You don’t really sound like a person who writes code for fun. On the contrary, I write code in my spare time a lot. I have a ton of GH repos, CodeSandbox things, Codepens, etc. I tinker with things all the time. I'm just aware that others don't so I try not to let my own preferences bias how I hire people. Missing out on a great candidate because they're not like me would suck for my team. Plus, I'm also aware that people's 'free time code' often isn't representative of how they write code professionally. I wouldn't want to be judged on mine... Your expectations are wildly out of touch with how most software companies operate. I've run a software company. I've worked at a lot of them. I'm very aware of how much things are held together with duct tape and undocumented YAML files. I don't see how that would impact how I'd review someone's public GH commits though. The company they work for might be operating a codebase that's one commit away from catastrophe, but it might not. I don't get to see that code so I can't really use it as a reference.

by pm90 4y ago

librish 4y ago

I think you've interpreted the post incorrectly. It's not saying "don't do side projects for fun". It's saying "don't do side projects as a means to get hired" which I agree with.

onion2k 4y ago

You don’t really sound like a person who writes code for fun. On the contrary, I write code in my spare time a lot. I have a ton of GH repos, CodeSandbox things, Codepens, etc. I tinker with things all the time. I'm just aware that others don't so I try not to let my own preferences bias how I hire people. Missing out on a great candidate because they're not like me would suck for my team. Plus, I'm also aware that people's 'free time code' often isn't representative of how they write code professionally. I wouldn't want to be judged on mine... Your expectations are wildly out of touch with how most software companies operate. I've run a software company. I've worked at a lot of them. I'm very aware of how much things are held together with duct tape and undocumented YAML files. I don't see how that would impact how I'd review someone's public GH commits though. The company they work for might be operating a codebase that's one commit away from catastrophe, but it might not. I don't get to see that code so I can't really use it as a reference.