@mayintoronto I don't know if I should answer this because I don't know if enough of what I do strictly counts as software development
@JubalBarca what do you do?
@mayintoronto I'm a historian but also my insitute's digital humanities person and also do game development work in my spare time: I do a moderate amount of of programming for both, and insofar as "build/adjust computer system using code in order to make it do the thing someone wants it to do" is software development, then that is a chunk of my job but it's not like my job title or core training.
I guess I don't really know where "proper" software developers think the edge of their field lies!
@JubalBarca I generally go with the self identification. If you feel like you're a developer, go for it either way.
I feel like classic software devs are the majority of people who identify as one, so a small percentage of outliers are expected and reasonable.
@mayintoronto luckily we meet with clients once every fortnight and often prep with them to present outside to others (this is data science though)
@mayintoronto Next to System Metaphor, which no one could quite figure out, and Sustainable Pace, which no employer could ever figure out, Onsite Customer is the most unused of all the original Extreme Programming practices.
I coached dozens of teams for over 25 years. I saw it twice. It worked, of course, *stunningly* well.
@GeePawHill Fully remote company makes onsite customer a little more complicated. We're just trying to get to Zoom calls, you know?
@mayintoronto Dig. I'd set up an always-on zoom and pay a customer to be "in the room" for half a day every day. Of course, I want the *team* to be "in the room" most of the day.
I emphasize over and over to people the extreme power of the Haykumeer Protocol:
"Hey. Come here."
@GeePawHill How do you swing this for B2B?