41–50 of 64 posts
I'm mostly waiting for something to more easily interact with the AST than pure text (like something more of a tree view).
Think more easily (that's the key) collapsing bits of code, dragging them around and deciding whether they're active.
“A typical organization in the 2020s has: Hundreds of microservices” Can people with expertise in this situation speak about how typical it is? I guess if you have all those services then you need your IDE to help - but surely this isn’t super common? If it is, what sort of size of micro service are we talking here? I’ve worked in orgs with 3M line codebases, and I’d struggle to find a hundred ways to partition the c…
Each team has developed it's own way to work with it's subset of services - I doubt every team across every org could figure out how to run everyone elses domains to even make checking out the world a useful exercise.
As a long term corporate exercise, maybe that would "be awesome", but not trivial to do and PAINFUL to support and stay on top of over time.
We had a hard enough time keeping test suites up to date - I can't imagine trying to keep our portfolio "runnable" for everyone else.
I do need to pair program remotely, and collaborate on design docs. Collaborative editing isn't like a 24/7 feature that you need to enable, and I don't know why the author thinks those are the reasons that they're valuable.
“A typical organization in the 2020s has: Hundreds of microservices” Can people with expertise in this situation speak about how typical it is? I guess if you have all those services then you need your IDE to help - but surely this isn’t super common? If it is, what sort of size of micro service are we talking here? I’ve worked in orgs with 3M line codebases, and I’d struggle to find a hundred ways to partition the c…
I switched from IntelliJ to Emacs about a year ago, and honestly these things seem relatively trivial in that environment, because I can write small ELisp functions that automate things like this without much effort or ceremony. For example it's quite easy to automate checking out repos, applying AST refactorings using LSP Mode, and then committing and sending PRs using VC/Magit. Or configuring projects and "Run Butt…
The available interface should be the same as what it is for plugins: https://plugins.jetbrains.com/docs/intellij/psi-cookbook.htm...
These should be useful imports:
* com.intellij.psi.JavaPsiFacade
* com.intellij.refactoring.RefactoringFactory
If someone knows better, happy to be educated on this!
https://www.jetbrains.com/help/idea/ide-scripting-console.ht...
My first time using IntelliJ was on trying to open a dozen microservices and discovering that I needed to mess with modules. Got back to Eclipse, especially because it already have the Launch Group feature to start multiple projects sequentially.
I think a great IDE is more UX intelligent and less UI heavy. I’m thinking like text editor that reads my mind and makes my bad code better
Its not hard to set up a multi-project view in Intellij. There are a lot of choices for build systems that will track cross repo builds. You can use something like Docker Compose (or several other options) to run many services locally.
Cross-repo refactoring (even worse: renaming) seems like an at best worthless and at worst quite costly thing to optimize your toolchain around. Having stable interfaces between systems is very important. The whole point of having separate systems is so you don't have to change one when you change the other. If that's not the case, you're better off with a monorepo.
Tools should help you do the right thing. They should not be a painful bludgeon against other devs. Enabling fast and easy end to end testing is only helpful.
I wonder, are some people writing (and sharing these things on HN), not to share some insight on some subject but to have something to point at during interviews?