How to become a part-time programmer
I&#x27;ve done this for a number of years. This would be my current advice:<p>- Don&#x27;t try it on-site (unless they specifically were seeking a consultant beforehand). It&#x27;ll just create resent.<p>- Therefore go for remote jobs. Which don&#x27;t need to be advertised as such - strong applicants can negotiate a remote arrangement.<p>- Don&#x27;t bill by the hour, but daily. Leaving your earnings aside, this approach puts the focus in work days, not hours (duh), therefore you aren&#x27;t framed as a &#x27;part-time&#x27; contributor.<p>- When asked how many hours your work day takes, reply &quot;as much as needed&quot;. This would be in fact a honest response. Some days (especially as you join a team) you&#x27;ll need 6-8h&#x2F;d to perform acceptably. Gradually you&#x27;ll be able to deliver the same in 3-5h&#x2F;d.<p>- The key part is, employer&#x2F;client is only aware (in principle) of days and results (tickets closed, commits pushed, meetings attended, etc). Again this is not hiding the truth - it is focusing on the results.<p>- Do keep track internally of your time spent per day, and have some way to graph your productivity vs. the time spent. That graph can eventually save your ass!<p>- Be aware that (at least IME), even if spending as little as 3 effective hours per day, a large chunk of your day can revolve around work, especially if you interact with a typical team. This includes being available in Slack, for meetings etc.