One of the reasons I love Google!

A few weeks ago, I was joking with a friend with how PMs aren't able to understand how weird are dev time estimations and how much they love meetings.

He: "Well, we can make a meet to estimate the hours of doing that"

Me: "Or better: We can make a meet to estimate the meet of estimations"

Three days ago, we are with the PM on the weekly meeting. In a part of his lovely speech, he asks:

"What if we meet the Thursday to estimate the weekly meeting for estimations?"

Obviously we laughed instantly, and he 'forget' he spoke that.

I would like to add a new word to the devrant glossary, next to !rant

Recursive rant - rant about another rant

Any one interested in building a devrant glossary with me? Comment the words you like to add 😅

TFW you’ve already ranted about something and you run into the same motherfucking situation again so you need another way to vent.

<rant>
when a female feels it's important to clarify that she's female in the middle of a programming discussion. what if males did the same thing?
dev1 - This recursive function just blew up the server, bitch.
dev2 - I'm a dude, bro. don't call me bitch.
commence: miles of much lost productivity.
</rant>

Google recursive and ++ if you understand Google's rant!! Lets see how many can get it :D

waiting for the stickers too come...
It's a rant about freebies for your rant. A recursive rant....

My current rant: Recursive promise chains in JS. That's all.

!rant
This morning a coworker comes to me and has been like "I've been compiling this list of all the files on our network that have x in the title for a week now"

I'm like do you want me to use a recursive Powershell script to get you that list in like 10 minutes.

The little things that make you invaluable at work because you are the sole tech guy.

#Suphle Rant 6: Deptrac, phparkitect

This entry isn't necessarily a rant but a tale of victory. I'm no more as sad as I used to be. I don't work as hard as I used to, so lesser challenges to frustrate my life. On top of that, I'm not bitter about the pace of progress. I'm at a state of contentment regarding Suphle's release

An opportunity to gain publicity presented itself last month when cfp for a php event was announced last month. I submitted and reviewed a post introducing suphle to the community. In the post, I assured readers that I won't be changing anything soon ie the apis are cast in stone. Then php 7.4 officially "went out of circulation". It hit me that even though the code supports php 8 on paper, it's kind of a red herring that decorators don't use php 8 attributes. So I doubled down, suspending documentation.

The container won't support union and intersection types cuz I dislike the ambiguity. Enums can't be hydrated. So I refactored implementation and usages of decorators from interfaces to native attributes. Tried automating typing for all class properties but psalm is using docblocks instead of native typing. So I disabled it and am doing it by hand whenever something takes me to an unfixed class (difficulty: 1). But the good news is, we are php 8 compliant as anybody can ask for!

I decided to ride that wave and implement other things that have been bothering me:
1) 2 commands for automating project setup for collaborators and user facing developers (CHECK)
2) transferring some operations from runtime to compile/build TIME (CHECK)
3) re-attempt implementing container scopes

I tried automating Deptrac usage ie adding the newly created module to the list of regulated architectural layers but their config is in yaml, so I moved to phparkitect which uses php to set the rules. I still can't find a library for programmatically updating php filed/classes but this is more dynamic for me than yaml. I set out to implement their library, turns out the entire logic is dumped into the command class, so I can neither control it without the cli or automate tests to it. I take the command apart, connect it to suphle and run. Guess what, it detects class parents as violations to the rule. Wtflyingfuck?!

As if that's not bad enough, roadrunner (that old biatch!) server setup doesn't fail if an initialization script fails. If initialization script is moved to the application code itself, server setup crumbles and takes the your initialization stuff down with it. I ping the maintainer, rustacian (god bless his soul), who informs me point blank that what I'm trying to do is not possible. Fuck it. I have to write a wrapper command for sequentially starting the server (or not starting if initialization operations don't all succeed).

Legitimate case to reinvent the wheel. I restored my deleted decorators that did dependency sanitation for me at runtime. The remaining piece of the puzzle was a recursive film iterator to feed the decorators. I checked my file system reader for clues on how to implement one and boom! The one I'd written for two other features was compatible. All I had to do was refactor decorators into dependency rules, give them fancy interfaces for customising and filtering what classes each rule should actually evaluate. In a night's work (if you're discrediting how long writing the original sanitization decorators and directory iterator), I coupled the Deptrac/phparkitect library of my dreams. This is one of the those few times I feel like a supreme deity

Hope I can eat better and get some sleep. This meme is me after getting bounced by those three library rejections