For 10 thousand years I have pronounced "Nginx" as "En ginns" just found out from Ubuntu's official page that it is pronouned "Engine-X".
What a shame (－‸ლ)

Haha, today I learnt that agile doesn't just stop in the enterprise with SAFe (Scaled Agile Framework), management has continued the theme in my new company with Lean-Agile Center of Excellence (LACE) and Agile Release Trains (ARTs).

Software development in 2021...

Story of my most useless meeting?

Too many to mention. Here's one. Years ago a new HR associate was specifically hired to better engage the workforce. About once a week, she conducted about an hour to two hour meetings which consisted of every 'touchy-feely' idea you could think of. I swear any day I was going to walk into a meeting and do the "fall back into your partner" trust exercises.

One particular meeting, 'Betty' engaged us with the topic of what keeps us motivated, and I was a little more annoyed than usual because I was behind on a system critical project and these meetings were mandatory.

User1: "Knowing I make customer satisfaction my number one priority."
User2: "The strong sense of accomplishment I feel by doing my best"
Me: "Money"
<you could almost hear Betty's gasp>
Betty: "Oh, no, money shouldn't be the motivator. Money is like icing on the cake. Tell us what keeps you happy and engaged."
<other users nod their heads in engagement>
Me: "Again, money."
User3: "I can't...ugh..I don't believe..oh..why would you say that? I think being part of such a great team is payment enough."
<more nodding of heads>
Me: "Do you work for free? I don't. None of us do. Would any of you keep doing your jobs here if you weren't getting paid?"
Betty: "That is really not the point of this meeting."
Me: "Sure it is. I'll bet if Order Taking starting providing bonuses for positive after-call surveys, employee satisfaction would go through the roof. Anyone else like that idea?"
Betty: "Your attitude isn't helping this discussion. Lets move on."
Me: "Lets not. In 20?? the Gartner group performed a study where they 'discovered' the primary motivator for employees was money. You want employees to perform better, you pay them. It is really that simple."
<I could see the looks of "Its OK to speak my mind?" and others wanting to speak up>
Betty: "Moving on. Lets go over the company core values again and discuss how they enrich our lives at work and at home."

I kept quiet for the rest of the meeting.

The poop hit the fan, and my boss pulls me into a conference room
Boss: "Betty is really pissed at you. She went directly to the VP of HR"
Me: "Good. Does this mean I don't have to attend the enrichment meetings?"
Boss: "Yea, that was her idea of punishment. Lucky bastard."

Still trying to get good.

The requirements are forever shifting, and so do the applied paradigms.

I think the first layer is learning about each paradigm.

You learn 5-10 languages/technologies, get a feeling for procedural/functional/OOP programming. You mess around with some electronics engineering, write a bit of assembly. You write an ugly GTK program, an Android todo app, check how OpenGL works. You learn about relational models, about graph databases, time series storage and key value caches. You learn about networking and protocols. You void the warranty of all the devices in your house at some point. You develop preferences for languages and systems. For certain periods of time, you even become an insufferable fanboy who claims that all databases should be replaced by MongoDB, or all applications should be written in C# -- no exceptions in your mind are possible, because you found the Perfect Thing. Temporarily.

Eventually, you get to the second layer: Instead of being a champion for a single cause, you start to see patterns of applicability.

You might have grown to prefer serverless microservice architectures driven by pub/sub event busses, but realize that some MVC framework is probably more suitable for a 5-employee company. You realize that development is not just about picking the best language and best architecture -- It's about pros and cons for every situation. You start to value consistency over hard rules. You realize that even respected books about computer science can sometimes contain lies -- or represent solutions which are only applicable to "spherical cows in a vacuum".

Then you get to the third layer: Which is about orchestrating migrations between paradigms without creating a bigger mess.

Your company started with a tiny MVC webshop written in PHP. There are now 300 employees and a few million lines of code, the framework more often gets in the way than it helps, the database is terribly strained. Big rewrite? Gradual refactor? Introduce new languages within the company or stick with what people know? Educate people about paradigms which might be more suitable, but which will feel unfamiliar? What leads to a better product, someone who is experienced with PHP, or someone just learning to use Typescript?

All that theoretical knowledge about superior paradigms won't help you now -- No clean slates! You have to build a skyscraper city to replace a swamp village while keeping the economy running, together with builders who have no clue what concrete even looks like. You might think "I'll throw my superior engineering against this, no harm done if it doesn't stick", but 9 out of 10 times that will just end in a mix of concrete rubble, corpses and mud.

I think I'm somewhere between 2 and 3.

I think I have most of the important knowledge about a wide array of languages, technologies and architectures.

I think I know how to come to a conclusion about what to use in which scenario -- most of the time.

But dealing with a giant legacy mess, transforming things into something better, without creating an ugly amalgamation of old and new systems blended together into an even bigger abomination? Nah, I don't think I'm fully there yet.

To my ex manager

you left to berlin, and left me to rot

my new lead sucks, i kid you not

it was ok if I slacked off, You used to be chill

But my new lead is uptight, he's on my list to kill

I wanna run errands in work hours, is that so bad?

was doing so for years, now i lost what i had

I cant drive in peace, coz i know he'd call

so i had to cancel plans to go to the mall

its like 10 to 6 is now constant work

I hate my new lead, he is such a jerk

Client-side router entirely in CSS

I must use GPT-3 to automate my daily rants on DevRant.

Drinking game: Take a shot whenever you’re staring at work and don’t feel like working.

Bonus game: try not to die or get fired.

The following meeting occurred at a client between a recently added client PM and our team, we'll call her Shrilldesi, previously from one of the main consulting vendors.

*Meeting begins after 15 minutes of bullshitting, waiting for people to file in*
Shrilldesi: "Ok everyone, let's get started
TeamMember: "We're still waiting for Z and W, not sure why they're late."
SD: "We can start there. It was decided had to lay off Z and W, because we didn't have enough work."
Moi: "Wait, what. Who made that decision? Why weren't we consulted on this? We have another project starting next week that they were needed for. They just delivered the entire public facing rewrite, why would we let them go?!"
SD: "It was decided by myself, pajeet, and venkata looking at the backlog. Not enough work, week gap."
Moi: "This is going to hurt our ability to deliver the next phase. When are we going to start interviewing new people, the project begins next week?"
SD: "We will interview new resources as needed."
Moi: "Who is we? And 'as needed' is yesterday, or realistically several weeks ago as the. project. starts. next. week. Also, we're obligated by federal law to bring back anyone we lay off before we hire anyone else for the same position."
SD: "Interviews will be done by myself, Mohd, and Pajeet."
Moi: "...can I point out that there's only one modestly technical person in that group, they're an admin, and none of them are from this team? How do you conduct an engineering interview without any engineers?"
SD: "That does not matter, I have watched enough to be able to ask your questions."
Moi: *anger intensifies* "I have to respectfully disagree. I don't feel it's appropriate to cut us out of the process of interviewing our own team members."
SD: "It is decided, we will take care of it, let us move on. Next, we need to find work for the Manasa, she doesn't have anything to do."
Moi: *sharpens baseball bat* "...shouldn't we just fire her then?"
SD: "Oh that is so mean, why would we fire her? We were thinking she might be able to do some of my project management work."
Moi: *sharpening intensifies* "You do realize it's a violation of H1-B statutes for someone to be employed in work other than what is stated on their contract, and Project Managers are specifically listed as not specialized skillsets per federal law."
SD: *ignores question* "We also need to find work for the offshore team, they don't have enough to do. Please find them work for the next period."
Moi: *checks how long the wait period is for ar-15s*
SD: "We also have a new person rolling onto our team, he comes from the xyz team, Dikshit *gestures to person we all figured was lost*. He will be handling our front end development."
Moi: *seething hatred* "WE JUST LET TWO EXCELLENT FRONT END DEVELOPERS GO. WE DO NOT NEED DIKSHIT."
SD: "Please calm down. We will be replacing the other two shortly, there is no problem."
Moi: "Have you heard nothing I've said? Did you even run this by legal and HR? Why did we let them go in the first place? Why do we even need Dikshit?!"
SD: "I said it before, please listen. There is not enough work for them. Dikshit will do front end. What is unclear?"

Note: There's not really any dramatization here. It's almost verbatim what happened. Eventually, the next project was cancelled, they incrementally rolled the rest of the local team off. They then had the cojones to express aghast anger when I notified them I would not be renewing my contract, and open hatred when I explained to them I was not a slave, and I refused to be a bag holder for the inevitable failure of a project without any chance of success. I don't really care what happened after that, they can all burn in their own little nepotistic shitshow of perpetual failure.

First month of project we suggest that we test that Entity Framework has made reasonable DB queries because the system will need to handle a lot of records. “Not a priority in this sprint because we need features.” Devs try to get it into every sprint. The last week of the project they want us to dump in a ton of records so they can test it. The N+1 SELECT query issue is on main queries. It is so bad and slow with more records that a simple query causes the container management to auto scale the application on a single query. They can have max 8 users in the system at a time and it will take 10 seconds to do a simple page refresh.

They get on our case and we dredge up all of the correspondence where they completely ignored our advice. Fix it now! We need another sprint. Fix it free! No.

WebDev jobs should come with big warning signs:
"You absolutely will lose your sanity!"
"IE11 might indirectly lead to impotence!"
"You won't get laid more often by using CSS Grid!"
"You will have to fix websites which only appear broken on iOS Safari!"
"Get some extra terabytes ready for your node modules!"
"Get ready to yarnify your npm dockerized webassembly blobs while gulping on your mocha chai latte with no karma!"

Can't we just go back to the good old times with Quick Basic and chill?
Man, the ladies were flocking around those programmer boyz, I tell ya... Klickety klackety on the mechanical

So, economy is fucked, that’s convenient

Today I welcome a new bot into our little world.

Have you ever had the need to write "did you google it" before?

@lmgtfy will turn your comment into a lmgtfy search.

Just tag @lmgtfy and any text afterwards will be added to a search term. (Excluding emojis - because reasons)

I'm going on vacation next week, and all I need to do before then is finish up my three tickets. Two of them are done save a code review comment that amounts to combining two migrations -- 30 seconds of work. The other amounts to some research, then including some new images and passing it off to QA.

I finish the migrations, and run the fast migration script -- should take 10 minutes. I come back half an hour later, and it's sitting there, frozen. Whatever; I'll kill it and start it again. Failure: database doesn't exist. whatever, `mysql` `create database misery;` rerun. Frozen. FINE. I'll do the proper, longer script. Recreate the db, run the script.... STILL GODDAMN FREEZING.

WHATEVER.

Research time.
I switch branches, follow the code, and look for any reference to the images, asset directory, anything. There are none. I analyze the data we're sending to the third party (Apple); no references there either, yet they appear on-device. I scour the code for references for hours; none except for one ref in google-specific code. I grep every file in the entire codebase for any reference (another half hour) and find only that one ref. I give up. It works, somehow, and the how doesn't matter. I can just replace the images and all should be well. If it isn't, it will be super obvious during QA.

So... I'll just bug product for the new images, add them, and push. No need to run specs if all that's changed is some assets. I ask the lead product goon, and .... Slack shits the bed. The outage lasts for two hours and change.

Meanwhile, I'm still trying to run db migrations. shit keeps hanging.

Slack eventually comes back, and ... Mr. Product is long gone. fine, it's late, and I can't blame him for leaving for the night. I'll just do it tomorrow.

I make a drink. and another.
hard horchata is amazing. Sheelin white chocolate is amazing. Rum and Kahlua and milk is kind of amazing too. I'm on an alcoholic milk kick; sue me.

I randomly decide to switch branches and start the migration script again, because why not? I'm not doing anything else anyway. and while I'm at it, I randomly Slack again.

Hey, Product dude messaged me. He's totally confused as to what i want, and says "All I created was {exact thing i fucking asked for}". sfjaskfj. He asks for the current images so he can "noodle" on it and ofc realize that they're the same fucking things, and that all he needs to provide is the new "hero" banner. Just like I asked him for. whatever. I comply and send him the archive. he's offline for the night, and won't have the images "compiled" until tomorrow anyway. Back to drinking.

But before then, what about that migration I started? I check on it. it's fucking frozen. Because of course it fucking is.

I HAD FIFTEEN MINUTES OF FUCKING WORK TODAY, AND I WOULD BE DONE FOR NEARLY THREE FUCKING WEEKS.

UGH!

Random Showerthought: Any 2FA code prefixed by 2 is a valid nhentai code

I get asked a lot of random questions. Today's climbs to the top ten:

"Does anybody own a hamster? Marketing is asking for one"

Next level of Google Translate

A friend bought a new PC and asked me to help him set it up. He said he got everything working except the CD drive. He said it took him forever just to figure out how to get the keyboard and mouse to work. "I mean, have you ever owned a computer where the keyboard and mouse had to plug into the monitor instead of the computer?"

He bought a desktop PC, and and all-in-one thinking it was a monitor. He had the HDMI going from the all-in-one to the desktop, and was trying to use the CD drive on the desktop.

Wish you could've seen his face when I unplugged the desktop computer and his "monitor" didn't shut off. He looked at the desktop, and then the all-in-one, and said, "Wait... How is it still on?"

He also had his old USB wifi plugged into the desktop thinking that's what was providing him with an internet connection.

SAO is the VIM of VRMMORPGs

(I liked this so much I had to continue the VIM shitposts)

I'm getting ridiculously pissed off at Intel's Management Engine (etc.), yet again. I'm learning new terrifying things it does, and about more exploits. Anything this nefarious and overreaching and untouchable is evil by its very nature.

(tl;dr at the bottom.)

I also learned that -- as I suspected -- AMD has their own version of the bloody thing. Apparently theirs is a bit less scary than Intel's since you can ostensibly disable it, but i don't believe that because spy agencies exist and people are power-hungry and corrupt as hell when they get it.

For those who don't know what the IME is, it's hardware godmode. It's a black box running obfuscated code on a coprocessor that's built into Intel cpus (all Intell cpus from 2008 on). It runs code continuously, even when the system is in S3 mode or powered off. As long as the psu is supplying current, it's running. It has its own mac and IP address, transmits out-of-band (so the OS can't see its traffic), some chips can even communicate via 3g, and it can accept remote commands, too. It has complete and unfettered access to everything, completely invisible to the OS. It can turn your computer on or off, use all hardware, access and change all data in ram and storage, etc. And all of this is completely transparent: when the IME interrupts, the cpu stores its state, pauses, runs the SMM (system management mode) code, restores the state, and resumes normal operation. Its memory always returns 0xff when read by the os, and all writes fail. So everything about it is completely hidden from the OS, though the OS can trigger the IME/SMM to run various functions through interrupts, too. But this system is also required for the CPU to even function, so killing it bricks your CPU. Which, ofc, you can do via exploits. Or install ring-2 keyloggers. or do fucking anything else you want to.

tl;dr IME is a hardware godmode, and if someone compromises this (and there have been many exploits), their code runs at ring-2 permissions (above kernel (0), above hypervisor (-1)). They can do anything and everything on/to your system, completely invisibly, and can even install persistent malware that lives inside your bloody cpu. And guess who has keys for this? Go on, guess. you're probably right. Are they completely trustworthy? No? You're probably right again.

There is absolutely no reason for this sort of thing to exist, and its existence can only makes things worse. It enables spying of literally all kinds, it enables cpu-resident malware, bricking your physical cpu, reading/modifying anything anywhere, taking control of your hardware, etc. Literal godmode. and some of it cannot be patched, meaning more than a few exploits require replacing your cpu to protect against.

And why does this exist?
Ostensibly to allow sysadmins to remote-manage fleets of computers, which it does. But it allows fucking everything else, too. and keys to it exist. and people are absolutely not trustworthy. especially those in power -- who are most likely to have access to said keys.

The only reason this exists is because fucking power-hungry doucherockets exist.

For those considering a job in Software Development ...

I want Gordon Ramsey to start a IT program in the same fashion as Hotel Hell and Kitchen Nightmares

He'll sit at a desk with a laptop, examining code as if he's eating food, venting frustrations and screaming insults out loud

Then he'll have a talk with the team and see how they work on a day

After that he'll go into the freezer (server room) and scream at mold and cockroaches

Then comes the intervention where we discover that the PM is still grieving about the death of his original programming language and the team loves him but thinks he should move on

The next day the development studio is modernised and has a candy bar, tennis table and everyone is forced to use linux on their new macbooks

Then we experience a good day where everything is great and velocity is through the roof

Then Gordon leaves and everything is shit again

$.ajax({});

We have a bunch of white people in human resources that are trying to hire "diverse" people because the company sets HR diversity targets. Which is an inherently racist way of hiring someone.

I am told to interview this guy who claims to have Angular experience. Before the interview I ask to see a form that he has built in Angular. He sends me a repo which is ripped off of an open source project and has the readme and git commits removed. A quick web search shows that it isn't his work. He shows up to the interview and I find out he is from a Southern African country. I deliberately ask some questions about code that I can see he didn't write that I prepared ahead of time. He lies to me and tells me all about how he wrote it which showed me that he has no idea what the code does. I tell HR they better not hire him because he was very comfortable lying to me, and I'm confident that he doesn't understand any of the code that he showed me. I do not trust this guy and would never choose to work with him. HR lady says "Ah okay."

Today he walks in with a big grin on his face. HR lady fucking hired this guy. I can see his monitors from my desk and he spent his whole first day looking at a soccer website on his second monitor. I call up HR, "Why would you even ask me to interview him if you refuse to listen to my feedback?". Lady tells me "You need to be open minded about diversity. Probably most of the things you observed were either cultural differences or language barrier." I tell her definitely not. He lied to me multiple times, and he took credit for other people's work." She tells me that they will keep an eye on me because I'm not being open to diversity.

Are you kidding me? This white lady is literally stereotyping me as a racist because I'm white.

So this fucking HR lady called me a racist because she decided to hire someone that we shouldn't trust. Then she put this asshat on my project. Now I have to be cautious about my position because HR is "watching" my racist ass. Even though I am literally the only one on the development team that is white and speaks English as my first-language. I called a team meeting before the on-boarding is over so I can tell the other developers what is happening. We restructured our code review process so that I will never give him feedback. Then when the time comes that he slips up the "diverse" developers will kick him out so I won't be reprimanded as a "racist".

This company that I work for is a special kind of stupid.

continued…
I'm In Canada. A woke HR lady hires an African guy despite him plagiarizing code and lying through an interview. First day he surfs soccer websites so I confront it and HR lady basically calls me a racist and to watch my back.

A second African new-hire comes into the office today and he seems quite capable in an area of specialization for our team. So I ask if we can have him on our team because he has skills. The exec decides to look at the costing for him and goes, "HOLY SHIT WHY ARE WE PAYING ANYONE THAT MUCH?" She looks at the résumé of the new guy and finds out that he is only at intermediate level in his specialization. So I say, "It could be worse. The other guy flat out lied through his interview and he got hired anyway." I forward the emails where I recommended against hiring the other guy and why.

My exec, who is a company stakeholder, opens the pricing list for recent hires. It is obvious that if you are not not white you get paid way above market value for your skill level. Exec is pissed off on a level I never knew was possible.

We make a call from the board room only to find out that the head of HR (also an executive) is driving this. My exec tells me to give her the room. The yelling was so loud everyone could hear what was said from outside the boardroom. At one point the HR lady says, "Just because we could get them cheaper doesn't mean that we should… We pay that much because it is 'the right thing to do'." My executive goes completely silent for a few seconds then in a super aggressive way says.

"…I am going to have your FUCKING head for this. Then I will make sure that you NEVER get a job in HR again for the rest of my natural life. ONLY ONE of us will survive this. YOU are the one pissing away profit. So get ready because I'm going to drown you and your team like a bag full of unwanted puppies." Then she hung up the Polycom. She came out about a minute later and kicked the office manager out of his office and sat there all day making calls and sending emails.

https://devrant.com/rants/2337768/...

Here's a tip to caffeinated-beverages lovers.

People often make this mistake with coffee.. They take a cup of coffee after lunch and expect it will make them productive and concentrated immediately. That's BS. Wait for the pee.

Digestion takes ~27% of your body energy molecules [ATP], so you will anyway be sleepy.

When you ingest a cup of coffee you ingest a warm beverage. The warmth will most likely make you sleepy and the sleepiness might last 5 to 15 minutes.

Caffeine in the coffee acts as diuretic - it makes your kidney filter blood more aggresively. As a result 20-40minutes after ingestion you will want to pee.

When you want to pee it's an obvious sign the caffeine is working. Now you should be productive.

Brain [cerebrum] uses glucose molecules for energy rather than ATP, like the rest of the body does. So for the best effect:
- have lunch
- have coffee with sugar during or right after the lunch [do not drink coffee if your stomach is empty!! Ulcers, gastritis, refluxes - that's your future if you do]
- wait ~30 minutes or until you pee
- go to do your work.

This way you will not be working sleepy and your brain will have enough pure glucose to operate on [sugar is just 2x glucose molecules bound together]

This facts are killing me

"During his own Google interview, Jeff Dean was asked the implications if P=NP were true. He said, "P = 0 or N = 1." Then, before the interviewer had even finished laughing, Jeff examined Google’s public certificate and wrote the private key on the whiteboard."

"Compilers don't warn Jeff Dean. Jeff Dean warns compilers."

"gcc -O4 emails your code to Jeff Dean for a rewrite."

"When Jeff Dean sends an ethernet frame there are no collisions because the competing frames retreat back up into the buffer memory on their source nic."

"When Jeff Dean has an ergonomic evaluation, it is for the protection of his keyboard."

"When Jeff Dean designs software, he first codes the binary and then writes the source as documentation."

"When Jeff has trouble sleeping, he Mapreduces sheep."

"When Jeff Dean listens to mp3s, he just cats them to /dev/dsp and does the decoding in his head."

"Google search went down for a few hours in 2002, and Jeff Dean started handling queries by hand. Search Quality doubled."

"One day Jeff Dean grabbed his Etch-a-Sketch instead of his laptop on his way out the door. On his way back home to get his real laptop, he programmed the Etch-a-Sketch to play Tetris."

"Jeff Dean once shifted a bit so hard, it ended up on another computer. "

Here’s a poster with a super short description of each one to help you keep track and find some new useful Linux tools.

Thank me later....

So someone invaded my workstation and did this on my Slack Status -.-"