Day 681 - Deploy straight to production - https://golifelog.com/posts/deploy-straight-to-production-1668235729994
One of the ‘secrets’ to @levelsio’s productivity is how he git commits straight to production with CMD+D:
"I commit with CMD+Enter git shortcut, no commit messages, straight to production. When I am coding I might be committing 3 times per minute or more etc. Uptime 99.99% no issues. I’m a bit different though 😅 This isn’t advice"
That resonated because that’s what I want to do too. I remember when I was coding Sheet2Bio, I enjoyed the process so much because I could play with code on Codepen, then edit the code directly in Github web and commit directly to production with a click of a button (Netlify takes care of everything). None of that nonsense of logging into Heroku, firing up terminal, writing a commit note, waiting for code to bundle while praying that nothing breaks, deploying to a staging site, and then repeat everything for production. All even if it’s just a single line of code, or a random style change.
That whole process is a barrier to constantly improving and working on my projects, like Lifelog. Whereas for Sheet2Bio when I was building it I was committing multiple times per day, because it’s all just HTML, CSS and Javascript!
I think Sheet2Bio opened up my eyes to what I prefer when it comes to coding my own products, even if that’s not considered industry best practice. @levelsio own self-taught approach resonated because it showed how it’s possible to build products that way.
With serverless and edge computing becoming more mainstream and convenient, I can imagine this approach to be easy to adopt.
Is it possible to build secure, performant SaaS using HTML, CSS and vanilla Javascript? No Javascript frameworks, no bundles, no npm. No installing of special software just to start coding, or to deploy. Everything goes to Github, and something like Netlify or Cloudflare will continuously deploy on a code commit.
Can’t wait to experiment more in this!
"I commit with CMD+Enter git shortcut, no commit messages, straight to production. When I am coding I might be committing 3 times per minute or more etc. Uptime 99.99% no issues. I’m a bit different though 😅 This isn’t advice"
That resonated because that’s what I want to do too. I remember when I was coding Sheet2Bio, I enjoyed the process so much because I could play with code on Codepen, then edit the code directly in Github web and commit directly to production with a click of a button (Netlify takes care of everything). None of that nonsense of logging into Heroku, firing up terminal, writing a commit note, waiting for code to bundle while praying that nothing breaks, deploying to a staging site, and then repeat everything for production. All even if it’s just a single line of code, or a random style change.
That whole process is a barrier to constantly improving and working on my projects, like Lifelog. Whereas for Sheet2Bio when I was building it I was committing multiple times per day, because it’s all just HTML, CSS and Javascript!
I think Sheet2Bio opened up my eyes to what I prefer when it comes to coding my own products, even if that’s not considered industry best practice. @levelsio own self-taught approach resonated because it showed how it’s possible to build products that way.
With serverless and edge computing becoming more mainstream and convenient, I can imagine this approach to be easy to adopt.
Is it possible to build secure, performant SaaS using HTML, CSS and vanilla Javascript? No Javascript frameworks, no bundles, no npm. No installing of special software just to start coding, or to deploy. Everything goes to Github, and something like Netlify or Cloudflare will continuously deploy on a code commit.
Can’t wait to experiment more in this!