2 ms·
I regularly consult for teams, so I guess that's similar. The big thing going is that it could take a very long time to learn to build something. Even for senio
by muzani 6y ago
I regularly consult for teams, so I guess that's similar. The big thing going is that it could take a very long time to learn to build something. Even for seniors, it can be a week or more, if there was no focus on onboarding.
However, it's always been very useful. Normally you hear of 'buzzwords' - kotlin, reactive, functional, dependency injection, architectures, all these things, but tutorials give you little to nothing. But once they're used in a project, the value (and downsides) are immediately clear.
It's also useful to learn some things, like how the caching works, why this thing is a bottleneck. Or some habits, like one person has their set of tools and configs which turned out to be really powerful.