DevOps as a self-taught developer

#devops #beginners #programming #webdev

Learning software development is not easy, you must figure out everything and mostly by yourself. While Tutorials are fine, they just give you an example and often not a proper one. I'm learning web development for a year now and I can tell you I'm starting over. After learning the basics of PHP and some Laravel by examples and tutorials, I've decided I want to start over, learning to do everything properly and most importantly - to understand what I'm doing. So why did I write DevOps? It is simple - I'm setting everything myself: the local development environments, docker images and containers, test servers in cloud, deploying to production. And overall, everyone is doing the same, until you work in a team with seniors or DevOps to do it for you.
Believe in yourself, you're doing much more than you think you do!

Top comments (0)

How to write a kickass README

Arguably the single most important piece of documentation for any open source project is the README. A good README not only informs people what the project does and who it is for but also how they use and contribute to it.

If you write a README without sufficient explanation of what your project does or how people can use it then it pretty much defeats the purpose of being open source as other developers are less likely to engage with or contribute towards it.