I’m a software developer but a lot of the work is ambiguous and the instructions are lacking sometimes. My company puts no pressure on me and is amazing with my neuroticism and ADHD. Yet I can’t not wreck my mental state by worrying about things and thinking I’m not cut out for this. This issue is worst Mon-Tue and then gets better towards the weekend. It’s also dependent on the work load and client emails.
Also, crashed my mums car last night by not paying attention and rear ended someone. Then they tried to fight me cause I asked them to all stop screaming as nobody is hurt and it’s only material objects and I’m fully comp so they’ll be fine. Fucking cavemen. I’m not adverse to hitting someone, but it would have to be over something more serious than a minor accident.
How long are you working as a software dev? Basically a lot of new devs want to “save the world” by closing tickets and using that as a metric if they’re doing well or not. The reality is that a software dev’s job is just about as much writing, as dealing with clients, going to meetings, etc. People might value you for things that you don’t think have value. For the cut out for this part - you most likely are. Imposter syndrome is normal, I had it too, even 6 years into my career. Been the “goto guy” for the team, multiple times a teamlead at 3 different companies / teams. Never had a problem I couldn’t google away. Yet in the back of my mind, there was always a “maybe you’ll encounter one on the next ticket? And they’ll fire you for it” etc. I managed to silence that shit and bury it deep behind all of my achievements.
For the second part - some people are just idiots, some are governed by emotion, etc. Also, saying “it’s not so bad” is a shit way to deescalate the situation ^^
So my company is less ticket based and more here’s a spec for the whole application go ahead and build it kind of thing. My boss is amazing but he keeps a lot in his head and when I ask for help he doesn’t explain it in way that makes me understand or feel more confident. These issues do pass and they’re never as bad as I make them seem in my head at the time. Then we get emails from clients which we just action as and when. You’re right about it not just being about coding, as a lot of time is in client meetings, email writing and stuff like that.
I don’t know if glad is the right word for you having imposter syndrome, but I’m kinda relieved so many people say they experienced it too.
Yeah I’m an enigma as I’m incredibly socially adept at times, but then others I’m a fucking idiot. Especially, if I think people are overreacting as I’ll then try all the wrong things to get them to calm down. It was just strange that they were screaming and talking to me like shit and the second I’m like fuck this mate they wanna get physical, I’m not adverse to physical altercations but not over something so trivial (in my mind). Perhaps I should watch the way I say things.
Well, there you go - the issue is with the company and the irreplacable boss. He is the weakest link obviously. Imagine he gets into a car crash, gets hit by a bus. Suddenly all his knowledge is gone, either for a while when recovering, or forever. Knowledge transfer is incredibly important. Things like tickets, scrum, kanban etc are used because they work for every type of person - they serve to transfer knowledge, the hierarchy in a team protects the programmers from shit they shouldn’t be dealing with (that’s the project manager’s role, to be a shield for the team, to curate the the messages comming from “higher up” and the ones sent out by the team). The most important thing to know is that “do the needful” is about as shitty of an ask someone can pose to a programmer. People doing that don’t know what they want, and instead rely on what they don’t want - once you actually implement something that remotely fits what they needed. As for clients not reading specs - it might be time for someone to have “the talk” with them (obviously not you). One thing you need to know is that shitty clients can be fired too, once the development starts breaking down, the communication is arse etc.
For the people on the road - they probably took it as you trying to bail on them. But yeah, impulsivity when things are getting heated is never good, it’s better to stay silent for a few seconds and then say something, rather than immediately say something that can be taken very badly.
Oof… Yeah it is hard to deescalate with a person who is primally furious with you. It was probably really scary for them, and it sounds like they might not have been emotionally intelligent enough to handle it. I’m glad you and everyone are ok.
I’m also in software and, yes, depending on what kind of business you’re in people often have no idea what they want. Do you like reading? One thing that helped me in those situations is Don Norman’s book, the design of everyday things. It helps me get into a big picture mindset.
Yeah I agree they were just people not cut out to handle the stress of the accident and just got mad. It was my fault and I owned up to that instantly, I’m just more a chill guy as things could always be worse and no body was injured thankfully.
Thanks for the book recommendation I’m have a look for it.
Yes we are consultants and we write extensive spec that clearly the clients don’t read and then we have to go back and redo a lot of work as “it’s not what they want” but they can’t articulate what they want so you have to infer it and then when it’s wrong they’re like bruh. This is what I struggle with, the ambiguity of it all. I like to know what I’m doing and when, whereas this small company is incredibly chill and don’t expect a lot which I find hard as I’m used to being worked to death in crappy jobs and here it’s like the staff come first the code is second after we are all happy. I am blessed in that regard.
Let me follow up, that that lack of direction is also a great opportunity for you too. If they afford it, take your time and weigh different ideas, different technology stacks or different designs, try to get the costs together (development and maintenance), and make a presentation to them. But most importantly learn as much as you can in the process every time
I’m a software developer but a lot of the work is ambiguous and the instructions are lacking sometimes. My company puts no pressure on me and is amazing with my neuroticism and ADHD. Yet I can’t not wreck my mental state by worrying about things and thinking I’m not cut out for this. This issue is worst Mon-Tue and then gets better towards the weekend. It’s also dependent on the work load and client emails.
Also, crashed my mums car last night by not paying attention and rear ended someone. Then they tried to fight me cause I asked them to all stop screaming as nobody is hurt and it’s only material objects and I’m fully comp so they’ll be fine. Fucking cavemen. I’m not adverse to hitting someone, but it would have to be over something more serious than a minor accident.
How long are you working as a software dev? Basically a lot of new devs want to “save the world” by closing tickets and using that as a metric if they’re doing well or not. The reality is that a software dev’s job is just about as much writing, as dealing with clients, going to meetings, etc. People might value you for things that you don’t think have value. For the cut out for this part - you most likely are. Imposter syndrome is normal, I had it too, even 6 years into my career. Been the “goto guy” for the team, multiple times a teamlead at 3 different companies / teams. Never had a problem I couldn’t google away. Yet in the back of my mind, there was always a “maybe you’ll encounter one on the next ticket? And they’ll fire you for it” etc. I managed to silence that shit and bury it deep behind all of my achievements.
For the second part - some people are just idiots, some are governed by emotion, etc. Also, saying “it’s not so bad” is a shit way to deescalate the situation ^^
Only 18 months.
So my company is less ticket based and more here’s a spec for the whole application go ahead and build it kind of thing. My boss is amazing but he keeps a lot in his head and when I ask for help he doesn’t explain it in way that makes me understand or feel more confident. These issues do pass and they’re never as bad as I make them seem in my head at the time. Then we get emails from clients which we just action as and when. You’re right about it not just being about coding, as a lot of time is in client meetings, email writing and stuff like that.
I don’t know if glad is the right word for you having imposter syndrome, but I’m kinda relieved so many people say they experienced it too.
Yeah I’m an enigma as I’m incredibly socially adept at times, but then others I’m a fucking idiot. Especially, if I think people are overreacting as I’ll then try all the wrong things to get them to calm down. It was just strange that they were screaming and talking to me like shit and the second I’m like fuck this mate they wanna get physical, I’m not adverse to physical altercations but not over something so trivial (in my mind). Perhaps I should watch the way I say things.
Well, there you go - the issue is with the company and the irreplacable boss. He is the weakest link obviously. Imagine he gets into a car crash, gets hit by a bus. Suddenly all his knowledge is gone, either for a while when recovering, or forever. Knowledge transfer is incredibly important. Things like tickets, scrum, kanban etc are used because they work for every type of person - they serve to transfer knowledge, the hierarchy in a team protects the programmers from shit they shouldn’t be dealing with (that’s the project manager’s role, to be a shield for the team, to curate the the messages comming from “higher up” and the ones sent out by the team). The most important thing to know is that “do the needful” is about as shitty of an ask someone can pose to a programmer. People doing that don’t know what they want, and instead rely on what they don’t want - once you actually implement something that remotely fits what they needed. As for clients not reading specs - it might be time for someone to have “the talk” with them (obviously not you). One thing you need to know is that shitty clients can be fired too, once the development starts breaking down, the communication is arse etc.
For the people on the road - they probably took it as you trying to bail on them. But yeah, impulsivity when things are getting heated is never good, it’s better to stay silent for a few seconds and then say something, rather than immediately say something that can be taken very badly.
Oof… Yeah it is hard to deescalate with a person who is primally furious with you. It was probably really scary for them, and it sounds like they might not have been emotionally intelligent enough to handle it. I’m glad you and everyone are ok.
I’m also in software and, yes, depending on what kind of business you’re in people often have no idea what they want. Do you like reading? One thing that helped me in those situations is Don Norman’s book, the design of everyday things. It helps me get into a big picture mindset.
Thanks for the response.
Yeah I agree they were just people not cut out to handle the stress of the accident and just got mad. It was my fault and I owned up to that instantly, I’m just more a chill guy as things could always be worse and no body was injured thankfully.
Thanks for the book recommendation I’m have a look for it.
Yes we are consultants and we write extensive spec that clearly the clients don’t read and then we have to go back and redo a lot of work as “it’s not what they want” but they can’t articulate what they want so you have to infer it and then when it’s wrong they’re like bruh. This is what I struggle with, the ambiguity of it all. I like to know what I’m doing and when, whereas this small company is incredibly chill and don’t expect a lot which I find hard as I’m used to being worked to death in crappy jobs and here it’s like the staff come first the code is second after we are all happy. I am blessed in that regard.
Let me follow up, that that lack of direction is also a great opportunity for you too. If they afford it, take your time and weigh different ideas, different technology stacks or different designs, try to get the costs together (development and maintenance), and make a presentation to them. But most importantly learn as much as you can in the process every time