Just a couple weeks ago I felt a bit like a hero.

My boss, who seems to have only a vague understanding of realistic deadlines, for once made an error that gave me more time than I needed, not less. I was working on a feature that other work would rely on, so some people had to wait to work on their own projects until I was done.

My boss said it would be done in two weeks, but the only reason why it would have taken that long was because I'd have to submit a ticket to our identity management team to set up the SSO integration with our identity provider, and their turnaround time is two weeks. Or it used to be, but they've actually gotten really fast recently, and as I'd actually grabbed this feature from someone else who had to take a few days off, he'd already gotten the SSO stuff taken care of in advance. My boss promised two weeks and I finished in two days. The shocked silence when they asked for a status update in our next meeting and I told them I'd just finished it was music to my ears.

Why did the chicken get a penalty? For fowl play.

Every time there is a new project, we programmers swear to ourselves that we will code it better this time. We get elated that we do not have to deal with the tech debts piled up in the old module.

Lord. Please deliver us from the cycle of unfinished programming languages and code benches that are designed to create more work for us. We beseech thee in thy mercy to transmute all this asynchronous lead that is found in javascript into a purer form of threading that is sensible and can be willfully blocked or not so in a way that works and does not divide us through our ugly code. May also we be given the ability to purge from our midst all child molesters and string them up by barbed wire off a line of telephone poles across the entire continental usa and may there be a sudden increase in the number of ravens and buzzards to feed on them, being nice birdies that I miss seeing so much. May half their positively identified population be kept alive and delivered unto us that we might remove their scrotum with a hook-ed barb and something resembling a serrated metallic spork, amen.

and please fix fucking node js. i agree that its asynchronous methods suck ass for literally everything as there is no use for it that seems to work given its a shitty emulated single thread.

Just had my last day at my current job last week. I got this amazing virtual card with 20-30 people telling me how amazing I was and how large of a difference I made. I’m not someone that seeks or needs validation, but to see those comments in writing really made me feel good and like I made a huge difference.

So if you’re awaiting a promise and the async function returning the promise calls another async function and doesn’t await it could this counterintuitively cause the whole thing to freeZe ?

Update from the last two rants:

The good ending :D (Solus Budgie)

Story of me trying to connect to a colleague from neighbouring team with 12 hour difference timezone:

Me: Hey! Shall we catch up to discuss a feature that will help us dominate the world?

She: Sure.. what time works for you?

Me: Since we have timezone challenge, I'd say boundary times would be good so none of us have to stretch.

She: umm.. good..

Me: How about 07:30 PM your time?

She: oh sweetie.. evenings don't work for me.. I want my evenings free..

Me: fine.. how about 07:00 AM your time?

She: no darling.. I am not a morning person..

Me: GO FUCK YOURSELF BITCH. I CAN'T COMPLY WITH EVERY TANTRUM OF YOURS.

And with that.. I didn't respond to her invites which were either super early for me or super late. Let her keep waiting..

Juniors with ego are shittiest folks to work with.

What am I doing with my life. Staying awake playing the stupid stardew game… it is 6 am ffs…

Programming is like cooking. In more ways than one.

PhD applications in computer science are so fucking frustrating. I have responded to so many invasive questions so far. The only private information universities haven't asked yet, is my bra size. The only contact they haven't asked for yet, is my kindergarten teacher (And her bra size, coincidentally). The only document about a potential project I haven't given to them yet, is my freaking dissertation. None of these have anything to do with my research potential, btw. There's nothing asked of me about my research aspiration and how I actually undertake a research project.

And then suddenly it occured to me: people in Academic administration are not smart. I'm actually explaining my potential to a pretty dumb bunch (Excluding those in research, none of whom will bother with these stupid documents).

... The world seems to revolve around stupid people. Fuck.

Like Ads on digital world werent enough, now there will be billboards in space too. 🤦‍♂️

(SpaceX Launching Satellite to Display Billboard Ads in Space)

https://futurism.com/spacex-billboa...

Two types of men in this world
The ones admitting to themselves they need a tomboy gf and the ones lying to themselves

Boss: Can I pick your brains about something for 5 mins?

Me: Sure

-Call started-

(2hr 49min later...)

Boss: So you're still on track to finish that project by lunch today?

...

-Call ends-

Hey. I'm still very new to CloudFlare and I have a question.

Let's say that I have 4 sub domains: a.test.com, b.test.com, c.test.com, d.test.com. They're all under the same domain (test.com).

I have a page rule setup specifically for a.test.com, where "Disable security" is set to On. I did this as a temporary solution so that I can figure out the problems that a.test.com has when the security is enabled (had users complaints regarding not being able to send requests with CF security On), so that it is still accessible while I try to fix it..

By turning disabling security for a.test.com, do I put others (b, c, d) at risk? I had someone telling me that it is possible for attackers to make use of a.test.con (unprotected by CF) in order to attack the other sub-domains. "a.test.com has no protection so attackers can use it to send requests to other secured subdomains, cross-site attack" or something along that line.

I don't get this. I thought page rule is supposed to be active only for the domain where it's being set up and the rest will still be secured, and that if attacker manages to attack the other subdomain its due to the others not having secure applications inside of it.

Dunno if that person was telling the truth or tried to mess around with me with their joke!

Thanks!