3 ms·
Where I work, I was just assigned a project to add functionality to. The README instructions for the project started thus: 1) Download Visual Studio Code from
by bitwize 5y ago
Where I work, I was just assigned a project to add functionality to. The README instructions for the project started thus:
1) Download Visual Studio Code from https://code.visualstudio.com https://code.visualstudio.com.
2) Clone the repository from BitBucket at <blah>.
3) Download Kafka and Zookeeper, and follow such-and-such directions to run them.
4) Make configuration changes <foo>, <bar>, and <blatz> to connect to the
nonprod Mongo database.
5) To run the program, right-click on Application.java in VSCode and then click on Run.
6) To run unit tests, right-click on their names in VSCode and click on Run Unit Test.
The real world is just like the university! IDEs are how you engage with the program in the enterprise -- and you'd better be using the same one that the original author used because if something goes wrong, you're not going to be able to find someone who can fix it without that particular IDE.
This idea that software should build and run with just the compiler and simple, scriptable build tools is a quirk of open-source development and distribution practice from the 90s and it does not generalize. In the real world, if it can't be done from the IDE it generally can't be done. I know, I know, CI/CD -- but that's generally provided by templates from the corporate CI/CD team and the average line programmer need never touch it, nor know how it works. You may think this is a totally clownshoes way to handle software, and you may be right. But billion-dollar companies run on software handled this way -- and worse ways! -- and you're not going to be able to change it. This stuff was written by tired programmers who just want to play with their kids after putting in their 9-5. You need to budget for these kinds of changes during work hours if you want them done -- and knowing how to operate javac, and structuring your software so that it can be edited, compiled, and run with any tools that are up to the job, do not deliver value to the customer and will not be budgeted for.
- vincnetas 5y agowhere i work most projects are IDE agnostic. Clone repo, cd to folder and "gradle build". In this case person can choose whatever ide he likes, or just use command line tools.
- denton-scratch 5y ago> but that's generally provided by templates from the corporate CI/CD team That's rather a "corporate" perspective. And having to rely on corporate infrastructure, build-teams and so on results in a mushroom outlook, in my experience, which I found depressing and disempowering. In most modern non-corporate development work, you are the CI/CD team.