I did that route. My experience in MY environment: Sysadmin/support is a very different gang from the Dev group. So I started with simple scripts (before cfe

I did that route. My experience in MY environment: Sysadmin/support is a very different gang from the Dev group. So I started with simple scripts (before cfengine/puppet). Later I did some coding to hibernate machines using MFC. After I started using python to generate inventories and to admin the whole University I used to work. Then the first site on Django. After another one in Django. Later a project in Django. Then some Consulting. And then a big one project in Django being consumed for a lot of customers. Now If I get my code from firsts projects I think: "Serious.. This code sucks look this..." My suggestion: 1. Accept that your code will be bad; 2. Accept that it will not be "smart"; 3. Once people ask for more features you will understand "Why" there are design patterns and best practices; 4. Once you are making money, you will understand the need for git, CI/ CD, testing. Sure you can learn about it first, but you really understand when you are on the field battle. So today I have 2 CVS one for Sysadmin/Devops and Other for Developer as people have a hard time understanding that I can do both very well. E.g., Today I finished a feature for a customer CRM python system, and later I set up an Asterisk PBX on cloud and a postfix setup. Keep learning, practicing, and it will compound over years PS. By doing well I mean: I am not updating my LinkedIn for 3 years as someone may do a tempting offer... I admit I afraid of the right proposal and say goodbye to some customers.