Code review habits in Kotlin projects
The community around Kotlin has changed a lot in the last few years.
The community around Kotlin has changed a lot in the last few years.
Whatever you pick, pick it soon. Waiting is the expensive part.
Small correction, but the point stands.
Start small and stay consistent. That's really all there is to it.
This deserves its own thread.
silver-hazel-65 wrote:
Start small and stay consistent.
Ha, I thought I was the only one.
Careful with that advice, it doesn't work for everyone.
That's fair. I hadn't looked at it that way.
Nothing beats doing it badly a few times.
Counterpoint: it depends a lot on how much time you have.
This is the most useful reply in the thread.
Have you tried asking in the local group too?
pale-birch-20 wrote:
Have you tried asking in the local group too?
Could you share a photo?
Second this.
Same experience here.
Whatever you pick, pick it soon. Waiting is the expensive part.
tidal-pine-1 wrote:
Whatever you pick, pick it soon.
Do you have a source for that? I'd like to read more.
woven-beech-91 wrote:
tidal-pine-1 wrote:
My experience was the opposite, oddly enough.
This is the most useful reply in the thread.
Whatever you pick, pick it soon. Waiting is the expensive part.
This deserves its own thread.
The cheap option was fine for years.
dusky-beech-27 wrote:
The cheap option was fine for years.
This is the most useful reply in the thread.
tidal-willow-17 wrote:
dusky-beech-27 wrote:
Strong disagree, but thanks for writing it up.
Thanks, exactly what I was looking for.
Thanks, exactly what I was looking for.
Agreed, and it takes a while before it clicks.
This is the most useful reply in the thread.
The official docs are better than they look.
Small correction, but the point stands.