4 ms·
FWIW, I'd approach other FAANG with the same "get ready to be betrayed" attitude I have to MS as well. Try to entrust as little as possible into their hands, bu
by karamanolev 4y ago
FWIW, I'd approach other FAANG with the same "get ready to be betrayed" attitude I have to MS as well. Try to entrust as little as possible into their hands, but still do what's necessary to your business (i.e. don't be fanatical about it).
- metaltyphoon 4y agoAlright, then let's hear: What is your go to stack?
- tartoran 4y agoThe stack could still be one of these; it’s just a reminder that betrayal will come and maybe not put all eggs in one basket type of things.
- TheRealDunkirk 4y agoNot OP, but my favorite stack is Rails/Postgres/Linux. It doesn't get more open and less corporate-controlled than that these days. To enjoin OP, however, I get worried when I think about the GitHub acquisition. To me, GitHub was everything open and non-corporate, like my stack. Then Microsoft bought it, and now I fear that they will bring their MSDN "dev portal" schtick over to it. They've already started integrating LinkedIn into Outlook. They will probably be doing the same thing with GitHub in Visual Studio, and downplaying others (like GitLab). Will it affect my use? I don't know. I doubt it, but I wish I didn't feel like I need to be watching them like a hawk now, and be ready to move my code to another provider at short notice. The really stupid part? Out of other companies who could have bought it, and would be interested in it, Microsoft is probably the best choice. Certainly better than Oracle or Salesforce.
- karamanolev 4y agoNot sure it matters, but my go-to is Python/Django/nginx/Ubuntu Server (VMs). I like open things with a track record (no chancing the latest shiny thing) that have proven to work for small-to-mid scale and I can count on in terms of securing talent. None of that "3 years of experience" for a framework that is 1 year old. I also have no issues depending on corporate things that I don't like, for example GitHub, as long as they can be replaced with minimal loss. I'd git remote set-url origin <something else> and be done with it.