this post was submitted on 01 Mar 2024
48 points (100.0% liked)

Programming

17512 readers
174 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
48
submitted 8 months ago* (last edited 8 months ago) by stembolts to c/programming
 

Edit : I appreciate all the PoVs and I will reply to everyone. This is important to me. Just going to go rest a bit and I'll be back.

Edit : Leaving the self-insulting language in, but yeah.. Point taken, I should stop being so mean to myself. And to add another FYI, I've been on this codebase for about 3 months, which I probably should have mentioned.

I have no idea what is wrong with me. I get tasks, I work on them, they NEVER seem to close. Meanwhile everyone around me is left and right solving their issues. I reach out for a second opinion because I must just be stupid, and every time I reach out the person is never able to assist in any meaningful way.

It's like my tasks always have blockers that everyone around me seems perplexed by, I get a lot of, "Wow, that's crazy," or, "Yeah your job does seem to have a lot of unusual blockers."

I'm at the point where I'm in a daily meeting where I explain what I'm working on to a senior dev because obviously they noticed I'm a person on the team with sometimes zero points in a whole month. It's so discouraging to have to go to a daily meeting because apparently I'm stupid? The thing is, when I explain what I'm blocked by, every person has said, "Oh weird, this seems like a really confusing task." Or, "Damn I've never seen anything like that."

So obviously I look at other peoples' tasks.. what are they working on? And their tasks are SO simple and straightforward, yet I've NEVER had a task like that, all my tasks were opened years ago, remained open for months or years, then were assigned to me. And they're all fucky. Wth.

Tbh I'm running out of things to write because I don't want to justify it, because I feel like I should be doing better. What the hell is wrong with me?

I have wanted to change jobs for close to two years now.. but you've all interacted with recruiters.. they never help, and job search is impossible as a person with anxiety and possibly autism?

I love coding, I hate my coding environment.. Anyone else ever have this type of issue in programming?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 15 points 8 months ago (1 children)

It's already been said a couple times but if your more experienced team members are saying, "that's a really weird task" the issue is probably the task not you.

Having daily meetings with a senior because you're having a lot of trouble progressing isn't necessarily a bad thing. Everyone has jobs that are absolute ordeals and sometimes it's better to break them down even further and just go one step at a time.

Also, are you involved in your team sprint planning? Who says "this ticket is a 1 day job" that should be your teammates, or at least a subset of them? Why did they decide this was an easy task? What did they, or you, miss in the execution?

[โ€“] stembolts 2 points 8 months ago

Alright, I never thought about the daily meetings like that, probably because of the context with which they started. It started because the guy who manages the points doesn't develop or understand software, he just reports progress of the team via points to the contract-host-company (we're all contractors on my team).

I'm not involved in any planning, I just get assigned stuff. As far as estimating how large the bugs are, that would be me, but I've only arrived working on this new code base three months ago so my estimates would be random guesses since I don't understand the larger context of any of the jobs, nor how the moving parts fit together. So what I do is take a job, then just add two points every day, one of my tasks is well over thirty points at this time.

I'm not sure how task difficulty is determined or if it is at all? It seems to be more that they chose these bugs just because they make sense for a new team member to get working on something, but that's just a guess.