Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In the software world something that works roughly similarly (i.e. where a prototype is differentiated from production) is devops. If you are deploying a toy-project once, maybe you are not setting up a CI/CD pipeline, Terraform templates, Github team permissions, Github/Jira integration, etc etc. - you do all of these things only for "real" products.

But yeah, going from prototype to production with hardware is much, much harder, I agree with you.



And the macro architecture of the project. As a one man project, the only thing it makes sense to build is a monolith.


Yeah as a solo freelance dev I couldn't see how stuff like microservices would remotely be helpful to me in any way. But a few years later I worked in a large-ish team where at some point we hit a wall due to the project being a monolith[1], then I realised what that stuff was about.

[1] the project changed scope and we had to do a large refactoring of the codebase as a result, if it had been based on microservices the refactoring would have been an order of magnitude simpler. Luckily the monolith was relatively well architected with separated service providers so it wasn't super bad.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: