Tools you’d miss if you left a company

Re:Tools you’d miss if you left a company by bgdnyxbjx on Sunday February 09, 2020 @02:01AM (#22280814)

This topic is one of the primary reasons I enjoy working at MS these days.

The tech stack is full of OSS or industry standard tools, not a bunch of internal NIH things.

My current stack is: React, Node, Kubernetes, Linux (for dev and deploy), Git for sc, GitHub, vs code.

I can’t even think of some internal tool that I depend on at the moment.

[ Parent | on HN ]

Re:Tools you’d miss if you left a company by ddlutz on Sunday February 09, 2020 @03:48AM (#22281108)

That depends entirely on what part of MS you are in right? There is cosmos (internal, not exactly the same as external cosmos), autopilot for infra, mdm for metrics, mds for logs, icm for alerts, etc.

[ Parent | on HN ]

Re:Tools you’d miss if you left a company by bgdnyxbjx on Sunday February 09, 2020 @09:24AM (#22282227)

Yeh, you’re right. I was thinking more of this and remember all the alerting and incident management stuff. Then I realized that I hate those tools and would happily leave them behind :)

[ Parent | on HN ]

Re:Tools you’d miss if you left a company by zepolen on Sunday February 09, 2020 @05:14AM (#22281364)

Github is open source?

[ Parent | on HN ]

Re:Tools you’d miss if you left a company by cnst on Sunday February 09, 2020 @11:12PM (#22286383)

Like it or, GitHub is ubiquitous enough that noone really cares. If you do care, there's plenty of OSS alternatives that aren't much different in their UI than GitHub itself.

You can easily put GitHub on your resume, and everyone would know what you're talking about. Of course, by itself, it's not much of an experience, but, surprisingly, it is often listed as a requirement and/or nice-to-have for certain SWE job posts.

[ Parent | on HN ]