As a conputer engineering student, you will be learning how to learn how to compose a problem report or compose a technical question.
Rule of thumb for app-related questions is specific hardware involved, and the operating system and app versions involved, minimally.
If the school is a good one, you will be responding to bug reports and pull requests and related within your own apps or within open source apps you might be contributing to, which will give you direct insight into what arriving information is important and in what context for receiving and remediating the reported issues.
Here, useful information includes which apps, and what platforms are those apps available for. You’ll certainly see Windows used, but likely also macOS and Linux, and potentially other platforms. Different apps have different requirements, as do different operating system platforms.
With Apple Mac, the previous-generation Mac systems use Intel x86-64 architecture processors and hardware, while current and newer systems use Apple silicon processors based on ARMv8 AArch64 architecture. You’ll probably also see RISC-V architecture and processors, and potentially others.
Here, which architecture is key to your question, as that will determine what else is possible with this Mac, and how.
Linux and Windows are available using various means for Mac with Intel x86-64 processors. Windows can boot on an Intel Mac using either Boot Camp—Boot Camp is an Apple package that presents the hardware abstraction layer expected by Windows, making an Intel Mac look like a Windows-compliant PC—or through an add-on hardware virtualization package such as Parallels, VirtualBox, or VMware Fusion.
Virtual machines are also sometimes known as hypervisors. Virtual machines or hypervisors virtualize the hardware. (Virtualization of memory, of system hardware, of networking, and of storage, is a key concept in modern computing, and something you will likely learn much more about.)
For direct booting, Linux is just becoming possible on Mac with Apple silicon processors, and Microsoft Windows is available to insiders but is not (yet?) a purchasable and supported product.
Virtual machines mostly work fine, though will require a fair amount of storage for each “guest” of the virtual machine, and also a fair amount of system memory while the vierual machine and operating system “guest” is running. Virtual machines are same-architecture choices, meaning an operating system built for x86-64 hardware will (usually) work as a “guest” on another x86-64 system using a virtual machine. Using an operating system built for x86-64 hardware on an ARMv8 AArch64 hardware will require emulation in addition to virtualization. One such virtual machine with hardware emulation support available for Mac is UTM.
All that out of the way, the key detail here is which platform the necessary apps require. That dictates which operating systems and which architectures, which then leads ro which other options and alternatives are available. Pretty much everything here is driven off the apps involved, and then the associated and app-specific dependencies.
IT is ever-increasing and ever-shifting stacks of abstractions and dependencies, as you’ll come to learn more about.
TL;DR: which apps? What are the operating system and processor dependencies for each app? Then for whether and what configuration might be used to run the apps, which Mac and which macOS version, and which Mac processor architecture?