soj.ooO
BETA
The social discussion platform
Home
Pochas
Channels
Videos
Log in
Sign up
Sign up
Home
Pochas
Channels
Videos
Log in
Sign up
Parent Post: How to "exit" software development
·
In Reply To
S
saarnok
·
10/1/2026, 9:19:24 PM
·
permalink
I'll attempt to summarize what I imagine is an understanding. Organizations have organization priorities. Not production priorities. Individuals (should) have production priorities. Not organizational priorities. Individuals solely are responsible to produce. Organizations exist solely to organize individuals. The protocols of organization are accumulated, not engineered and trend toward entropy, with protocols that do not get updated or deleted, but added to as standard. Eventually the organizational protocols will overwhelm the productive protocols until the organization is forced to hire contractors outside the organizational structure to aquire productivity. My mistake was in trying to identify with a coding problem where none existed. Notes: Self motivated individuals aquire skills like a velcro ball under a bed aquires fuzz. It's just what happens. Non or un-motivated individuals aquire familiarity with protocols. Which enables them to survive within a non-productive organizational structure. Documentation in the real sense is vanishingly rare, and reconstructing a chain of "why" is largely forensic in nature and frequently more productive to start over from scratch. As an independant coder you can satisfy sufficient protocols to gain acceptance while not being mired in the mud of entropied protocols. Am I even close?
Save
Cancel
5
bumps
Share
gaby
·
10/9/2026, 4:56:58 AM
·
permalink
Thats a wonderful perspective. The coding problem is the solution. Because it takes effort to write the bureaucracy (code) into software (code) you are highly motivated to get rid of the dead code and you can add lots of easy new code that doesn't require people monitoring other people and people monitoring them where you constantly have to wonder if it is worth the money (it usually isn't) Someone who doesn't write software doesn't know which part is easy or hard.
Save
Cancel
3
bumps
Share
S
saarnok
·
10/9/2026, 10:27:10 PM
·
permalink
I'll just have to admit I don't have the experience to really understand what you're saying. I think perhaps it's a tiny bit like something I can understand, but you'd have to know what I would understand in order to make a better analogy. Unfortunately I can only grope in the dark to apprehend your meaning, where you could only tune your analogy if you had a better sense of my experiences. But, truly, thanks for the effort.
Save
Cancel
1
bump
Share
Signature
Loading…
Verify locally
Close
