This is what I am learning now. How best to maintain project management docs, specifications, tickets, and so on, on trunk.

I started out putting it in a separate branch and committing generated code to its own branch, and merging. I thought my prompting and writing was just for me, or at least, not what people would want to see.

#LiterateDevelopment #CleanCode

I have realized the error of my ways. The docs are the code. The English is the important part, now.

How are you doing it?

Writing Clean Code for Games (Industry Veteran) - YouTube

https://www.youtube.com/watch?v=Fxea6TG0PXk

#gamedev #cleancode

🚀 New chapter added to the Guile Hacker Handbook 🚀

This is a book to learn #Guile in a #TestDrivenLearning style 👽

⬇️ Check it out ⬇️
🇫🇷 🇬🇧 🇮🇹 https://jeko.frama.io

Contrary to what I have said previously, this new chapter is about having some fun using the use-cases in the REPL.

#gnu #scheme #tdd #cleanCode #cleanArchitecture

Distressed friend demands help: Even support systems need clear boundaries. Demanding emotional labour without consent violates the Principle of Reciprocity and drains energy. We move from Corrupted Code (Force) to Clean Code (Power).

Scenario: A friend is in crisis and demands immediate emotional support late at night, despite repeated hints the recipient is busy. The friend replies:

❌ Corrupted Code (Force):
"I need to talk right now, I'm having a crisis. Just drop what you're doing, I can't handle this alone." (Demands immediate, non-consensual labor, ignoring the recipient's boundaries.)

✅ Clean Code (Power):
"I'm having a crisis and need support. Are you in a good space to talk for a few minutes now? If not, please let me know when might work for you tomorrow." (Asks for consent; respects the recipient's agency and energy.)

The difference? The second message respects the recipient’s energy system. What boundary can you clearly state today?

#SystemsLeadership #EmotionalLabor #Reciprocity #CleanCode

Hot for teacher? Academic settings are not exempt from power abuse. Coercion violates the Principle of Trust and corrupts the integrity of mentorship. We move from Corrupted Code (Force) to Clean Code (Power).

Scenario: A student approaches a professor for help on a critical assignment. The professor replies:

❌ Corrupted Code (Force):
"I can help, but it will require a lot of late-night one-on-one time outside the office. Maybe we discuss it over dinner tonight?" (Leverages academic need to blur boundaries.)

✅ Clean Code (Power):
"That's a critical topic. I can give you an extra 30 minutes during my office hours tomorrow, or connect you with the senior TA for immediate help." (Affirms professional boundary; prioritizes resource access.)

The difference? The second message preserves the trust essential for education. What boundary can you clearly state today?

#SystemsLeadership #AcademicIntegrity #PowerDynamics #CleanCode

Bad Boss? When power dynamics are involved, clear boundaries are critical. Coercion is not only personal; it is a Systemic Failure that violates the Principle of Professional Equity. We move from Corrupted Code (Force) to Clean Code (Power).

Scenario: A junior team member ends a secret relationship with their senior manager. The manager replies:

❌ Corrupted Code (Force):
"If you end this, it will make things awkward in the team, and I can't guarantee your next review will be positive. We should keep this quiet." (Coercive; uses professional power to threaten and manipulate.)

✅ Clean Code (Power):
"I respect your decision completely. I will be transparent with HR about my boundary failure, and your job security is not threatened. We proceed professionally." (Restores integrity; affirms the junior's agency and safety.)

The difference? The second message prioritizes integrity over personal gain. What boundary can you clearly state today?

#SystemsLeadership #WorkplaceIntegrity #PowerDynamics #CleanCode

Meat Grindr: Misogyny isn't the only systemic failure online. Pressure and coercion violate the Principle of Agency. We move from Corrupted Code (Force) to Clean Code (Power).

Scenario: A newly single man on Grindr is pressured to meet up immediately without safety checks. The messager replies:

❌ Corrupted Code (Force):
"Stop making excuses. If you're serious, you'd come over now. Don't waste my time." (Coercive; ignores safety and agency.)

✅ Clean Code (Power):
"I understand you need to take your time. Your safety is most important. Let's do a quick video chat first, or we can chat more until you feel ready." (Affirms boundary; prioritizes well-being.)

The difference? The second message respects pace and safety. What boundary can you clearly state today?

#SystemsLeadership #ConsentCulture #GrindrSafety #CleanCode

Direct application of the 'Easy Wins' from my recent Scaling Respect + Consent on the Fediverse infographic. (Context: https://tech.lgbt/@Crissy/115647862289071322)

Misogyny isn't just poor communication; it's a Systemic Failure that violates the Principle of Trust. We fix it by moving from Corrupted Code (Force) to Clean Code (Power).

Scenario: A woman declines a nude request. The man sends one anyway (unsolicited). She declines to send her own. The man replies:

❌ Corrupted Code (Force):
"Okay, but you need to send me one back now. It's only fair." (This assumes entitlement and ignores consent.)

✅ Clean Code (Power):
"My apologies, sending that was out of line. I should have respected your initial 'no.' I respect your boundaries entirely." (This affirms integrity.)

The difference? The second message rebuilds trust. What boundary can you clearly state today?

#ConsentCulture #SystemsLeadership #CleanCode #Fediverse

🚀 New chapter added to the Guile Hacker Handbook 🚀

This is a book to learn #Guile in a #TestDrivenLearning style 👽

⬇️ Check it out ⬇️
🇫🇷 🇬🇧 🇮🇹 https://jeko.frama.io

Contrary to what I have said previously, this new chapter is about having some fun using the use-cases in the REPL.

#gnu #scheme #tdd #cleanCode #cleanArchitecture

Simplify Your Code: Functional Core, Imperative Shell

https://testing.googleblog.com/2025/10/simplify-your-code-functional-core.html

#HackerNews #SimplifyYourCode #FunctionalCore #ImperativeShell #CodingTips #SoftwareDevelopment #CleanCode

Favour composition over inheritance. Instead of deep class hierarchies, build objects by combining smaller, focused components. Easier to test, modify, and reason about. #DesignPatterns#CleanCode

Favour composition over inheritance. Instead of deep class hierarchies, build objects by combining smaller, focused components. Easier to test, modify, and reason about. #DesignPatterns#CleanCode