maybe just because we don't want things to happen behind the curtains. As a personal preference, I don't want magic buttons that builds if they weren't crafted by me. At least, all that automation must not be hidden or obfuscated around IDE options.
Also, IDE tends to do things like they do things. This is, you probably will have a lot of troubles to run the project in another IDE/configuration. That's why I prefer things to be done by portable scripts so people can run/debug the project with as little as dependency as possible.
Another key thing is this: ask a developer who has used any IDE for life to put the build project in an automated pipeline... then, maybe you will have the answer why we shouldn't use any IDE.
Another key thing is this: ask a developer who has used any IDE for life to put the build project in an automated pipeline... then, maybe you will have the answer why we shouldn't use any IDE.
Interesting you should say that.
I have been using build tools manually for a decade and then switched to IDE. Of course, I still can setup automated pipelines (as I often do) because of that. The IDEs that I use just streamlined the things I already know how to do and have done magnitudes of times.
I think that the morale of this is that less experienced developers need to learn the basics first before they are allowed to use power-tools that hide all the details and foundations from them.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
maybe just because we don't want things to happen behind the curtains. As a personal preference, I don't want magic buttons that builds if they weren't crafted by me. At least, all that automation must not be hidden or obfuscated around IDE options.
Also, IDE tends to do things like they do things. This is, you probably will have a lot of troubles to run the project in another IDE/configuration. That's why I prefer things to be done by portable scripts so people can run/debug the project with as little as dependency as possible.
Another key thing is this: ask a developer who has used any IDE for life to put the build project in an automated pipeline... then, maybe you will have the answer why we shouldn't use any IDE.
Interesting you should say that.
I have been using build tools manually for a decade and then switched to IDE. Of course, I still can setup automated pipelines (as I often do) because of that. The IDEs that I use just streamlined the things I already know how to do and have done magnitudes of times.
I think that the morale of this is that less experienced developers need to learn the basics first before they are allowed to use power-tools that hide all the details and foundations from them.