> I would say the good lawyers are going to naturally be bad clients for software development services. “Can’t be bothered” is how I would sum it up. Can’t be bothered to flush out requirements, can’t be bothered to use any project management tools like JIRA or Basecamp, absolutely no interest in understanding the difference between Solution A and Solution B or the potential consequences of either.
Sounds pretty good to me TBH. I see this stuff as part of software development, though often there's a specialised role (e.g. project manager) that handles it, I think there's value in learning to enjoy it. If they don't want to use Jira, can you make it work for them via their preferred channel and write your own tickets? If they don't care about the difference between two solutions, does that mean they trust you? Can you communicate it in terms they care about (e.g. economics, security)?
I can see how you'd want to focus on the code, but I really do think the stuff between the stakeholder's brain and the code can be a satisfying part of the job as well.
Yeah fair enough. I do write my own tickets. I don't think that resolves the "can't be bothered" attitude- that they're very busy and value their time very highly.
I will add another interesting quirk- he will never admit fault and in written communication tends to "make assertions" and I feel like I have to defend them or the lack of defense means his assertions are correct "in a court of law" - I don't know if I'm describing that well. Basically he has it so ingrained in him never to say anything that may be used against him later, even though obviously I have no intention of suing him now or in the future.
It amounts to a sense of under-appreciation and that I am not respected.
We have a patent together through this project. It's very interesting work that I wouldn't be doing anywhere else. It definitely could be worse.
Sounds pretty good to me TBH. I see this stuff as part of software development, though often there's a specialised role (e.g. project manager) that handles it, I think there's value in learning to enjoy it. If they don't want to use Jira, can you make it work for them via their preferred channel and write your own tickets? If they don't care about the difference between two solutions, does that mean they trust you? Can you communicate it in terms they care about (e.g. economics, security)?
I can see how you'd want to focus on the code, but I really do think the stuff between the stakeholder's brain and the code can be a satisfying part of the job as well.