I'd like to take this question one step further: When do you think is an appropriate point to take a sabbatical? After working for a year, two years, three etc. The reason I'm asking is that junior developers might feel the need for a break earlier in their careers compared to experienced devs.
"Sabbatical" after 1 or 2 years is a joke right? It's no wonder companies are looking hard to ditch entitled software engineering labor as quickly as they can.
I think employers, already prone to looking askance at resume gaps, might be particularly put off by that (no counter example of long commitment, no way to brush it off as a better offer or need to move). I personally wouldn't risk it until I had four or five years at one company but others may have more confidence.
You might be able to get extended unpaid time off without leaving. My team has an unofficial policy that you can take up to about a month unpaid (not every year).
Come on, this is the kind of project that could be done by an intern in a day or two. Not much of a waste and it's nice to be able to access models without login or history.
Amazing timing, I was just getting into open source these days and I have the same feelings you described in the beginning when I make a contribution.
The essay kindly tells us how you feel right now, proud but tired and contemplating. IMHO That’s always going to be the case for hard working people like you, but still it is interesting that you kept pushing even though you didn’t feel comfortable and confident doing all those things you were unprepared for. And even though you were able to overcome all those challenges, you still doesn’t sound satisfied with you current situation. Maybe that’s because you have even bigger dreams?
I think you’ve done an amazing work and deserve a long rest. I’m sure it’ll be bit harder for people depending on you, but they’ll get used to it eventually and you’ll feel more relaxed and maybe more fulfilled by giving yourself some space and time.
I knew other people felt the same way! There was this coffee shop I always hanged out, which recently "permanently closed" as the owner died RIP. It is really hard to explain that feeling, which I literally can't. But awesome idea!
Yes! This! The code should be so boring it's never a point of discussion. This implies several things - for example when bringing in a new person, it should be straightforward to teach them how to work with codebase.
Other implications include naming conventions, sufficient amount of documentation, what architectural patterns to choose (if you need to do something that even hints of accidental complexity you need to have really good justification for it)...etc.
> The code should be so boring it's never a point of discussion. This implies several things - for example when bringing in a new person, it should be straightforward to teach them how to work with codebase.
That simplicity, and we could say the same thing for React, makes it the worse candidate for developing apps. The building blocks are so small that it is almost impossible for juniors/mids to write well-written/well-structured code.
reply