3 ms·
The backend was in Go, a language that I have no idea about. Also this was in Japan and backend discussions and 3rd party vendors all happened in Japanese, whic
by franciscop 4y ago
The backend was in Go, a language that I have no idea about. Also this was in Japan and backend discussions and 3rd party vendors all happened in Japanese, which I also didn't speak. I suggested learning Go myself and try to help, but my manager was also against it.
I was dubious I'd be of much help when I suggested but at least I'd learn the language we were using and might be able to help long-term. But as things kept getting delayed I'm sure I'd have been able to learn enough to be of help even within that project. But again, had a hard ban to either join a different project or learn/help with Go, "just keep improving the front-end and integrate it with the backend and don't do anything else until that's done".
- scary-size 4y agoThanks for the additional context. In your initial post it came across like you sat and watched the project burn.
- franciscop 4y agoSorry for my bad explanation/coming off as that, since it's definitely the opposite. I actually left the company because of the stress of wanting to help and not being able to help. Going everyday seeing how the project was going into the ground and being told I couldn't help and to just sit there destroyed my soul.
- IshKebab 4y agoYour manager sounds like a complete tool. Go is easier to learn than React IMO. Japanese not so much, but it sounds like you could have at least helped with the implementation without speaking it.
- Aloha 4y agoWorking with Japanese engineers without either speaking Japanese or being sufficiently acultured to Japanese cultural norms was an interesting experience for me. Brilliant fellows, with a very different way of thinking about issues. Often however the solution was dictated by things outside of the engineering problem at hand.