Elektrine lite

← Feed

@EricLawton@kolektiva.social

Post #2832576

2025-12-25 18:17 UTC

@soph@grrl.me @hazelweakly@hachyderm.io @adub@kolektiva.social My job as lead IT architect was to get people talking and converge on a solution that would help the people who could benefit from better information and automation of tasks that humans couldn't do well or didn't want to do. Although I had Comp Sci qualifications, and had written almost a million lines of code, that was just a barely-useful requirement to get the job. My most useful qualifications were: - Formally, experience as a social worker and grad school in philosophy. Maths helped a little, in knowing how to read and question statistics. - Informally, wide reading and lengthy discussions with academic friends in the social sciences and political activity in organizing for progressive movements and a socialist political party. - From social work, an ability to listen carefully and ask questions to help people say what they found hard to express, and a knowledge of how to deal with bureaucracy. (Not always possible 😟) From philosophy, as you say, ethics was most important, and a toolkit for analyzing complex problems. Although there are other combinations of skills and experience that help with the role, I agree that getting people to see that tech skills are low on the requirements list is the hard problem.

Replies (1)

  • @siderea@universeodon.com 2025-12-25 21:34

    @EricLawton@kolektiva.social One of the missing bits is tech people not realizing that they would get to feel differently about their work if they connected to the for-other-people aspect of it. Those who lack it are missing out on the satisfactions of meeting human needs. And that is the crucial "what's in it for me of doing this differently, for caring about all this human stuff like requirements discovery and ethics" part that motivates change. @soph@grrl.me @hazelweakly@hachyderm.io @adub@kolektiva.social

    Open ##2832577