1. Modify your codebase to use microservices
2. Modify your IDE habits to be more REPL friendly
3. Modify your team coding habits even if it makes it hard for one person to work on the other person's codebase.
1. Modify your codebase to use microservices
2. Modify your IDE habits to be more REPL friendly
3. Modify your team coding habits even if it makes it hard for one person to work on the other person's codebase.
>2. Modify your IDE habits to be more REPL friendly
Plenty of people use IDEs, I just think if that's what your main sticking point when picking a language, go with C#. It has the best IDE of any language.
>3. Modify your team coding habits even if it makes it hard for one person to work on the other person's codebase.
Nope, not a problem. I can work on any code base in the company. It's spooky how fast we can jump into others teams projects and contribute, and a lot of that is due to the power of the language.
GF mentioned microservices because they end up forcing this by design, but nowhere does it say "you must use microservices or else get horrible compile times"