> Their argument is that all team members should use the same tools, and I guess that is a valid point.

Why is that a valid point?

In my case, I am a very senior member of my team so 25-50% of each day is spent helping and/or teaching teammates. In situations like that, it is useful to be deeply familiar with the tools that your teammates are using so you can tell them exactly what to do.

For example, if I'm teaching a new hire to set up their vscode it is not very helpful to tell them "now you need to activate the python venv". It is much more helpful to be able to tell them "Now we're going to activate the python venv. To do that, open your command palette and search for 'select python interpreter'".

In my personal life, I still exclusively use emacs (which I have scripted to auto-detect venvs) but I put up with using vscode at work to be a greater utility to my team.

▲

tvink 2 hours ago | parent | next [-]

Idunno. I think you end up teaching them nothing and just doing it for them. I mentor plenty folks without learning more than basics of vscode/cursor, and the most important lesson for them is always how to figure out how to do stuff (which has never been easier than today).

	▲	wtetzner an hour ago \| parent [-]
		Yeah, I kinda feel like when you're mentoring people, you should let them drive. If you're going to do it for them, you might as well just record a training video.

▲

shakow 4 hours ago | parent | prev [-]

At some point, shouldn't installing a venv be a pre-requisite to actually be hired as a dev?

	▲	kleiba2 4 hours ago \| parent \| next [-]
		That was just an example. The point of the parent is that in an ideal situation, where everything works without flaw, theoretically it makes no difference which tools everyone uses. In real life, you having a homogeneous setup across a team makes the sysadmin's job a lot easier.
	▲	4 hours ago \| parent \| prev [-]
		[deleted]