I&#x27;ve recently started preparing for a job change. Part of my preparation is reading books on interviewing, brushing up on data structures&#x2F;algorithms etc. I think these are a must-do for any developer that starts looking for a new job.<p>However, I&#x27;m also torn about what _else_ to do. I&#x27;ve been working on a commercial project on the side that hasn&#x27;t shipped yet. I think it would be great if I could ship it prior to interviewing (would look good and give me something to show&#x2F;talk about that is professional and polished besides my day job).<p>I&#x27;ve also got personal projects on GitHub that span the last year give or take a few small pockets of inactivity. All in all, this is a lot of stuff to take on at one time while also maintaining my current job and responsibilities.<p>In other words, I&#x27;ve got to choose one or two things to focus on (books&#x2F;practicing problems, commercial project that hasn&#x27;t shipped yet, or public GitHub projects).<p>My assumption is I should focus on reading and brushing up while working on my side project even though it&#x27;s not publicly visible.<p>The question is, should I worry if I stop my public GitHub activity for 2-3 months while I prepare and (potentially) finish a commercial project? It will be quite a hole in activity, and with all the &#x27;GitHub as a resume&#x27; hype, it worries me.<p>I&#x27;m most likely worrying unnecessarily about all of this and I&#x27;m probably placing too much importance on GitHub activity (and Stackoverflow karma for that matter...).
Ask HN: Should I fret my GitHub activity when job hunting?