I was doing some sentiment analysis on social comments on banks back in the day. I found out that while most banks had a positive feedback rate of around 70% - 80%, HSBC only scored a mere 31% and most comments are about their shitty card issuance service

@johnmelodyme it is this line of thought of you that give employers the false impression that developers are magicians who can pull out a codebase from thin air when tossed a coin. We work as hard as any other profession. If our effort are not respected, the employers can suck a fat dick and search for another mule to carry their shits.

Please, have respect for your own expertise and well-being.

@johnmelodyme if someone offers me 1000 bucks a month to build two different mobile app I'd tell them to go finish masturbating before talking to me.

a bunch of people at my place use a single character password for ubuntu login, cuz "convenience"

just stop ++ meme posts then

imho the strong point of vim is their editing motions. Modal editing may sound like a lot of work, but one you get used to it it's actually really natural

Setting up code navigation and completion on vim is actually a lot of work. I just use vim-mode on Jetbrains IDEs instead

try to use scoped styling for your module, don't touch the others, do your jobs, run away as fast as you can

to be fair, the project owners kinda bought their own doom when they allow devs to have freedom of choices

@comfycoding the fact that non tech companies still vastly use windows xp - 7 and outdated microsoft office just really show that these ppl actually don't give a shit about security, they just don't wanna use something they are not familiar with.

@electrineer yeah well to be honest, Linux GUI app are not known to be efficient and bug free. If you are running linux, just go cli i guess

yeah until you had to spend some few hours finding out why the program just randomly broke down in prod, said you can't call a_random_string.lower() because a_random_string was, in fact, a tuple.

You saw that, a_random_string is assigned with the result from a 150 lines function that a coworker of you wrote. You fired up the debugger, hoping to catch where the function return a tuple. However, the bug would only surface in a few rare edge cases. You spent a whole fucking hour trying to look the buggy input only to find out that, a return statement was:

return result,

instead of:

return result

Fuck lazy ass devs telling us to use dynamically typed language because they are "faster to write", they should be tried in a fucking court

Also to be honest, most of the hard to read codes I've ever come across actually had really simple working principle, but the writers was just really having to abuse the language syntactic sugars.

Have you ever came across a python function consisting of a single line spanning 200 characters across, all of them are just list and dict comprehension expressions.

@FranzFerdinand then it should be the tech leads' faults for not enforcing code review.

@electrineer it's not actually about issues, but jetbrains stuffs are known for hogging 100% resources to randomly rebuild indices every 10 minutes. How could you expect that they would run smoothly on a VM.

IMHO ppl should be allowed to write messy code if they are in a hurry, but only if their tech leads require them to fix their shits before working on other stuffs

bro what do you expect, running GUI apps in VM and demanding good performance?