181–186 of 186 posts
Earlier quoted context omitted.
> Time tracking by the hour... How is that a difficult idea to get around? As a contractor I'm expected to keep track of my hours and what I'm working on. Lucky it's just a chrome extension that I click to start and click to stop. Boom, tracking by hour of what I work on.
Which chrome extension would that be?
I think it is a little bit of exaggeration to claim Senior Developer title on a project with unfamiliar tech stack.
I think it is a little bit of exaggeration to claim Senior Developer title on a project with unfamiliar tech stack.
To the contrary, I'd say the ability to pick up a product in an unfamiliar tech stack and be productive relatively quickly is one factor that would make you more deserving of the "senior" qualification.
When you say "be productive," whose judgement will be making that assessment? I ask because if you were hired to come in and right the ship, writing tests might not be perceived by your manager as the right thing to do. If you need to impress the other developers, that might or might not be the right choice. If you are trying to communicate progress upward, then I would make an honest assessment of the challenges and…
As always, it depends on the context. Do you know why you were hired? You mentioned "10 devs, QA, BA" .. maybe a good chance to talk to everyone and write down and later agree on a roles & responsibilities matrix. Same goes with process. Talk to everyone and find out what they actually do, write it down and then have an objective discussion if all this is still the best way of doing things / working together. As for…
I have started having conversations with people on their experience, expectations etc. I am new to the stack but aware of what it is. The team is ramping up and certainly know more about it than me.
The links are very helpful, thanks.
I think it is a little bit of exaggeration to claim Senior Developer title on a project with unfamiliar tech stack.
Every place has its own names for things, but I often see "senior" refer to your interchangeable seniority in the field, not just in the one company/code base. Then for people to grow into "lead" or "principal".
It might be that I read the question wrong. OP says that the tech stack is unfamiliar, and I guess it comes down on whether they've been familiar with a similar tech stack or something is architecturely different.