[bochoh]

I've been grinding on kidcarekit.com for a long while in fits in spurts. I find myself working more on the DevOps side rather than the actual functionality but I've learned so much about rails and DevOps that it's been a net win for me even though it doesn't functionally do much yet!

[ptsneves]

Be careful if you see yourself spending too much time on the devops side of things. You can be building a tower of work that has zero customer value in the end.

Even the supposed quality improvements found in an automated way may just turn out very expensive compared to just spending the time doing the QA yourself at specific milestones. Unless your career is devops be very skeptical and track your time and return on that time.

I learned this the hard way although I am a build/devops person professional I came to realise I had a tendency to build really complicated processes that would be ok in a hundred person team, while I actually was working solo. The upside is that there is lots of reusability for future projects and I also became very skeptical of custom CI jobs and CD tools, and try to reduce everything to env variables 1 line bash scripts. I also am very skeptical of automated integration tests as they are incredibly expensive to build and maintain.

[fourseventy]

This is the way