Let me weigh in here. I've worked with Rails, ported a php application to Django, currently working with Spring MVC and Angular JS.<p>PHP is a scripting language, Django is a framework. I think you are comparing 2 different things.<p>If you want to get into web development, there are 2 major concepts/skills you need to get down. First, understanding of MVC, or "MTV"[0], as in Django's case, or whatever other variation of said design pattern (MVP, MVVC, etc..). Second, writing and consuming REST APIs. The frameworks will handle or at least guide you through the rest. CSS, HTML, and JS will help you with the front end, but I think as someone who works in ops, you'd be more comfortable establishing a solid back-end first. You can always bootstrap the front-end.<p>Personally, I try to stay away from anything PHP based. I don't think anyone in their right mind would start a new project with a PHP stack. Frameworks like Django, Rails, and other JS frameworks are much more mature, in terms of utility, than anything you'll find in PHP.<p>Since you already have experience with it, it would be fairly easy to work with Django after running through a few tutorials.<p>IMO if you go the PHP route, you'll get stuck with old technologies, as in your job prospects would involve maintaining legacy php apps. I haven't heard of anyone starting a new project with PHP.<p>A developer should be concerned with building applications to meet requirements, writing and consuming REST APIs, and implementing features and utility functions around those.<p>Once you become fairly experienced with one web framework, whether it's Django or Rails, explore another framework. Don't get stuck with a single technology stack. That's the mistake most developers make. They never get out of their comfort zone. Become a polyglot.<p>Fact of the matter is, some frameworks have better integration with certain tools, because of community support. Learn one framework, then learn another, and keep going.<p>Personally, Django is one of my favorites, but I also love Rails. Both do certain things better than the other. There's no perfect framework.<p>Check this book out, it's free if you read it online. It is a really good resource on TDD with Python and Django
<a href="http://www.obeythetestinggoat.com/" rel="nofollow">http://www.obeythetestinggoat.com/</a><p>0. <a href="https://docs.djangoproject.com/en/1.8/faq/general/" rel="nofollow">https://docs.djangoproject.com/en/1.8/faq/general/</a>