Readit NewsPaying people "fairly" seems to mean "years of experience" multiplied by some factors based on the individual.
This means a talented junior gets screwed and leaves, and the one year twenty times over crowd stay forever.
I went through a pay review where I was apparently too far up the curve for my age and that wasn't fair, so I got less than my colleagues that round. That's a conversation you only get to have with an engineer once.
I’m the author. I would never advocate for pay levels to be based on years of experience personally.
jaderubick commented on Great engineering teams focus on milestones instead of projects rubick.com/milestones-not... · Posted by u/tyroh
If we stick to strict Project Management definitions, milestones are within a project.
A program (representing a strategic goal) can contain multiple projects big and small. Perhaps the author wants to convey programs which map to company or divisions strategic initiatives.
I’m the author. No, not intending programs. Milestones are smaller than projects in my definition.
jaderubick commented on Great engineering teams focus on milestones instead of projects rubick.com/milestones-not... · Posted by u/tyroh
I ignore so many of these nonsensical articles on here, but this one really got my goat. Is there someone out there that works on "projects" where the goals of the project are not delivering milestones? I'm probably just lost in the generic management babble.
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.
jaderubick commented on Great engineering teams focus on milestones instead of projects rubick.com/milestones-not... · Posted by u/tyroh
Think of driving from point A to point B. A project is completing the journey. A milestone is like a major stopping point or identifying landmark that is unique and distinct. A mile marker is like a sprint story.
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.
jaderubick commented on Infobits: A tool for situational awareness on teams rubick.com/infobits-for-i... · Posted by u/jaderubick
Perhaps a better title is: how to share nuggets of info with the people around you to help everyone work better together?
jaderubick commented on Bundled hiring to double the effectiveness of your hiring process rubick.com/bundled-hiring... · Posted by u/mooreds
Am I missing something, or is that just a lot of words just to say "let's save some money by combining two positions into one"?
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.
jaderubick commented on Everyone Lies to Tech Leaders rubick.com/everyone-lies-... · Posted by u/jaderubick
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?
Still it missed “how should I fire new junior engineers”