News for hackers. Stuff that matters.

A comment on Why we ditched Django for Microservices. Parent comment

Re:Why we ditched Django for Microservices by tmwatson100 on Monday January 12, 2015 @09:24AM (#8873968)
I perhaps should have explained that a bit more. Technology choices have to make sense before implemented but giving developers the flexibility opens a lot of doors for creativity and exploration.

I strongly believe that learning new languages help people become better coders overall as it increases their knowledge of different problems and solutions which can be applied across most stacks.

Also no one developer should ever be solely responsible for a particular service. But that should also be the case for apps within a Django project.

[ Parent | on HN ]
Re:Why we ditched Django for Microservices by bsdpython on Monday January 12, 2015 @09:39AM (#8874053)
As a business if you want to encourage your developers to improve by exposing them to more different types of languages and technologies then I am all for it. You can fund a weekly Haskell class. You can implement a 20% time initiative and let developers work on prototypes using whatever tech they want. For your production systems, however, you need to have some boundaries to serve the business even if you are a tech company run by engineers.
[ Parent | on HN ]