3 ms·
One data point but I have a ".NET background", primarily write "Enterprise software" in Windows stacks, but although I have a Windows Amazon Workspace at my dis
by vector_spaces 7y ago
One data point but I have a ".NET background", primarily write "Enterprise software" in Windows stacks, but although I have a Windows Amazon Workspace at my disposal my daily drivers are Linux and Emacs.
That said I haven't really observed this phenomenon among any of my coworkers who run on Visual Studio and Windows full time. I think experienced devs who care about their craft enough to know a modicum of computer science understand what is happening "under the hood" when tooling like Visual Studio abstracts build steps away from them, or at least enough to be able to manually replicate it themselves if needed.
- dkhenry 7y agoI don't want to contest your personal experience, however I find it very hard to believe you could work in an enterprise environment and not know people like the one's I have described. I have met these kinds of people at all the FAANG companies as well as every single software development firm I have worked with.
- vector_spaces 7y agoI have known people like this, but my point (poorly articulated) is that I don't think these biases against enterprise devs who happen to have experience with a particular toolchain are appropriate, since not all enterprise devs are like this, and, as others have mentioned, they aren't unique to developers with experience in those technologies -- for example, I've run into this issue pretty much exclusively with folks on the data side (not in the company I work for) using Python via Jupyter Notebooks and R via RStudio. Anyway -- I think it's fairly straightforward to filter these kinds of people out of your pool without going the nuclear option?