My company just did its first delivery to a new big customer , got the acceptance docs signed etc.

Was pretty funny to see management and the business-tards furiously emailing one another with company wide replyAll
Congratulating one another over an excellent job they had done in particular,

for example :
Gavin : Ahh capital , well done john for your undertaking in this tremendous accomplishment

John: oh and thank YOU for your guidance Gavin, couldnt have done it without you, we really exceeded outselves with the hard work we put it, also a big mention to (insert another inbred manager's name)

And that keeps on bouncing on and on

( absolutely no fucking mention of devs who did the actual Work, nooo nooo just a brief reference to us as "the boys in london"....)

Kinda glad they aren't in office most of the time else this level of back-patting would have probably turned into a circle jerk in the board room.

Almost thought of getting the dev teams to join the storm of emails and start randomly congratulating one another too with company wide replyAlls but that kind of prank would likely be ill received by out high and mighty leaders.

( on the flip side maybe they would actually learn out names)

google products...

I am writing a UI api for microcontrollers as a pet project.
I usually follow kernel.org for coding style so visited the site to see if there are any changes, these docs are so funny

Ok who is the Cordova dev that thought it would be funny to make the indices from the confirmation box start at 1 and not mention it in the docs?!

It’s so funny when old ass software tries to be hip and add a cool new design to their documentation, but they just end up fucking it all up because they don’t know how to setup anything in the modern era. Like I’m looking at these docs but it is fucking with the JavaScript page click events and the FID is like SECONDS longer than the LCP so your like “oh fuck did this shit just crash my computer?!?”. On top of that everything is overflowing with this absolutely positioned nightmare.

I don't know how it works with my team but almost always I'm the one who is at the frontier when there is a need to migrate to new technology or to do something that nobody in my team knows how to do including me. So usually when we have planning and nobody wants to take the task I take it because someone has to do it. I think it's not my job to only do the things that I know but I'm expected to work outside my comfort zone and I wish others did the same. What happens after I'm done reading docs, testing and learning new thing is that I have to deliver training about it. The funny thing is that I also have to train experts and I'm below expert

#Suphle Rant 8: Strange star discovered

I was searching for a project I'd starred earlier, on my github feed, when I realised a user had starred suphle at some point but for some reason, it wasn't reflecting on the stargazers. I was half overjoyed and half confused. Overjoyed over unlocking the milestone.

User seemed legit –an Italian with projects in C that were not forked. Followers and commit graph are organic. Did he star in error, feel the project is a stinker, or encounter installation challenges? Luckily, I found his email address but all his repositories are in Italian so I wasn't too sure he'd understand English, or if the mail was being attended to. Yet, I took my chances

He surprisingly got back to me, affirming that the star-unstar was actually deliberate. He withdrew the star cuz project's documentation is not hosted online and still requires npm start.

I try to persuade him by reminding him it's just a one liner but that markdown files are equally rendered directly on github. Never heard from him again, sadly

I'm kind of bothered cos I find it funny I thought suphle's APIs are all cast in stone, but the more I work on the docs, the closer I am to spotting something that doesn't sit right with me, and diving in to modify it. This not only prolongs ETA, there's the risk of someone who may have stumbled upon it and is studying it, having the rug pulled from under their feet. Things like validator rules and route-collection service-coordinators have been converted from methods and classes to native decorators. I guess I'm safe since nobody has indicated any signal to the contrary. It'll be pedantic to start tagging versions for each change.

Another consideration is that these breaking changes would go to the first segment of the semver scheme, which is hilarious because the rate at which I push such changes is so alarming, we'd probably progress through 15 versions under a year

LXDE documentation.. :')