Earlier quoted context omitted.
There is little difference between "experience programming during a job" and "experience programming for fun". It is the same activity. Over of my more recent hobby projects was writing an RSS->IMAP bridge in maybe a couple hundred lines of Python. It has one user (me). This is fairly typical. Until this year, my primary work project was a toolset for streamlining one-off ETL projects. It has parts written in I think…
Yeah, exactly. With the work frequently being the dollhouse. At my various $dayjobs, I spent most of the time building various flavours of the same CRUD (web CRUD, desktop CRUD) in dumb mainstream languages. At home, I do everything from video games to data processing to AI, in actually productive languages. The difference I see is that with hobby projects, you're at least free to make something that's actually usefu…
It used to be one of the biggest reasons why we learned so many thing in comparison to the rest of the team(which was fairly big), to a point we could make a lot of very critical design decisions or write an application that could save hours of time for our users.
Its one of those axioms of software development I've learned, in order to do good work you have to do mountains worth of waste work.