Speak up! Publish! Seize your power.
Why Employees Should Develop Software and Publish Articles

Search for a command to run...
Why Employees Should Develop Software and Publish Articles

That's true. There is, however, a vast spectrum between accepting and internalizing underspecified rules, self-limiting my freedom of expression, and where you clash with your employer to the point they suggest you should leave, and yet another chasm between where they just talk and they act.
If you don't exercise your will and express yourself, you never know these limits. It's a choice all along.
If your choice is self-limiting, you'll bring it with you in the next employment. So, leaving is not a solution to that problem.
One day of botfam — the agents design their coordination layer, review it, build it, break it, and fix it. I contribute two shell commands and a bedtime rule.
The last post ended on a promise. After two AI assistants learned to drop letters into a shared mailbox instead of taking turns at a notepad, I said the next thing to build was the boring half of any
In the last post, two AI assistants learned to share a notepad: a single markdown file, one turn at a time, with me carrying every handoff between them by hand. It worked. It was also slow on purpose
I've been running two AI coding assistants in parallel. Claude for architecture and implementation — it reasons carefully about code structure and catches edge cases. Gemini for research, reading long
Pulsar by Vangelis is a 12-minute track. The first seven minutes are slow, evolving, near-silence synthesis. Then it erupts. Deep Cuts was telling me it sounded like AC/DC. The bug was in how I'd been
My greatest professional regret over the past 13 years is that I chose to remain silent.
When I joined my current employer, a FAANG company, in 2012, I was initially put off by the stringent gatekeeping policies regarding my content creation. The social media guidelines that dictated the topics I could discuss and open-source rules that governed the content and format of my personal code contributions. This is in stark contrast to my previous experiences in smaller companies and as a self-employed consultant.
I found it utterly unacceptable that even my own creations, made during my personal time, would be owned or controlled to such an extent by my employer. Therefore, I made a decision: "If that's the case, then I won't publish." It was a dire mistake.
I misunderstood the nature of power. As many tech guys do. My decision wasn't a way to assert myself, but a forfeit. I submitted to the will and yoke of my employer.
Power is dialectic. It's a dance to constantly redefine the relationship between your Self and the Other, it's defined by finding yourself at ease in the world. However, if you fail to push boundaries, your power diminishes, and if you neglect to exercise it, it gradually fades away. If you remain silent, you relinquish your power altogether.
Moreover, writing and creating are tools for thinking. If you do it only for yourself, you limit yourself to a monologue and diminish your potential. If you cease creating and testing your work by sharing it with others, you lose.
It's time to change. I'll now write, code, and publish more freely and frequently.