So today its my joining day and I'm laying in my bed with high fever and pain in my side belly . Manager was kind enough to ask me to join from Monday .
Fuck this shitty feeling .
(it's my first ever Job)

Why exacly PHP contains "T_PAAMAYIM_NEKUDOTAYIM".

Yes, I googled what that is, I understand message, yet still it strikes me if PHP creator was high that night and later figured T_THE_DOUBLE_COLON_THING_OF_MAGICK is not what he aims for and out of wtf'ness temporarly forgotten english?

And what is your theory on that

JS at its finest

while registering domain @ GoDaddy

A young guy I work with burst into tears today, I had no idea what happened so I tried to comfort him and ask what was up.

It appears his main client had gone nuts with him because they wanted him to make an internet toolbar (think Ask.com) and he politely informed them toolbars doesn't really exist anymore and it wouldn't work on things like modern browsers or mobile devices.

Being given a polite but honest opinion was obviously something the client wasn't used to and knowing the guy was a young and fairly inexperienced, they started throwing very personal insults and asking him exactly what he knows about things (a lot more than them).

So being the big, bold, handsome senior developer I am, I immediately phoned the client back and told them to either come speak to me face-to-face and apologise to him in person or we'd terminate there contract with immediate effect. They're coming down tomorrow...

So part my rant, part a rant on behalf of a young developer who did nothing wrong and was treated like shit, I think we've all been there.

We'll see how this goes! Who the hell wants a toolbar anyway?!

😮 Aparently double tapping a rant does a ++.

Try it if you are on mobile! 📱

Looking at code in our workplace.. I realized one thing. Like Devops, legacy code is actually a mindset.

So here goes my thought:

A piece of code is not legacy because it was written ten years ago.

A piece of code is legacy because it looks like a piece of legacy code.

With the legacy code mindset, you end up writing legacy code no matter where you are, when you wrote it.

I was looking at some part of our code which we written in just the last few months, and I can’t help but think that they were legacy, so it really doesn’t matter when it was written!

It is more about how you write your code that determines whether it is legacy :)

Hopefully this was not crazily confusing anyone. Have a good day guys & gals!

Wanna mess with users? Take

“OK” and “Cancel”.

You know what looks visually the same but means the opposite?

“NO” and “Confirm”.

Deploy that little ui update overnight and watch the world burn.

Class constructor defined on line 700+
😑 Really...

FREE!!!! At last, my kids are out for the whole day!!!!!!!
No more nagging, crying, bitching from them while I'm in the zone!!!!

FREE!!!!!!!!

If you're going to have your package write into the SSIS log "please check the SSIS log for details" when your package throws an error

Kindly throw yourself off a cliff.

WRITE THE FUCKING ERROR TO THE FUCKING LOG.

If I'm reading the log, I'm already CHECKING THE FUCKING LOG. So I don't need the log to tell me to check the log.

Accurate 😆

Had to share it

It’s true

The sorrow does not go away, one only gets used to it.

In the before time (late 90s) I worked for a company that worked for a company that worked for a company that provided software engineering services for NRC regulatory compliance. Fallout radius simulation, security access and checks, operational reporting, that sort of thing. Given that, I spent a lot of time around/at/in nuclear reactors.

One day, we're working on this system that uses RFID (before it was cool) and various physical sensors to do a few things, one of which is to determine if people exist at the intersection of hazardous particles, gasses, etc.

This also happens to be a system which, at that moment, is reporting hazardous conditions and people at the top of the outer containment shell. We know this is probably a red herring or faulty sensor because no one is present in the system vs the access logs and cameras, but we have to check anyways. A few building engineers climb the ladders up there and find that nothing is really visibly wrong and we have an all clear. They did not however know how to check the sensor.

Enter me, the only person from our firm on site that day. So in the next few minutes I am also in a monkey suit (bc protocol), climbing a 150 foot ladder that leads to another 150 foot ladder, all 110lbs of me + a 30lb diag "laptop" slung over my shoulder by a strap. At the top, I walk about a quarter of the way out, open the casing on the sensor module and find that someone had hooked up the line feed, but not the activity connection wire so it was sending a false signal. I open the diag laptop, plug it into the unit, write a simple firmware extension to intermediate the condition, flash, reload. I verify the error has cleared and an appropriate message was sent to the diagnostic system over the radio, run through an error test cycle, radio again, close it up. Once I returned to the ground, sweating my ass off, I also send a not at all passive aggressive email letting the boss know that the next shift will need to push the update to the other 600 air-gapped, unidirectional sensors around the facility.