4 ms·
I disagree with your point about juniors with unfinished side projects. There are fun parts of coding and tedious parts. Greenfielding, using a new language/fra
by vlunkr 4y ago
I disagree with your point about juniors with unfinished side projects. There are fun parts of coding and tedious parts. Greenfielding, using a new language/framework/library, coming up with high-level architecture is fun. Tracking down bugs, forcing a new feature into a legacy system and writing test is not fun. I'll do it if I'm compensated, and it can be rewarding in it's own way, but if I'm coding for leisure (and avoiding burnout), then yeah, I'll drop a side project as soon as it stops being fun.
- PragmaticPulp 4y agoThe difference is in how they’re presented. Often, I see resumes that claim people built complex things, but when I check their GitHub it’s just a few commits over the course of a week several years back. The key is in presenting it within the right context. Doing a quick architecture exploration is indeed fun and insightful, but presenting that work as if it was a usable project would be misleading.
- vlunkr 4y agoAh, yeah in the context of building a portfolio that makes sense.
- deleted 4y ago[deleted]