Mastodawn

Hi Everyone!

I’m excited to share that I just had a paper accepted in ACM Transactions on Software Engineering and Methodology (TOSEM) co-authored with @mastorey , where we present a grounded theory, rooted in cognitive science, of the developer’s cognitive experience of troubleshooting and overcoming confusion.

Our theory 𝗴𝗶𝘃𝗲𝘀 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 𝘄𝗼𝗿𝗱𝘀 𝘁𝗼 𝗲𝘅𝗽𝗹𝗮𝗶𝗻 𝘄𝗵𝗮𝘁’𝘀 𝗵𝗮𝗽𝗽𝗲𝗻𝗶𝗻𝗴 𝘄𝗵𝗲𝗻 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝘀𝘆𝘀𝘁𝗲𝗺𝘀 𝗴𝗲𝘁 𝗼𝘂𝘁 𝗼𝗳 𝗰𝗼𝗻𝘁𝗿𝗼𝗹—𝗮𝗻𝗱 𝗹𝗲𝗮𝗱𝘀 𝘁𝗼 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗮𝗹 𝗮𝗱𝘃𝗶𝗰𝗲 𝗳𝗼𝗿 𝗶𝗺𝗽𝗿𝗼𝘃𝗲𝗺𝗲𝗻𝘁.

https://artystarr.com/blog/giving-developers-words

Show thread

Dale Hagglund

@art3starr @mastorey Just read the blog article you point to here, and it's very interesting.. The idea of troubleshooting time as a direct representation of the growing complexity of software is very interesting, and at least for me, it aligns well with my personal experience.

One of the metaphors I've used, at least in my own mind, is the notion of software being "under my control", and although I doubt I ever attempted to give it a precise definition, I think it relates closely to the idea that whatever software I'm talking about doesn't give me many surprises in it's behaviour.

Show thread

Arty Starr : ☮️ :starrgirl.eth 2h ago

@DaleHagglund @mastorey Thanks Dale, it's interesting to hear about how this maps to personal experience for you, and what you've noticed about the words and subtle meanings.

I think that's probably how I got started on this thread, is similarly noticing the subtleties of sense, like with careful iterative building up of code and things making sense as "staying in control" vs when you're surprised and not sure what is happening any more.