4 ms·

Easy... choose Node and put the Python engineer in charge or choose Python and put the Node guy in charge. Or redo the whole thing in Go.

munin 11y ago
There is definitely some degree of executive decision their management could make but it would shred one of the two leads careers. This kind of hard call is why you're boss, so it says something about someone when they don't make this call (although we don't know the full story here, this situation happens enough in general). The post I was replying to was asking why an individual lead engineer in this scenario would do this. They have reasons to fight and no reason to concede. Their bosses have every reason to, at minimum, get both sides to "hug it out" so why haven't they?
thedevopsguy 11y ago
Or move everything to a microservices architecture and use the best suited language for each subsystem. It would force both camps to engineer for composability and open service apis. My tupence.
- rco8786 11y ago
  I assure you that Uber is built using "micro services". That doesn't mean there isn't value in having some language uniformity in the org and it doesn't solve the language preference between people problem.
- gansai 11y ago
  Looks like Uber has moved to a microservices architecture. Check their engineering blog: (https://eng.uber.com/soa/ https://eng.uber.com/soa/)
  - thedevopsguy 11y ago
    Wasn't aware of their move. A microservices architecture then makes the technical conversation about the service, it's latency, performance rather than implementation details. Is it such a bad thing to have many different languages in play as long as the SLAs are met?
- deleted 11y ago
  [deleted]
brobinson 11y ago
I have a friend in SF who works at Uber and writes Go there. He said they're using it for a lot of things internally.
threeseed 11y ago
If you are choosing a whole new language why not one of the JVM ones. It is faster and more scalable than Go plus it has a usable debugger.

munin 11y ago

There is definitely some degree of executive decision their management could make but it would shred one of the two leads careers. This kind of hard call is why you're boss, so it says something about someone when they don't make this call (although we don't know the full story here, this situation happens enough in general). The post I was replying to was asking why an individual lead engineer in this scenario would do this. They have reasons to fight and no reason to concede. Their bosses have every reason to, at minimum, get both sides to "hug it out" so why haven't they?

thedevopsguy 11y ago

Or move everything to a microservices architecture and use the best suited language for each subsystem. It would force both camps to engineer for composability and open service apis. My tupence.

rco8786 11y ago
I assure you that Uber is built using "micro services". That doesn't mean there isn't value in having some language uniformity in the org and it doesn't solve the language preference between people problem.
gansai 11y ago
Looks like Uber has moved to a microservices architecture. Check their engineering blog: (https://eng.uber.com/soa/ https://eng.uber.com/soa/)
- thedevopsguy 11y ago
  Wasn't aware of their move. A microservices architecture then makes the technical conversation about the service, it's latency, performance rather than implementation details. Is it such a bad thing to have many different languages in play as long as the SLAs are met?
deleted 11y ago
[deleted]

brobinson 11y ago

I have a friend in SF who works at Uber and writes Go there. He said they're using it for a lot of things internally.

threeseed 11y ago

If you are choosing a whole new language why not one of the JVM ones. It is faster and more scalable than Go plus it has a usable debugger.