Indeed so what, but do you program on weekends anyway? At least sometimes? Earlier in the thread you complained about golden handcuffs. That indicates there&#x27;s something you&#x27;d rather be doing than your work, but the pay is too good to leave. I scratch my own itches with occasional weekend or night coding and usually it&#x27;s for the fun of it, learning or keeping up with the trends can be a side benefit but not the goal. Often I work with one-off projects like coding a game using a new engine in a functional language. If I didn&#x27;t need or like money as much I might just do these fun projects all the time. I think this personality of programming-as-hobby is pretty common in the field, and when we run into people who program strictly on the job and never any other time, who started programming only in college when they decided to get a degree and only did work for assignments or internships before getting hired, they may be really talented programmers on the job (which is why you can say &quot;so what&quot;) but something feels off culturally. It&#x27;d be like meeting a guitarist who rocks with the best of them on stage while being paid but never plays off-the-clock or seems to have any interest in the instrument or the scene or the genres of play beyond their ability to make money. <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=7423626" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=7423626</a> makes the point well that for many programmers, we&#x27;re just potheads whose potheadery became valuable.