Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
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.