IDE's (integrated development environments) have been optional, a secret tool that made you vastly more productive, but now it's become required, for security engineering. I mention this because people still wrongly use 'vim' or 'nano' to edit code.
A say 'secret tool' because most programmers don't use IDEs because of the overhead. They take a lot of learning/training before you can use them, and it's a lot of work to create a "project" before you start editing code.
But once you overcome that hurdle, the payoffs are enormous. Instead of using print statements to debug code, you use a source-level debugger that allows you to examine values. A debugger is no longer something used as a last resort, but something you use just to watch code run.
Let's talk about Apple's XCode for a moment. It's not simply based around compiling the code to produce the end-product, but about building all the unit/regression tests, profile tests, and security tests, and running those.
For example, with a few clicks of a button, I can create a "scheme" to run the "address sanitizer". 
To demonstrate this, I changed my memory allocation statement to allocate 1 fewer bytes for a buffer, to trigger a buffer overflow, as you see in the lower-right where the address sanitizer has detected the overflow and halted the program.
In the upper middle I see the line of offending code.
In the lower middle I see the values of variables, inspecting them without print statements.
In the left I see the call stack, where this event happened relative to the execution of the code.
In the lower middle I see the values of variables, inspecting them without print statements.
In the left I see the call stack, where this event happened relative to the execution of the code.
For "cybersecurity", we have a lot of tasks we need to perform above and beyond simply editing code. Engineers from Apple and Microsoft spend a lot of time doing these tasks. Therefore, their IDEs are designed to simplify those tasks.
