Not really, no. I'm more of a writer, but I'm a writer interested in software development.
Discussion
writer and analyst i'd call it
also not just software development but also resilient, reliable communication systems
Processes, really. I'm also really interested in logistics and production chains.
SW algorithms are just more processes.
i do prefer to study processes over objects.
verbs are more important than nouns
all nouns represent processes
born, live, die... a process, not a fixed entity
objects are a terrible way to model processes
Completely, but we could be wired (evolutionary or developmentally) to "encapsulate" ideas and to understand their bounds. So embedded in our language design, how does one even create a process based language?
"humaning sitting over compacting earthing, thinking"
/400px-Mus%C3%A9e_Rodin_1.jpg
"Pasting chiseling marbling stabilizing as humaning sitting over compacted earthing, thinking"
Modern Germans do something like this to avoid using nouns, as a way to not presume gender.
Instead of "swimmer", they say "swimming person", for instance.
one of the most ancient and still living languages, Bulgarian, heavily focuses on verbs, and has way more explicit tense modifier suffixes and prefixes than any other language i am familiar with
i'm inclined to suspect that at one time, humans had a more imperative language style than the typical modern languages
Fascinating. Process theory is so interesting because if you want to model/simulate/learn about Complex phenomena you can't start out with its basic components (unless you approximate with a computational model. Emphasis on approximate). You need to observe the system as it exists. There is never any "jump starting" like you can do with a computer because it is all entangled at multiple levels and is always in flux. You're never going to get to the "origin" but you can find limits to your theory, placing bounds that describe the phenomena in a specific context.
Didn't she like, oversee a dev project though? Maybe more than analyst
Writer and visionary or something like that
I'm a developer, actually. I just don't burn with ambition for coding.
I burn with ambition to see the problems solved by an elegant solution, and to see processes efficiently formalized, and software is often part of that solution.