0% written by AI.

I’m the author. I would never advocate for pay levels to be based on years of experience personally.

I’m the author. No, not intending programs. Milestones are smaller than projects in my definition.

I’m the author. Most teams don’t work in this way in my experience. The key is how “milestone” is defined in the article.

A milestone == a mile marker. That is where the term came from.

https://en.m.wikipedia.org/wiki/Milestone

I think the term is rather unimportant. You could also use the term epic.

Perhaps a better title is: how to share nuggets of info with the people around you to help everyone work better together?

You’re missing something. Metaphorically it is like the difference between having a long lived process that services web requests and spinning up your whole environment per request.

Nuts and bolts of how the division was organized during its most rapid growth period.

That seems better to me! Thanks for the feedback.

Also. "If we do this, what kind of problems to you foresee that we might need to watch out for?" Because every solution creates or exposes new problems, but that's not a reason to do nothing.

Do you mind if I incorporate these into the blog post and mention you in the thank you?

Please be my guest. No ACK needed.

"I'm telling you, Molotov cocktails work! Anytime I had a problem and I threw a Molotov cocktail, boom! Right away, I had a different problem." - Jason Mendoza, The Good Place

Team communication suffers from the same challenges as serialization and deserialization.