Let me tell you how shit flies in Aerospace&Defense companies in certain place in on earth

1. Your dev. PC is isolated from the internet. You can not download any software/library etc directly. "Legal" way takes literally days and you must all effort for it to work. I will not discuss the details of legal way but it is not asking IT team to download it for you, you do it yourself.

2. You use an archaic requirement standard that is somehow used by all other similar companies too. These companies f*ck each other in the arse when they are working on projects together(hiding details from each other which is necessary most of the times etc.) but they were kind to each other when it came to share shitty req. standard.

3. When you try to switch to new requirement standard, you waste weeks only to amend the old one, because everyone is using old one for all projects, so changing it would upset old guards in the company(which are people works in same project for 10 years, no personal development)
4. You came 1 minutes late, you fill the "minutely permission" form.

5. You already work long hours per day and they remove your small breaks during day, because developers use those breaks longer than intended(I wonder what might be the reason...)

6. A technology can not be adopted into current projects even it has objective advantages proven many times in the outer world, because old guards(developers), IT team and configuration management guys(poor man's dev ops role sometimes) can not change their ways.

I hate this shit...

Mgmt: We need performance metrics' comparison for those 2 tests ASAP, we'll ping you every 5 minutes

AWS Cloudwatch: *unusually slow - takes ~2 minutes to add/remove a metric or change the timeframe*

Me: *fuck*

AWS Autologout: "Let me just intervene here right before you take that screenshot that took you 1.5 hours to filter out..."

"four million dollars"

TL;DR. Seriously, It's way too long.

That's all the management really cares about, apparently.

It all started when there were heated, war faced discussions with a major client this weekend (coonts, I tell ye) and it was decided that a stupid, out of context customisation POC had that was hacked together by the "customisation and delivery " (they know to do neither) team needed to be merged with the product (a hot, lumpy cluster fuck, made in a technology so old that even the great creators (namely Goo-fucking-gle) decided that it was their worst mistake ever and stopped supporting it (or even considering its existence at this point)).

Today morning, I my manager calls me and announces that I'm the lucky fuck who gets to do this shit.

Now being the defacto got admin to our team (after the last lead left, I was the only one with adequate experience), I suggested to my manager "boss, here's a light bulb. Why don't we just create a new branch for the fuckers and ask them to merge their shite with our shite and then all we'll have to do it build the mixed up shite to create an even smellier pile of shite and feed it to the customer".

"I agree with you mahaDev (when haven't you said that, coont), but the thing is <insert random manger talk here> so we're the ones who'll have to do it (again, when haven't you said that, coont)"

I said fine. Send me the details. He forwarded me a mail, which contained context not amounting to half a syllable of the word "context". I pinged the guy who developed the hack. He gave me nothing but a link to his code repo. I said give me details. He simply said "I've sent the repo details, what else do you require?"

1st motherfucker.

Dafuq? Dude, gimme some spice. Dafuq you done? Dafuq libraries you used? Dafuq APIs you used? Where Dafuq did you get this old ass checkout on which you've made these changes? AND DAFUQ IS THIS TOOL SUPPOSED TO DO AND HOW DOES IT AFFECT MY PRODUCT?

Anyway, since I didn't get a lot of info, I set about trying to just merge the code blindly and fix all conflicts, assuming that no new libraries/APIs have been used and the code is compatible with our master code base.

Enter delivery head. 2nd motherfucker.

This coont neither has technical knowledge nor the common sense to ask someone who knows his shit to help out with the technical stuff.

I find out that this was the half assed moron who agreed to a 3 day timeline (and our build takes around 13 hours to complete, end to end). Because fuck testing. They validated the their tool, we've tested our product. There's no way it can fail when we make a hybrid cocktail that will make the elephants foot look like a frikkin mojito!

Anywho, he comes by every half-mother fucking-hour and asks whether the build has been triggered.

Bitch. I have no clue what is going on and your people apparently don't have the time to give a fuck. How in the world do you expect me to finish this in 5 minutes?

Anyway, after I compile for the first time after merging, I see enough compilations to last a frikkin life time. I kid you not, I scrolled for a complete minute before reaching the last one.

Again, my assumption was that there are no library or dependency changes, neither did I know the fact that the dude implemented using completely different libraries altogether in some places.

Now I know it's my fault for not checking myself, but I was already having a bad day.

I then proceeded to have a little tantrum. In the middle of the floor, because I DIDN'T HAVE A CLUE WHAT CHANGES WERE MADE AND NOBODY CARED ENOUGH TO GIVE A FUCKING FUCK ABOUT THE DAMN FUCK.

Lo and behold, everyone's at my service now. I get all things clarified, takes around an hour and a half of my time (could have been done in 20 minutes had someone given me the complete info) to find out all I need to know and proceed to remove all compilation problems.

Hurrah. In my frustration, I forgot to push some changes, and because of some weird shit in our build framework, the build failed in Jenkins. Multiple times. Even though the exact same code was working on my local setup (cliche, I know).

In any case, it was sometime during sorting out this mess did I come to know that the reason why the 2nd motherfucker accepted the 3 day deadline was because the total bill being slapped to the customer is four fucking million USD.

Greed. Wow. The fucker just sacrificed everyone's day and night (his team and the next) for 4mil. And my manager and director agreed. Four fucking million dollars. I don't get to see a penny of it, I work for peanut shells, for 15 hours, you'll get bonuses and commissions, the fucking junior Dev earns more than me, but my manager says I'm the MVP of the team, all I get is a thanks and a bad rating for this hike cycle.

4mil usd, I learnt today, is enough to make you lick the smelly, hairy balls of a Neanderthal even though the money isn't truly yours.

Removing a kiwi tree is like unsubscribing every single spam you receive and hoping they don't ever come back.

think I'm starting to get why the c/c++ people are all crazy

I wanted to upgrade something so I wrote it then had to plug in the new version in 7 different crates. cool well after dozens of different file changes I found like 3 bugs and figured hey ok maybe some small edge case bug fixes and now I'm just frustrated because nothing is working and also did I mention I have like 3 deprecated crates but I haven't had a moment to rest to deprecate them fully and remove them and it's all massively annoying me

I keep just rewriting things because it's easier than changing the static typing system everywhere, but no matter what I do I just end up in more changing of the static typing system, repeat

I think I might just end at a non working codebase and lock myself up for 3 days and take some drugs and see what happens until either I pass out from lack of sleep and wake up not caring, someone finds me and takes me away, or I finally have a working product

things can't be done in chunks I guess

cuz if it works in isolation then you stress test it and it works then you plug it into the live system and heyyo look it doesn't because you didn't stress test these edge cases enough and now everything is broken and who wants to revert like 2 hours of stupid secretary work because StATiC TyPe SysTeM. so what my stress tests need to be the live system? and speaking of tests I keep have to go back to older tests and keep updating them every time the damned static type system updates so I don't want more tests

the irony in all this is suddenly for once in my life I had this funny thought of "whoa, remember when people said coding wasn't for them?". I mean if I keep shooting myself in the foot does end up feeling like a me problem. I still think like a damned computer though. literally the thing i've always been best at so I'm just laughing at the ridiculousness

(maybe it's the brain damage, let's be fair to myself)

wanted to watch a horror movie with the bf for a few days and the guy is a narcoleptic. told him I wanted to today but now look at me, I wanna lock myself in a room until I solve my disaster so how am I supposed to enjoy a movie, and do I just ditch what I'm doing and hope I give a shit later or do I blow him off? fuuuuck why

The data at the bottom are statistics regarding my key presses. It's literally every key pressed on this laptop since 2024-12-08. Since that date I entered a total of unique 925450 unique inputs. I did 4751951 keyboard inputs.

I know from 595 hours exactly what i've done for tasks (described by LLM based on my keylog data).

I type 107 lines per hour on average (return presses) based on 595 hours. With that logic, i did around 63925 lines.

I'm not very happy with the statistics, especially not because backspace is a hardcore first. Now, while i'm typing i'm focusing on how much I use it and it's not a lot at all.

But the thing is, if you remove abcdef, you have one a, one b, but six times back space. And these are real presses - not keyboard repeats. Also abcdef will be counted by the tag counter as a whole. Everything is a tag until it sees a new line or a white space or some punct.

Funny is that there are completely different keys on the list than I expected. You're so you used to those keys that you don't even notice using them.

I'm almost considering to add a sound under the backspace button to teach myself WHEN i use it and try to avoid it.

The key logger database is now 346Mb. Some overhead because every keypress takes around 40 chars of description (timestamp, press type, char, input device).

Creating statistics for the tags (unique words typed) takes several minutes. Already rewriting that part to C. The stats are made by python, the key logs with C.

I'm just shocked, I used 144644 times a key that I think not to use that much? :P How retoorded can you be. Imagine if i actually fixed typo's :P

But based on these keys you can see that i'm mainly working in terminal / vim. The 'i' for insert for example, typed so many times. The 'x' for save+quit. The '0' to go to beginning of line.

Did you expect that these buttons would've been the most used?

#0 BACKSPACE is pressed 144644 times (15.63% of total input)
#1 UP is pressed 92711 times (10.02% of total input)
#2 LEFT_SHIFT is pressed 73777 times (7.97% of total input)
#3 ENTER is pressed 63883 times (6.9% of total input)
#4 DOWN is pressed 56838 times (6.14% of total input)
#5 TAB is pressed 43635 times (4.72% of total input)
#6 RIGHT is pressed 37710 times (4.07% of total input)
#7 SPACE is pressed 34438 times (3.72% of total input)
#8 LEFT is pressed 26800 times (2.9% of total input)
#9 LEFT_CTRL is pressed 25402 times (2.74% of total input)
#10 LEFT_ALT is pressed 17289 times (1.87% of total input)
#11 I is pressed 12856 times (1.39% of total input)
#12 X is pressed 6106 times (0.66% of total input)
#13 A is pressed 5163 times (0.56% of total input)
#14 0 is pressed 4487 times (0.48% of total input)
#15 PAGEDOWN is pressed 4151 times (0.45% of total input)