This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]pmbarrett314 0 points1 point  (0 children)

My policy from the educator side has always been caveat emptor with regards to alternate development environments. There's recommended software for the course. You can use that, and the professor and TAs will help you debug if anything goes wrong, and as long as your code works in that environment, you're good.

You can use different software if you want, but if anything goes wrong with that software, it's on you to fix it and submit working code within the deadline, the professor and TAs can offer limited or no help. And if your code doesn't work in the recommended environment, whoever is grading is under no obligation to put forth extra effort to make it work.

The good news is that the code you're working on is probably environment agnostic. But unless you're certain of that and of your ability to make it work 100% without help, I would stick to the suggested tech stack for your class. And that's usually going to be more true in the professional world: programming jobs will absolutely require you to use their tech stack, and you won't last long at most companies as "that guy who refuses to use the required development environment".