4 ms·
I don't want to be mean but he wasn't a good cultural fit if he complained about that and should've been let go. That seems a very rash assumption with so litt
by Silhouette 11y ago
I don't want to be mean but he wasn't a good cultural fit if he complained about that and should've been let go.
That seems a very rash assumption with so little information.
Maybe the developer in question needs other software to do their job and some of that software only runs on a certain OS.
Maybe the advantages of having the right person on the team and able to use their preferred dev tools are a big overall win for the project.
Maybe running into portability issues with such a fundamental tool is a warning sign that the build process isn't as robust as it could be.
Maybe the whole thing can be fixed with a ten minute discussion and two-line edit to the makefile, and then you have the option of bringing other developers who prefer the same platform onto the team later as well.
Successful companies and products are built by like-minded people.
If you'd said something like "compatible", I might have agreed with you, but I see little evidence that complete enforced uniformity is necessarily a win in a field like software development. This sounds a lot like the kinds of managers who want to reduce everyone on a development team to interchangeable commodities, ignoring the inevitable reality that everyone's background and ability to contribute will be different. It also sounds a lot like the kinds of development teams that can spend weeks going down a dead-end path because no-one had enough varied experience that they anticipated the problem and thought to question the direction the project was going.
- eropple 11y ago> Maybe the developer in question needs other software to do their job and some of that software only runs on a certain OS. This can't be understated. How about, say, accessibility software? There's a reason that, say, visually impaired developers very often use Windows: because the accessibility tools are really, really good. But, naturally, it's just not understanding the beauty of Unix. Ick.
- Silhouette 11y agoYes, if we're talking about web development here, there are loads of practical examples. Testing and debugging with browsers only available on certain platforms obviously requires that platform, and sometimes an emulation or VM version isn't close enough. Graphics software is frequently platform-specific, so if you have a front-end developer who also deals with logos, icons, animations, or any number of other graphical assets, they probably need a compatible system. Plenty of conference calling and desktop sharing tools are platform-specific, and you need to be using the same as whatever your clients or external collaborators use. The list goes on, but certainly for the three big areas I just mentioned Linux platforms are often far behind both Windows and OS X in what is available.
- mwcampbell 11y agoFWIW, of the dozen or so blind programmers that I know, the majority use Windows, but a few use OS X, and one uses GNU/Linux on the desktop (Fedora, running GNOME and the Orca screen reader). So all three OS's are usable for a blind programmer. A bigger problem would be insisting that everyone use the same IDE, if that IDE isn't accessible (like, say, the JetBrains family AFAIK).
- eropple 11y agoI didn't say the others didn't have usable tools. But the investment in Windows's is significant and it shows.