Honest github commit message

tl;dr I need ideas on how to warn the next dev(s) that the company is a dumpster fire.

------

For the past week (actual time: three days) I've been writing documentation for work, since there isn't any. It's been okay, I guess. Certainly more interesting than anything else I've done at work in months.

I'm up to 10k words / 67kb of markdown, and I think I'm done. I could easily write another 30k words on everything, but I just can't care enough.

However, what I do care about is warning the next dev(s) about how terrible the place is to work, so I want to add little references or hints or other such things to my writing. To complicate that, there's a contractor dev who said he will edit the document to strip out my commentary and make it "friendly" for the next person. (I can kind of see why: I've been quite honest about the situation of everything, and it's pretty dire. If they read it as-is, they might just walk out the door. I certainly would have.) I'm also going to commit it to the repo, and afaik he doesn't have push rights, so he can't force-push and remove it. (and a force-push by someone else, adding my documentation immediately after I leave... that would be pretty fishy, too.)

Anyway, at someone's suggestion, I added a "three envelopes" reference in the access phrase generator section. I also wrote "Promises made outside of ES6 will not resolve" -- in the warning section of a document almost entirely about Rails. (because the boss has broken every single promise he has ever made me.)

What other hints and subtle warnings could I add?

(And hurry: tomorrow is my last day! ;3)

git commit -m "It's 4:59pm, let me commit since it seems like a sane choice even though everything is currently broken"

So this is what happened!
It was a rainy Friday, I was asked to add a quick bug fix to a js application, I spent my Friday coding, testing ..., baam the patch is ready ... I wrote a nice commit message explains the problem and the fix but I didn't push the code.

On Monday the fuckin code disappeared, no commit no code no nothing no trace ... To be honest I don't know what happened. I rewrote everything on that Money morning (you can only imagine how pest I was)

I use vim with tmux.
I have done everything I could to figure out what happened to that commit, I even doubted If had did wrote the fix that Friday, but it's not possible to forget few hours of a day
I checked my commit history on the different branches i did everything

No trace ...
Conclusion
My machine is hunted ...
Or I have multiple personalities and one of them is a programmer and he is fucking with me

I discovered a commit message from one of my (senior) colleagues today. It made me shudder. It read, 'Just adding some changes made outside of source control and deployed (over last 12 months)'.

I genuinely think he can't follow any processes he didn't design. He controls the servers too, so it's not like any pipeline would prevent him from just doing what he wants. It's a bit scary to be honest, he thinks MD5 is a secure password hash!

Probably either writing the occasional lazy commit message, or skipping a few testing scenarios when testing dev work locally. Although to be honest, its rarely out of laziness that I do these things. Its often trying to urgently finish something for a weekend release/hotfix.

Work with someone else on your side project and commit to a schedule. It will keep you both honest.

In a world brimming with enticing investment opportunities, it is crucial to tread carefully. The rise of digital currencies has attracted many eager investors, but along with this excitement lurk deceitful characters ready to exploit the unsuspecting. I learned this lesson the hard way, and I want to share my story in the hopes that it can save someone from making the same mistakes I did.

It all began innocently enough when I came across an engaging individual on Facebook. Lured in by promises of high returns in the cryptocurrency market, I felt the electric thrill of potential wealth coursing through me. Initial investments returned some profits, and that exhilarating taste of success fueled my ambition. Encouraged by a meager withdrawal, I decided to commit even more funds. This was the moment I let my guard down, blinded by greed.

As time went on, the red flags started to multiply. The moment I tried to withdraw my earnings, a cascade of unreasonable fees appeared like a thick mist, obscuring the truth. “Just a little more,” they said, “Just until the next phase.” I watched my hard-earned money slip through my fingers as I scraped together every last cent to pay those relentless fees. My trust had become my downfall. In the end, I lost not just a significant amount of cash, but my peace of mind about $1.1 million vanished into the abyss of false promises and hollow guarantees.

But despair birthed hope. After a cascade of letdowns, I enlisted the help of KAY-NINE CYBER SERVICES, a team that specializes in reclaiming lost funds from scams. Amazingly, they worked tirelessly to piece together what had been ripped away, providing me with honest guidance when I felt utterly defeated. Their expertise in navigating the treacherous waters of crypto recovery was a lifeline I desperately needed.

To anyone reading this, please let my story serve as a warning. High returns often come wrapped in the guise of deception. Protect your investments, scrutinize every opportunity, and trust your instincts. Remember, the allure of quick riches can lead you straight to heartbreak, but with cautious determination and support, it is possible to begin healing from such devastating loss. Stay informed, stay vigilant, and may you choose your investment paths wisely.

Email: kaynine @ cyberservices . com