Wtf, really??? Are they trying to liyerally KILL ME????

Got home from hospital today wth my family. Baby got sick. Wife also caught cold... Bad news. It was just me still healthy like a raddish [we have such saying].
So I got home. Started feeling somewhat funny. Sore thighs, feeling nauseaus, chilly, a bit dizzy.

10 minutes later I'm fucking trembling! It felt as of I was kicked put bare ass to -20C outside! I'm not exaggerating [probably made some typos.. Pls correct me] - i live where winters get like -35C. Everything around got like twice darker. And my lower teeth got itchy af [NOT the best feeling, trust me].

I must have caught cold too - I thought to myself, cuz I know what these sympthoms mean. I always have 'em all when I have fever. Since shivers are caused by rising fever I got my Microlife remote thermometer out of my drawer. Click, blue light, wait, beeep. 36.5C. Allright.. Maybe I got it wrong... Try again -- same result. Wife also gave a couple tries - nada. Nil. Nullpointerexception. Healthy like a pickle!

10 minutes later I couldn't stand the cold. Got under my blankets wife made some soup, tea,... I still have this analog thermometer, the one with quicksilver. Pop it into my armpit - jusyt in case. 10minutes later I take it out. It says 39,5 and rising. Try the microlife again. 36,5. WHAT THE FUCK?????????

If I weren't so fond of old-school stuff I'd be in a fucking ER now!!

Fuck you medical digital equipment made to be used at home! FUCK YOU!!

I'm pissed.

Do you folks kbow where could I get those q-silver thermometers? Just in case. They're already out of matket in my area for quite some time... For being dangerous [i give 'em that, okay?] and.... Lisen to this.... "unreliable"!

FUCK IT!

ARGH. I wrote a long rant containing a bunch of gems from the codebase at @work, and lost it.

I'll summarize the few I remember.

First, the cliche:
if (x == true) { return true; } else { return false; };
Seriously written (more than once) by the "legendary" devs themselves.

Then, lots of typos in constants (and methods, and comments, and ...) like:
SMD_AGENT_SHCEDULE_XYZ = '5-year-old-typo'

and gems like:

def hot_garbage
magic = [nil, '']
magic = [0, nil] if something_something
success = other_method_that_returns_nothing(magic)
if success == true
return true # signal success
end
end

^ That one is from our glorious self-proclaimed leader / "engineering director" / the junior dev thundercunt on a power trip. Good stuff.

Next up are a few of my personal favorites:

Report.run_every 4.hours # Every 6 hours
Daemon.run_at_hour 6 # Daily at 8am

LANG_ENGLISH = :en
LANG_SPANISH = :sp # because fuck standards, right?

And for design decisions...

The code was supposed to support multiple currencies, but just disregards them and sets a hardcoded 'usd' instead -- and the system stores that string on literally hundreds of millions of records, often multiple times too (e.g. for payment, display fees, etc). and! AND! IT'S ALWAYS A FUCKING VARCHAR(255)! So a single payment record uses 768 bytes to store 'usd' 'usd' 'usd'

I'd mention the design decisions that led to the 35 second minimum pay API response time (often 55 sec), but i don't remember the details well enough.

Also:
The senior devs can get pretty much anything through code review. So can the dev accountants. and ... well, pretty much everyone else. Seriously, i have absolutely no idea how all of this shit managed to get published.

But speaking of code reviews: Some security holes are allowed through because (and i quote) "they already exist elsewhere in the codebase." You can't make this up.

Oh, and another!
In a feature that merges two user objects and all their data, there's a method to generate a unique ID. It concatenates 12 random numbers (one at a time, ofc) then checks the database to see if that id already exists. It tries this 20 times, and uses the first unique one... or falls through and uses its last attempt. This ofc leads to collisions, and those collisions are messy and require a db rollback to fix. gg. This was written by the "legendary" dev himself, replete with his signature single-letter variable names. I brought it up and he laughed it off, saying the collisions have been rare enough it doesn't really matter so he won't fix it.

Yep, it's garbage all the way down.

Refactoring code of somebody who left and:

- Plagued the code with TYPOS (milions of them but ok I can live with those... to a certain point)
- Used global variables by default.... of course even where they're not needed
- Used comments only in parts of code where... well they're not needed, important ones are of course left out
- Did not indent code. 3..2..1... Did not FUCKING indent code properly and when he did... did WRONG!
- Instead of indentation he used commented line with multiple ==== signes.... so far top is 60 consecutive lines with olny ==== again no apparent pattern here
- Did not follow a fucking standard in variable naming... no camle casing... there are varaibles assigned multiple times to "temp" variables without no reason just for the sake of wasting resources on the system I guess

This is just the beginning of the review but I already want to change job, die, scream, cry... not in any specific order.

Hey Root, remember that super high-priority ticket that we ignored for five months before demanding you rewrite it a specific way in one day?

Yeah, the new approach we made you use broke the expected usecases, and now the page is completely useless to the support team and they're freaking out. Drop everything you're doing and go fix it! Code-complete for this release is tonight! -- This right after "impacting our business flow" while being collapsed on the fucking floor.

Jesus FUCKING christ, what the fuck is wrong with these people?

If I dropped the ball on a high-priority ticket for two weeks, I'd get fired, let alone for five fucking months.

If I was a manager and demanded a one-day rewrite I can only imagine the amount of chewing out I'd receive, especially on something high-priority.

And let's not forget product ownership: imagine if I screwed up feature planning for someone so badly I made them break a support tool in production. I'd never hear the end of it.

Fucking double standards.

And while I'm at it. Some of the code I've seen in this codebase is awful. Uncommented spaghetti, or an unreadable mess with single-letter variables, super-tightly coupled modules so updates are nearly impossible, typos in freaking constants added across sixty+ files, obviously-incorrect comments, ... . I'll have to start posting snippets to show them off. But could I get away with any of it? ha. Hell no. My code must be absolutely perfect. I hear about any and every flaw, doesn't matter how minor, and nothing can go out until everything is just so.

Hell, I even hear about flaws in other peoples' code during my code reviews. Why? Because I should have fixed it, that's why. But if I do, I get yelled at for "muddying the waters."

Just. JESUS FUCKING CHRIST.

It's like playing a shell game where no matter which shell I pick (or point to their goddamn sleeve where they're clearly hiding it), I get insulted for being so consistently useless, and god damn, how can I never find the fucking pea or follow the damned rules? I'm so terrible and this is why "nobody trusts me." Fuck you.

I'll tell you why I can't find your damned pea: IT'S RATTLING INSIDE YOUR FUCKING HEADS, you ASSHOLE FUCKING IMBECILES.

That's right: one pea among the lot of them.

goddamn I am fucking pissed off.

typos are ok if you can still understand what one is trying to say.

if your typos interfere with understanding, THEN FUCKING CORRECT THEM.

I'M TIRED OF NOT BEING ABLE TELL IF YO MEANT "…" OR "." WHEN YOU TYPE ".."

DID YOU FUCKING PRESS IT TWICE BY ACCIDENT OR DID YOU MEAN TO TYPE THREE PERIODS?

FUCK YOUUUUUU

Today on "How the Fuck is Python a Real Language?": Lambda functions and other dumb Python syntax.

Lambda functions are generally passed as callbacks, e.g. "myFunc(a, b, lambda c, d: c + d)". Note that the comma between c and d is somehow on a completely different level than the comma between a and b, even though they're both within the same brackets, because instead of using something like, say, universally agreed-upon grouping symbols to visually group the lambda function arguments together, Python groups them using a reserved keyword on one end, and two little dots on the other end. Like yeah, that's easy to notice among 10 other variable and argument names. But Python couldn't really do any better, because "myFunc(a, b, (c, d): c + d)" would be even less readable and prone to typos given how fucked up Python's use of brackets already is.

And while I'm on the topic of dumb Python syntax, let's look at the switch, um, match statements. For a long time, people behind Python argued that a bunch of elif statements with the same fucking conditions (e.g. x == 1, x == 2, x == 3, ...) are more readable than a standard switch statement, but then in Python 3.10 (released only 1 year ago), they finally came to their senses and added match and case keywords to implement pattern matching. Except they managed to fuck up yet again; instead of a normal "default:" statement, the default statement is denoted by "case _:". Because somehow, everywhere else in the code _ behaves as a normal variable name, but in match statement it instead means "ignore the value in this place". For example, "match myVar:" and "case [first, *rest]:" will behave exactly like "[first, *rest] = myVar" as long as myVar is a list with one or more elements, but "case [_, *rest]:" won't assign the first element from the list to anything, even though "[_, *rest] = myVar" will assign it to _. Because fuck consistency, that's why.

And why the fuck is there no fallthrough? Wouldn't it make perfect sense to write

case ('rgb', r, g, b):
case ('argb', _, r, g, b):
case ('rgba', r, g, b, _):
case ('bgr', b, g, r):
case ('abgr', _, b, g, r):
case ('bgra', b, g, r, _):

and then, you know, handle r, g, and b values in the same fucking block of code? Pretty sure that would be more readable than having to write "handeRGB(r, g, b)" 6 fucking times depending on the input format. Oh, and never mind that Python already has a "break" keyword.

Speaking of the "break" keyword, if you try to use it outside of a loop, you get an error "'break' outside loop". However, there's also the "continue" keyword, and if you try to use it outside of a loop, you get an error "'continue' not properly in loop". Why the fuck are there two completely different error messages for that? Does it mean there exists some weird improper syntax to use "continue" inside of a loop? Or is it just another inconsistent Python bullshit where until Python 3.8 you couldn't use "continue" inside the "finally:" block (but you could always use "break", even though it does essentially the same thing, just branching to a different point).

So, the reason I couldn't save screenshots to ~/Screenshots is that the directory doesn't exist.

But ~/Screenschots does

You realize that the ERP software you use at your company is shit when:
- there is no service-side ERP backend handling requests
- the whole permission system is client-side (!)
- every client directly connects to the MSSQL database with a supervisor user (stored in plain text in a local config file)
- the MSSQL database contains tables with:
- typos
- names like "contract" but then also "contracts"
- mixed german and english words
- the multiple-business-unit implementation uses 4 columns named "Layer 1, Layer 2, Layer 3, Layer 4" in EACH table
- you find out that the ERP software is created with a fucking "software creation tool"
- there is no API, so you have to program one yourself to use for services

Yet, they charge us shit ton of money for their broken ass software.

I spend 1 day debugging why I can't connect to my neo4j database. I reinstalled neo4j, I tweaked the configs, I still could not connect from my web application. The I tried to copy the url where to request are being send to into curl.

The error message: "Could not resolve host: locahost"

LOCAHOST. FUCKING LOCAHOST

FUCK ME AND MY ABILITY TO WRITE ONE OF THE MOST USED WORDS IN NETWORKING.

Been working on a new project for the last couple of weeks. New client with a big name, probably lots of money for the company I work for, plus a nice bonus for myself.

But our technical referent....... Goddammit. PhD in computer science, and he probably. approved our project outline. 3 days in development, the basic features of the applications are there for him to see (yay. Agile.), and guess what? We need to change the user roles hierarchy we had agreed on. Oh, and that shouldn't be treated as extra development, it's obviously a bug! Also, these features he never talked about and never have been in the project? That's also a bug! That thing I couldn't start working on before yesterday because I was still waiting the specs from him? It should've been ready a week ago, it's a bug that it's not there! Also, he notes how he could've developes it within 40 minutes and offered to sens us the code to implement directly in our application, or he may even do so himself.... Ah, I forgot to say, he has no idea on what language we are developing the app. He said he didn't care many times so far.

But the best part? Yesterday he signales an outstanding bug: some data has been changed without anyone interacting. It was a bug! And it was costing them moneeeeey (on a dev server)! Ok, let's dig in, it may really be a bug this time, I did update the code and... Wait, what? Someone actually did update a new file? ...Oh my Anubis. HE did replace the file a few minutes before and tried to make it look like a bug! ..May as well double check. So, 15 minutes later I answer to his e-mail, saying that 4 files have been compromised by a user account with admin privileges (not mentioning I knee it was him)... And 3 minutes later he answered me. It was a message full of anger, saying (oh Lord) it was a bug! If a user can upload a new file, it's the application's fault for not blocking him (except, users ARE supposed to upload files, and admins have been requestes to be able to circumvent any kind of restriction)! Then he added how lucky I was, becausw "the issue resolved itself and the data was back, and we shouldn't waste any more yime.on thos". Let's check the logs again.... It'a true! HE UPLOADED THE ORIGINAL FILES BACK! He... He has no idea that logs do exist? A fucking PhD in computer science? He still believes no one knows it was him....... But... Why did he do that? It couldn't have been a mistake. Was he trying to troll me? Or... Or is he really that dense?

I was laughing my ass of there. But there's more! He actually phones my boss (who knew what had happened) to insult me! And to threaten not dwell on that issue anymore because "it's making them lose money". We were both speechless....

There's no way he's a PhD. Yet it's a legit piece of paper the one he has. Funny thing is, he actually manages to launch a couple of sort-of-nationally-popular webservices, and takes every opportunity to remember us how he built them from scratch and so he know what he's saying... But digging through google, you can easily find how he actually outsurced the development to Chinese companies while he "watched over their work" until he bought the code

Wait... Big ego, a decent amount of money... I'm starting to guess how he got his PhD. I also get why he's a "freelance consultant" and none of the place he worked for ever hired him again (couldn't even cover his own tracks)....

But I can't get his definition of "bug".
If it doesn't work as intended, it's a bug (ok)
If something he never communicated is not implemented, it's a bug (what.)
If development has been slowed because he failed to provide specs, it's a bug (uh?)
If he changes his own mind and wants to change a process, it's a bug it doesn't already work that way (ffs.)
If he doesn't understand or like something, it's a bug (i hopw he dies by sonic diarrhoea)

I'm just glad my boss isn't falling for him... If anything, we have enough info to accuse him of sabotage and delaying my work....

Ah, right. He also didn't get how to publish our application we needes access to the server he wantes us to deploy it on. Also, he doesn't understand why we have acces to the app's database and admin users created on the webapp don't. These are bugs (seriously his own words). Outstanding ones.

Just..... Ffs.

Also, sorry for the typos.

Ive got this colleague who knows so much about cloud services, networking etcetera, but 90% of the code he writes I have to rewrite in a way.

So many typos that classnames become unreadable and not understandable.
Small pieces of code that breaks so many other pieces of code.
And code which isnnt needed because it doesnt do shite. "o = (o==null?null: o)" (this is the exact thing he wrote (spacing included))

Sometimes it takes me 6 hours to find the source of an issue because he changed something. Everything I change I confront him about because they are things that can be avoided by rereading the code written.

Fucking doesnt wanna learn....

<iframe src="index5.jsp">

Hello Mr. Tester Guy, At last you finally saw this. I don't know how to say this but I'm sick and tired of your bs!

You wanna know what’s wrong with everything?

I could tell you what’s wrong with this country – or at least I could give you my opinion about it. I could tell you what’s wrong with “the church” (as though all churches are guilty of what some churches do). But I can't fucking tell what your problem is!

Let’s get pragmatic for a second.

I have worked tirelessly for over only God knows how long, trying to get this platform running on all browsers in this world even on obsolete ones (IE7,6,5,4,3... to the shithole).

You are heartless!
After all these pain you still rant about index pages not rendering equally in time across all browsers.
You are a demon from hell!

I could go on, but with your degree in Q.A. (like measuring the margin between two images using a tape-rule or looking for typos in a dummy text) you should understand my point fucking cunt.

I realize I just ranted a little, but I’d like to think that this rant is more of an attempt to end the useless practice of ranting about your moronic findings on this platform.

The devil awaits you in hell, bitch!

</iframe>

9000 internet cookie points to whoever figures out this shit:

I'm trying to import a secret gpg key into my keyring.
If I run "gpg2 --import secring.gpg" and manually type each possible password that I can think of, the import fails. So far, nothing unusual.
HOWEVER
If I type the same passwords into a file and run:
echo pwfile.txt | gpg2 --batch --import secring.gpg
IT ACTUALLY FUCKING WORKS

What the fuck??? How can it be that whenever I type the pw manually it fails, but when I import it from a file it works??
And no, it's not typos: I could type those passwords blindfolded from muscle memory alone, and still get them right 99% of the time. And I'm definitely not blindfolded right now.

BUT WAIT, THERE'S MORE!!

Suppose my pwfile.txt looks something like this:

password1
password2
password3
password4
password5
password6

Now, I'm trying to narrow it down and figure out which one is the right password, so I'm gonna split the file in two parts and see which one succeds. Easy, right?

$ cat pw1.txt
password1
password2
password3

$ cat pw2.txt
password4
password5
password6

$ echo pw1.txt | gpg2 --batch --import secring.gpg
gpg: key 149C7ED3: secret key imported

$ gpg2 --delete-secret-key "149C7ED3"
[confirm deletion]

$ echo pw2.txt | gpg2 --batch --import secring.gpg
gpg: key 149C7ED3: secret key imported

In other words, both files successfully managed to import the secret key, but there are no passwords in common between the two!!
Am I going retarded, or is there something really wrong here? WTF!

Do you guys remember the fun little joke utility called fuck that corrected typos?

While debugging an absurd 2s shell load time, I noticed today that the command it appends to .bashrc to _set a fucking alias_ takes almost 400ms to execute.

Fucking typos 😡

Clients are total assholes, we all know it, just sharing my another depressed instance.

> be me, freelancing.
> client sends in an image of a webpage
> le me gently ask "What is the functionality here since this has a form?"
> Client explains
> OK let's do this because I have other stuff to do as well.
> Sends in demo
> Client: "Numerous typos, send again"
> Okay, sends again.
> Client Rages: "This still has typos. I thought you were a good developer. You look like a has-been.

I promptly quit the project and tried to explain to him the difference between a "demo" and a finished project. He was supposed to check the functionality of the fucking form, which he didn't.

Got a call to finish the project, him explaining nobody is working for him for given budget, he can't afford anybody in this town (literally), and I am not going back.

Super late at night that it's pretty much morning, got another cup of coffee and now looking at my code trying to figure out where I fucked up, for hours and VSC doesn't show that I have any errors.... 4 hours later, still looking and I finally notice it.... I typed (options.lenght) instead of length...

Bought great book from this Spanish company on Drupal. The book is well structured and the examples are excellent. Just some typos that they mistranslate from Spanish.

But thought it was weird that the code examples were not available online. Sent them an email to request for them.

They answered that the code is not online beacuse their students have to remake the code using the book in their courses. And ask them if I was interested in the course.

Fuck them! They are using opensource code but their examples are not open source because of some elementary-level school mentality that their students might copy the code and somehow not learn well.

They are fucking adults ffs!

Ps: Even though their answer piss me off, they still have the best book I've read on Drupal.

You'd think I'd fucking learn by now to check for typos before going off on a tangent of over complicated reasons why something may not be working... Learning python/django for the first time, and have been trying to figure out how to run gunicorn... turns out I was typing myproject.wgsi rather than myproject.wsgi...

Though I suppose not knowing about how python modules work added to my confusion... still... ugh...

I just helped my friend setting up Laravel on her machine. The npm is giving me headache because of the fucking permission issue. WHY THE FUCK chmod DOESN'T WORK ON WINDOWS IF POWERSHELL RECOGNIZE THE COMMAND?? Then composer says that it cannot find the autoload.php. I thought it was another permission issue end up it's because composer fuck up installing on Windows. Wasted 2 hours for this shit.

Oh and the default language she uses is French. The keyboard layout is entirely different. French is totally awesome but the typos in command is getting really annoying. :(

I'm not saying Windows is bad for general use but I think it's a bad idea for developing non-Microsoft product on Windows. I don't understand how can one bear with so much shit on Windows. Most dev tools tutorials are written in Unix system so fucking get a Mac or Linux at least!