3 ms·

> There were several factors to account for that scenario including fragility of the software product, fragility of the work requirements, challenge communicati

> There were several factors to account for that scenario including fragility of the software product, fragility of the work requirements, challenge communicating tasks, and so forth. This definitely plays into why I'm feeling overwhelmed. I get these big projects assigned to me with zero clarity on what exactly needs to be built. I reach out to the people who'll use it and not even they know what they want, they just want "something." It's very hard for me to make progress on things because all our infra is managed by an operations team, so anything I want to explore needs to be done by "human proxy". Communication is a huge issue for me as I'm in the spectrum. How I wish neurodiversity was as recognized and catered to as gender and racial diversity! There is virtually zero empathy for those of us that are quite challenged when it comes to dealing with other people who are not immediate team members who we've gotten used to. Are you in the US armed forces? I have considered enlisting and not trying to move up the ranks as a way to basically give up my life for a bit and be ordered around without having to make big decisions.

austincheney 6y ago
I work as both a senior developer for a large corporation and am in the US military. Right now I am temporarily just military. As for communication spend some time with your QA people. In my past employment the people who really mastered precision are always the QA. The clarity and detail they dive into with their written word is nothing short of astonishing compared to what many developers produce. If you want to depth of detail that goes into communicating a well written plan spend some time with a good PMP certified project manager. To produce better communication about product direction/features you need a huge level of empathy for your users. The end user generally knows what they want intuitively but often cannot communicate that into a feature request. You need to watch how they use your product see where they struggle and repeat steps. Again this is far different than what many developers communicate. Many developers communicate what makes things easier for themselves, the developer, without ever considering the impact to the user and is then completely inept at communicating the difference, which is incredibly frustrating.

austincheney 6y ago

I work as both a senior developer for a large corporation and am in the US military. Right now I am temporarily just military. As for communication spend some time with your QA people. In my past employment the people who really mastered precision are always the QA. The clarity and detail they dive into with their written word is nothing short of astonishing compared to what many developers produce. If you want to depth of detail that goes into communicating a well written plan spend some time with a good PMP certified project manager. To produce better communication about product direction/features you need a huge level of empathy for your users. The end user generally knows what they want intuitively but often cannot communicate that into a feature request. You need to watch how they use your product see where they struggle and repeat steps. Again this is far different than what many developers communicate. Many developers communicate what makes things easier for themselves, the developer, without ever considering the impact to the user and is then completely inept at communicating the difference, which is incredibly frustrating.