|
|
|
|
|
by binarytox1n
1917 days ago
|
|
One on one meetings are not "creepy" - they are a chance to have an open conversation about your goals; your concerns; and anything else that needs to be discussed about your career, the organization, etc. Do you know what the sales people in your organization do? What about the legal department? Procurement? HR? Your lack of knowledge is not evidence. "lol, do some coding instead"? And what should I code? How do you know what _you_ should be coding? Where does that work come from? Who makes sure that you're writing quality code and not some shit spaghetti mess? When the lawyers come knocking who answers the questions about security and compliance? You're just going to write some code for that? Your myopic complaints do nothing to further your own goals - rather than make baseless accusations, look into the problems yourself and try to solve them. You might get some career growth out of it. At the very least you'll understand that not all problems can be solved with code. |
|
Actually, who decides this, and how?
I mean, I understand why 1:1 are considered necessary, but I still get the creepy vibe. It's probably mostly my introversion speaking, but this is honestly how I feel about it.
> conversation about your goals; your concerns; and anything else that needs to be discussed about your career
What goals exactly? We do sprint planning every spring, plus all that backlog refinement and other stuff.
Long-term goals? Well, they don't change that often (that's what "long-term" means). Neither does my career. So having this kind of debate once or twice a year would be quite enough.