Im a bit anxious and introverted and thus like to get my part done and focus on other things.
This always results in rest of the team losing will to go far and beyond.
I dont know what to do about it, beside aknowledging it exists.
Do you say that ppl like me should simply quit and go working at sewege?
I dont think I like that idea. So what can I do if thats just how I am ? I cant seem to change how others see ppl like me.
1. "The extent to which you publicly complain about something should be proportional to the robustness of your solution and your confidence in it."
2. If you think things need to be done better, lead by example. I've found that you will be hated for saying things are bad, but loved for proving how things can be good (by example).
3. Note down your concerns (Notion is free!). Wait on them, then talk about them >=1 day later if you still feel like they are valid.
4. Ensure you have enough employable skills on the side so that you can jump ship if the company or your place within it is totally DOA.
Unfortunately Im not a rockstar engineer and stuff takes me more time. I care a lot about maintainability, so writing docs or good explanations to design decisions simply take time.
As you can guess we often dont have that time in the industry thus most things look like they look.
My biggest issue right now is communicating those findings.
Curse of things seeming too obvious, trivial or simply requiring more time.
To me, a problem engineer is someone who blocks the discussion, or that any solution needs to fit the specs of what the problem engineer wants, even before anyone has outlined what the issues are. Basically someone everyone walks on eggshells around. Anyone who breaks collaboration, team work, and especially anyone who ignores good engineering practices just because that makes that specific person happy... Is a problem.. for all the engineers.
You take a little extra time, that's fine. You're taking that time to do good documentation, or writing higher quality code.. you're an engineer, that's what I expect. Higher quality code and better documentation helps boost velocity in so many ways. You're doing yourself, and everyone around you a good service.
Don't beat yourself up.
> This always results in rest of the team losing will to go far and beyond.
The logic chain here is not very clear, I'm wondering if you actually understand what's going on.
If it's unexplainable, or the majority doesn't accept it, move on: change your ways or accept they are going to see you as such.
Most things are not written in stone. You can probably change even if it's not comfortable to do so. Maybe a different role or organization would be a better fit. But typically just getting your part done and moving on isn't the best fit for a lot of jobs and, even if you work for yourself, you probably even have more interactions with clients at that point.