Re:Uber's technology is reportedly 'hanging by a thread'
by ericfrederich on Wednesday September 30, 2015 @08:19AM
(#10303339)
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.
Re:Uber's technology is reportedly 'hanging by a thread'
by munin on Wednesday September 30, 2015 @08:23AM
(#10303360)
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?
Re:Uber's technology is reportedly 'hanging by a thread'
by thedevopsguy on Wednesday September 30, 2015 @08:29AM
(#10303389)
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.
Re:Uber's technology is reportedly 'hanging by a thread'
by rco8786 on Wednesday September 30, 2015 @08:58AM
(#10303539)
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.
Re:Uber's technology is reportedly 'hanging by a thread'
by gansai on Wednesday September 30, 2015 @09:03AM
(#10303561)
Looks like Uber has moved to a microservices architecture. Check their engineering blog: (https://eng.uber.com/soa/)
Re:Uber's technology is reportedly 'hanging by a thread'
by thedevopsguy on Wednesday September 30, 2015 @10:11AM
(#10304063)
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?
It would be, if you lose. If you win, you are rich beyond the dreams of avarice. It would also be a career ending move to admit that your system is less than the other system and everyone will remember you as that loser whose system was done better by the current VP of engineering.