Admitting that the code you wrote is no longer necessary. Erasing it and starting over, or giving way to a better alternative. On a long enough timespan, holding on to old code can hinder an entire team or even organization.

There's still a stigma that marketing somehow equals snake oil salesmanship. It's supported by myths that certain products became immensely popular without any marketing that ironically you read about in media that promotes the same product. Marketing and programming map to different personality types. You program a machine, alone, and it's predictable. Marketing is based on understanding and dealing with people, their needs, emotions and inner drives. No wonder our first geek reaction is to shy away. But in my experience most people with engineering background who are given the job of marketing, eventually understand what's the deal, and either become what it takes or find and support someone to do the job well.

I can recommend Claudia.js which raises the level of abstraction for you so you just do npm run deploy from command line. As Philip Davis mentioned automating it completely via CI/CD, so you just do git push , would be a possible next step. Semaphore for example provides special support for setting up deployment to Lambda ( docs ).

Check out these two tutorials: Dockerizing a Ruby on Rails Application Continuous Deployment with Docker, AWS, and Ansible

Since you've mentioned 30 lines I guess your app is doing something more complex than trivial CRUD so... I find TDD to be a great guide. If you're writing a controller spec (mocking approach, as explained in the original RSpec book), than anything longer than ~5 lines is usually too much, because writing a sensible spec becomes just too hard. Have controller only pass params to other objects which live in lib or wherever your domain logic is.