If Operating Systems Ran The Airlines

UNIX Airways
Everyone brings one piece of the plane along when they come to the airport. They all go out on the runway and put the plane together piece by piece, arguing non-stop about what kind of plane they are supposed to be building.

Air DOS

Everybody pushes the airplane until it glides, then they jump on and let the plane coast until it hits the ground again. Then they push again, jump on again, and so on ...

Mac Airlines

All the stewards, captains, baggage handlers, and ticket agents look and act exactly the same. Every time you ask questions about details, you are gently but firmly told that you don't need to know, don't want to know, and everything will be done for you without your ever having to know, so just shut up.

Windows Air

The terminal is pretty and colorful, with friendly stewards, easy baggage check and boarding, and a smooth take-off. After about 10 minutes in the air, the plane explodes with no warning whatsoever.

Windows NT Air

Just like Windows Air, but costs more, uses much bigger planes, and takes out all the other aircraft within a 40-mile radius when it explodes.

Linux Air

Disgruntled employees of all the other OS airlines decide to start their own airline. They build the planes, ticket counters, and pave the runways themselves. They charge a small fee to cover the cost of printing the ticket, but you can also download and print the ticket yourself. When you board the plane, you are given a seat, four bolts, a wrench and a copy of the Seat-HOWTO.html. Once settled, the fully adjustable seat is very comfortable, the plane leaves and arrives on time without a single problem, the in-flight meal is wonderful. You try to tell customers of the other airlines about the great trip, but all they can say is, "You had to do what with the seat?"

Client: "Hi, there's a problem with this link"
Me: "How odd, I'll take a look right away"

-- 19 minutes later --

Client: "Has this been fixed?"
Me: "I'm working on it currently"
Client: "OK please let us know when it's done"
Me: "I will do"

-- 2 minutes later --

Client: "Hi, is this done?"
Me: "I've just told you I will let you know as soon as it's done"

-- 5 minutes later --

Client: "Hi, sorry to hassle, but is this done yet?"
Me: *starts twitching*
Me: "I am working on it and I will let you know when it's done"
Client: "OK, well don't worry about it, it doesn't really matter"
Me: *explodes*

If programming languages where weapons...

1. C is an M1 Garand standard issue rifle, old but reliable.

2. C++ is a set of nunchuks, powerful and impressive when wielded but takes many years of pain to master and often you probably wish you were using something else.

3. Perl is a molotov cocktail, it was probably useful once, but few people use it

4. Java is a belt fed 240G automatic weapon where sometimes the belt has rounds, sometimes it doesn’t, and when it doesn’t during firing you get an NullPointerException, the gun explodes and you die.

5. Scala is a variant of the 240G Java, except the training manual is written in an incomprehensible dialect which many suspect is just gibberish.

6. JavaScript is a sword without a hilt.

7. Go is the custom made “if err != nil” starter pistol and after each shot you must check to make sure it actually shot. Also it shoots tabs instead of blanks.

8. Rust is a 3d printed gun. It may work some day.

9. bash is a cursed hammer, when wielded everything looks like a nail, especially your thumb.

10. Python is the “v2/v3” double barrel shotgun, only one barrel will shoot at a time, and you never end up shooting the recommended one. Also I probably should have used a line tool to draw that.

11. Ruby is a ruby encrusted sword, it is usually only used because of how shiny it is.

12. PHP is a hose, you usually plug one end into a car exhaust, and the other you stick in through a window and then you sit in the car and turn the engine on.

13. Mathematica is a low earth orbit projectile cannon, it could probably do amazing things if only anyone could actually afford one.

14. C# is a powerful laser rifle strapped to a donkey, when taken off the donkey the laser doesn’t seem to work as well.

15. Prolog is an AI weapon, you tell it what to do, which it does but then it also builds some terminators to go back in time and kill your mom

All credits go to Vicky from damnet.com

Me: *uploads pre-alpha images of game demo to twitter*

User: "That's a game? It looks like shit."

Me: "I was just showing off a test."

User: "No, like your entire game is garbage."

Me: "Okay? Don't play it."

User: "Also hacking is illegal, so you shouldn't be advertising it in your garbage game."

Me: *explodes into barely readable rant* 😭😭😭😭😭😭😭😭😭😭😭😭

When you get up from your desk and your entire work space explodes...

... you left your headphones in

Sorry for being late, stuffs came inbetween!

I have done a few privacy rants/posts before but why not another one. @tahnik did one a few days ago so I thought I'd do a new one myself based on his rant.

So, online privacy. Some people say it's entirely dead, that's bullshit. It's up to an individual, though, how far they want to go as for protecting it.

I personally want to retain as much control over my data as possible (this seems to be a weird thing these days for unknown reasons...). That's why I spend quite some time/effort to take precautions, read myself into how to protect my data more and so on.

'Everyone should have the choice of what services they use' - fully agreed, no doubt about that.

I just find one thing problematic. Some services/companies handle data in a way or have certain business models which takes the control which some people want/have over their data away when you communicate with someone using that service.

Some people (like me) don't want anything to do with google but even when I want to email my best fucking friend, I lose the control over that email data since he uses gmail.

So, when someone chooses to use gmail and I *HAVE* to email them, my choice is gone.

TO BE VERY CLEAR: I'm not blaming that on the users, I'm blaming that on the company/service.

Then for example, google analytics. It's a very good/powerful when you're solely looking at its functions.
I just don't want to be part of their data collection as I don't want to get any data into the google engine.

There's a solution for that: installing an addon in order to opt out.

I'm sorry, WHAT?! --> I <-- have to install an addon in order to opt out of something that is happening on my own motherfucking computer?! What the actual fuck, I don't call that a fucking solution. I'll use Privacy Badger + hosts files to block that instead.

Google vs 'privacy' friendly search engines - I don't trust DDG completely because their backend is closed/not available to the public but I'd rather use them then a search engine which is known to be integrated into PRISM/other surveillance engines by default.

I don't mind the existence of certain services, as long as they don't integrated you with data hungry companies/mass surveillance without you even using their services.

Now lets see how fast the comment section explodes!

Reads clients rambling description of app they want developed... Head explodes!

The newest *DD development trend: Panic Driven Development.

When your hexagonal domain driven serverless microservice architecture explodes in production and you don't know which one of the 50k components is failing.

My first job stared when i was 16 when i make my first power generator with some hardware stuff and c++.

I remember when it explodes one week later.

How to make a bomb:

Buy a note 7 [Even your OWN color]
Plug up
Wait
Enjoy

I hate fanboys. If ANYBODY is saying something against "their" company, they get upset and argue about it like little children. If your technology is shit, if your browser sucks, if your phone explodes, if your OS is slow, just admit it. I can't stand these fuckers thinking they have to defend themselves just cause a company released a shit product...

Friday 15:30
Prod explodes.

Typical...

Programmer: ..coding..

"Planet explodes"

Programmer: removes earbud:

"...what?"

Testing hell.

I'm working on a ticket that touches a lot of areas of the codebase, and impacts everything that creates a ... really common kind of object.

This means changes throughout the codebase and lots of failing specs. Ofc sometimes the code needs changing, and sometimes the specs do. it's tedious.

What makes this incredibly challenging is that different specs fail depend on how i run them. If I use Jenkins, i'm currently at 160 failing tests. If I run the same specs from the terminal, Iget 132. If I run them from RubyMine... well, I can't run them all at once because RubyMine sucks, but I'm guessing it's around 90 failures based on spot-checking some of the files.

But seriously, how can I determine what "fixed" even means if the issues arbitrarily pass or fail in different environments? I don't even know how cli and rubymine *can* differ, if I'm being honest.

I asked my boss about this and he said he's never seen the issue in the ten years he's worked there. so now i'm doubly confused.

Update: I used a copy of his db (the same one Jenkins is using), and now rspec reports 137 failures from the terminal, and a similar ~90 (again, a guess) from rubymine based on more spot-checking. I am so confused. The db dump has the same structure, and rspec clears the actual data between tests, so wtf is even going on? Maybe the encoding differs? but the failing specs are mostly testing logic?

none of this makes any sense.
i'm so confused.

It feels like i'm being asked to build a machine when the laws of physics change with locality. I can make it work here just fine, but it misbehaves a little at my neighbor's house, and outright explodes at the testing ground.

Okay, fuck it. I'm going to buy $20 worth of every penny crypto currency until one of them explodes making me a millionaire

This is big brain time

Damn, the food explodes?

You know what?
No you don't!
PHP decided 'in time memorial' to deprecate their 'split' function for another function called 'explode' that splits, oh sorry, that explodes a string.

Now you know something!

Went from a web developer (mostly front end, moderate back end experience) to now being a firmware developer for a backup product. *head explodes*

Just got into web development.

Y U NOT WORKING RIGHT?

How do you guys make really complex websites when I can even center an unordered list without the first child...

I write something like align-vertically: center;
And what does it do? NOTHING!
And if it does something, it mirrors the whole page, makes it all bright pink and then everything explodes and I'm alone in a dark void, only me and my PC are there and somehow I have access to the internet.
And then I look it up at stackoverflow and I'm like: Oh, ok, I'll do it this way then.
And it still doesn't work and does absolutly nothing!
So I'm trapped in this void of nothingness till the end of my days.
At least that's what it feels like.

Not planning for it at all, then see the service gain traction and traffic explodes through the roof.

Not gonna do that mistake again!

I just want to share this:

When I start working at my last job, I have little idea of what a unit test was.

My boss on one meeting said that unit testing will be mandatory (wich is ok and umderstandable).

Almost a *year* after that, no one still care about them. I see myself doing them the best I can, but I saw things like wrap the assertion line with "try / catch" to lie to the coverage and unit test percentage. Or in other cases directly uploading *manually* the code on the server without test at all.

And then, as the only developer who do the unit test ok I have to do the missing ones and repair the fake ones.

Then when something explodes the question all the managers love to ask "Did we had the testing?"

At least I quit... that job was some crazy shit, this is just one story of many.

Like that other time that my co-workers did not understand why I needed to do POJOs on an android app because the big bad JSON that the app used was working fine....

My company email:

- It's time for the monthly password change!
<writes the usual passwod>
- The password must be over 50 characters long!
<adds more letters>
- The password must have numbers!
<adds some numbers, though it's getting irritating>
- The password must have special characters!
<wtf?? Adds a pound character>
- The password must have at least 20 different special characters!
<da fuq???>
- The password must be at least 50 characters, only special characters and invisible tab/LF/CR characters and it must be changed daily!
<head explodes>
- Thank you! Now please sign in with your new password for 200 times per day.
<closes the laptop and starts using Remington type writer>

Usually these remainders start popping up during the 1st vacation day. When you return to the office, the account is already locked.

And then you wonder why people have the passwords written on a post-it or as a plain txt file in SkyDrive.

I found this on a wiki with Haskell Humor... it's interesting...

How to Shoot Your Self in the Foot With Haskell: Putting the unsafe in unsafePerformIO!

You shoot the gun, but the bullet gets trapped in the IO monad.
Couldn't match expected type 'Deer' against inferred type 'Foot'.
While compiling your program the compiler produces a type error long enough to overflow a kernel buffer, overwrite the trigger control register and shoot you in the foot.
After trying to decipher the type errors from the compiler, your head explodes.
After you've finally found a way to circumvent the type system and shoot yourself in the foot, Oleg appears out of nothing and shoots you in the foot for coming up with it before him.
You shoot the gun but nothing happens (Haskell is pure, after all).
Your foot is fine, until you try to walk on it, at which point it becomes mangled.
You have a shootFoot function which you've proven correct. QuickCheck validates it for arbitrary you-like values. It will be evaluated only when you end up at the hospital. You hope this doesn't come to pass, as it actually returns a bullet-ridden copy of yourself and you don't want to be garbage-collected.
foreign import ccall "shootparts.h shootfoot" shoot_foot :: Gun -> Programmer -> IO ()
shootSelfInFoot = unsafePerformIO . shoot . foot $ self -- Shoot self in foot 0 or more times depending on evaluation order
No instance for (Target Foot)
arising from use of `shoot' at SelfInflictedInjury.hs:1:0
Possible fix: add an instance declaration for (Target Foot)
In the expression: shoot foot
You go to shoot yourself in the foot but the bullet is in the ST monad and the gun is in the IO monad, so you can't.
You ask Haskell to shoot you in the foot but by the rules of lazy evaluation you don't need the result yet so it doesn't happen.
You decide to shoot yourself in the foot but get distracted devising a ballistics algebra and wondering if you can do the calculations in the type system.
You want to shoot yourself in the foot but realize there is no Gun datatype so use Arrows instead.
You shoot in the direction of your foot, but since you are inside the STM monad you can just retry until you figure out what to do.
You shoot yourself in the foot, but you are perfectly fine as long you just don't evaluate the foot.
You shoot yourself in the foot, but nothing happens unless you start walking.
Don't forget about memory consumption! If you don't look, the bullet causes heap overflow. If you look, the bullet causes stack overflow.
You *appear* to have deliberately shot yourself in the foot, and yet your program actually runs perfectly OK due to lazy evaluation. (So long as you remember to not look at your foot...)
You aim the gun at your foot, pull the trigger and remove the clip. When you look at your undamaged foot, the hammer clicks on an empty barrel.

when everything explodes on a Monday... past 5.pm 😑

I am a mechanical engineer first and my companies go to sysadmin second. So software developing isnt really my main field of expertise buuttt:

WHY IS SLOOPY SOFTWARE WRITING A VIABLE EXCUSE?

Story:
Yesterday i started to migrate some stuff from our old Win 2008 Server to the new 2016. Turns out there are some MS SQL Express Servers running. Quick check for what they are turns out that they are activly used. So far so good. For other reasons we have a new MSSQL 2017 Core Licence. So i thought, hey it would be nice to just move those 2012, 2008 and 2014 Express Servers to a real one that can use the entire machines capabilities.
After some try & error with exporting one of the softwares (where i had to elevate one the user rights to sysadmin for reasons) the entire system stopped working. I didnt deleted anything or changed anything! Well, i elevated user rights. After 2 hours of support call it turns out that the software stopped working cause i gave the database user sysadmin rights. I dont know enough about MSSQL to judge wether that is logical or not, but it sounds super illogical and i suspect sloopy software writing on the manufacturers part. One way or another, the excuse from the telephone support was "yeah, our software is a very fragile child"
Okay.
After i told all that my coworkers two of them were also "yeah, that is just how the [company] software is, you have to be careful with it"

Apparently it broke in the past for other minor stuff.
As an engineer i cannot build bridges that collapse when you use the left and the right lane at the same time. For an architect it isnt okay to build an house where the front door explodes when you open a window. It is not okay for a power tool to go out in a fireball when you accidently drill plastic with it. But for some weird reasons its socially acceptable for programs to be sloopy, buggy and only working under specific conditions. Since when is it okay for a car only to work when you know specific steps to make it run? Like, throwing your spare key in the gas tank, the kick the left wheel exactly three times and finally tapping the steering wheel 5 times left, 4 times right. What? That would be ridiculous? But that is exactly how that software works. You have to follow a specific step guide to make it work, EVERY TIME.

I. JUST. DONT. GET. IT

Is it just me, or are the media / journalists once again putting a stupidly unfair pessimistic spin on that SpaceX launch?

"SpaceX rocket launches but explodes shortly into flight"
"Musk's SpaceX big rocket explodes on test flight"
"SpaceX rocket explosion: None injured or killed"

They've said time and time again, it's the first test of a massively complex rocket that's bigger than anything that's ever gone before it, and success is just defined as "getting off the launch pad" and collecting data. They did that and then some.

But instead of spreading excitement about the data, the fact it launched, that it's a world first, etc. - it's all doom and gloom, implying that the whole thing was a failure and people could have died 🙄

And people wonder why I have a low opinion of journalists.

I have a cheap crappy drone and while not using it I hang it on the smoke detector. Neither the drone or the smoke alarm have batteries.

I glance up and see a light flashing, freak out, shoot the drone...lights still flashing and I realize it's the smoke detector. Fuck that, there's no batteries. I shoot the smoke alarm and it explodes...battery lands at my feet still intact...

...the alarm is dead, the drone is crying, the toaster is laughing and I can't figure out why the fuck I shot my drone and smoke detector but the toaster doesn't phase me.

(Some of this is actually true)

Ever work on a codebase that's so shitty, that if you do something in a generally accepted and expected way the entire product shits the bed? Cuz that's the situation I am in. Been working on the same fucking feature for like 4 sprints because it keeps being sent back because every time I adjust it to the shittiness that is currently in the baseline, someone changed something and it explodes again. And the worst part is that this is a well known and established problem. Basically every engineer, except the guy who wrote it of course, hates this system. Hates the baseline, and hates the platform. Yet I'm the one who is "losing trust" with the team, even though I get my shit up and running early all the time. They just break the foundation every time.

News headline:
Thief runs off with Galaxy Note 7 before it explodes moments later

I need someone to explain me this:

- whenever I work hard as fuck and stay on my purpose and fuckin grinding out all of my work being focused as fuck on it; EVERYONE SUDDENLY WANTS TO FUCKING TEXT ME. I AM BUSY. MY DAD WANTS TO TALK. MY MOM HAS QUESTIONS. MY DOG WANTS TO SHIT. MY FRIENDS WANT TO HANG OUT WITH ME AND FIND ME COOL. RANDOM GIRLS TEXT ME. RANDOM GIRLS WANT TO FUCK ME. MY PHONE EXPLODES FROM TEXTS AND NOTIFICATIONS. NUCLEAR DISTRACTIONS

- whenever i dont work anything, just lay on the couch to have some rest or when i feel depressed and lonely; NO ONE WANTS TO TEXT ME. PEOPLE TAKE HOURS OF FUCKING TIME TO RESPOND. THOSE WHO USED TO GIVE A FUCK TO SPAMBOMB ME WITH TEXTS NO LONGER GIVE A FUCK. I FEEL EVEN WORSE THEN. FUCK YOU AND FUCK EVERYONE WHO DISTURBS ME WITH DISTRACTIONS

Fucking shit for brains authors that think the digital world is a fantasy realm where everything can happen just to aid their story. Out of boredom i watched "scorpion" today, a tv series about a group of geniusses which are a special case task force.
They got a visitor from the government saying the servers from the federal reserve bank were encrypted with ransomware. I already twitched when they said the economic system would collapse if the servers were left inoperational for a few days. Then one guy got to his desk and "hacked" the fed network to check... he then tried to remove the malware but "it changed itself when observed". But they got the magical fingerprint of the device that uploaded it. In the end some non-programmers created the malware, but it is super fast and dangerous because it runs on a quantum computer which makes it hyper fast and dangerous. They got to the quantum computer which was a glowing cube inside another cube with lasers going into it and they had to use mirrors to divert the lasers to slow down that quantum thingy. And be careful with that, otherwise it explodes. In the end the anti-malware battled the malware and won, all in a matter of minutes.

This is a multimillion hollywood production. How can a movie this abusive to computer science even air on television? Shit like this is the reason people still think the cyberworld is some instable thing that can explode any second. It's not, it's an instable thing that can break down any second. I remember "ghost in the wires" and people had surreal imaginations about the internet already. Shit like this is why people stay dumb and think everything can be done in seconds. If i ever should encounter one of these idiots i tell him i have an app that can publish his browser history by taking a picture of his phone and watch his reaction.
Time to shuw down the tv and learn vim again.

there is nothing more annoying than plugging the usb cable to the real android device for debugging, but if you move that cable 1mm the whole fucking connection breaks, the beep sounds of connected/disconnected phone rings, the fucking laptop explodes, phone explodes, dick explodes, the house gets on fire, my dog gets on fire, i run out of house while burning in flames alive and the whole house fuckin explodes like a nuclear bomb

When the battery in your MacBook Pro explodes , buckling the trackpad and prying off the bottom 👍🏽

I hate React. I keep reading that people have problem of grasping it, but that's not the case for me. I get it, I understand it, but I hate with passion HOW it's done knowing how nice it's done elsewhere. What really triggers me is how ugly it looks, both from architecture and code level. To me it really say a lot when even code shown in documentation looks ugly, and while reading it you ask ourself constantly "why it's done this way?". When I read React being called an "elegant" solution something explodes in me. Did you saw Svelte? Vue? Damn, even Alpine.js?
I just cannot how overengineered this API is. Even doing simplest things there produces so much junk code written only because this is what library requires. Why? I feel like working with it is a punishment.
And scalability and maintainability? I've never seen large-scale projects more messed up than those wrote with React. And yes, you can blame teams working on them for lack of skills, but it is the library which encourages or not good practices also, and I've never seen such bad situation with other libraries/frameworks.

my company is "pivoting" way too goddamn fast; they are pulling devs from other projects and throwing them into something that is a fragile system (was supposed to be replaced already) and is using a completely different stack than most of them usually work with. they keep promising 3rd parties that we will knock out their requirements within a week or two, and as such they are pushing haphazardly merged feature branches into production with absolutely no regression testing.

then when shit explodes and operations grinds to a halt, they tell the half of the team that actually knows how the system works to drop everything and fix it, and leave the diverted devs to continue to develop shit based on requirements drawn on a cocktail napkin, and then they fucking push both the hotfixes and the newest features at the same time.

I probably have the most tribal knowledge at this company, and they are paying me ok, so it's enough for me to just pour some rye and suck it up for the time being and milk the gig. but this can't be sustainable, right? i'm passively looking around for other work, as I've already had enough being here for over 3 years, but i'm finding most places to be slow on the application/hiring process lately due to covid.

Edit: i think i used the wrong tag here, but what the fuck ever. i haven't figured out how to tag shit properly on any platform

Instead of using 2 dimensional arrays to represent tables, my supervisor implodes the arrays on a delimiter before loading them into the other arrays... then explodes them again when he needs to use them.

Why? "It's easier"

My backend devs are so explosive, whenever they release an api, the server explodes

Thinking of writing new books

"How to become obese in a week?"

And

"Race between your code and yourself. Who explodes first!"

IMAGE COMPRESSION QUESTION

lets say i upload a 100x100 photo from my android device. this image has a size of e.g. 2MB. not a lot. if i compress it then the size will be e.g. 300kB. cool. upload is thunderbolt for any internet speed.

lets consider this case. a random ass motherfucker decides it is cool to upload a 10000x10000 image that has a size e.g. 300MB. compressing this would be e.g. 150MB which is still a lot as fuck for one pic.

heres my question: where should the compression be handled? at backend (REST API server) or client (android image compression library)?

because if i try to send a 150MB pic to the server and their internet sucks but to be fucking honest even the best internet speed would take way too long to upload, is it better to do the compression on the backend or client?

or should i do compression in android? if i should do compression on client then should i;
1) do the compression on the main thread with a progress dialog to wait them until the compression + PLUS the fucking upload is done or
2) do the compression + THE upload in a background thread in which case it can be dangerous for verbose amount of fuckups (internet dies phone explodes etc) and the app crashes

which (one) option of the 2 suboptions from the second parent option branch?

of course this is an extremely unrealistic case, it is possible but thats not my point: my point is WHERE SHOULD THE COMPRESSION (as some kind of universal standard) BE HANDLED AT?

Sometimes I have zero motivation. Then, I get a great idea and my dick explodes from excitement.

Goddamn it!
Every time I pull changes on this project, it goes nuclear and explodes in my face 🤯

Wordpress... Developer... *explodes*

Working with a pointer-linked graph. With pointers referencing pointers referencing pointers referencing pointers ref....
*explodes*
it's not (only) bad code, its my life now.

So I'm not much for Linux, but I'll admit. It's a pretty damn solid environment, especially for programmers.
Since my main computer can't afford to have Linux on it, I decided to start working on making the Raspberry Pi handheld notebook. But after I added up the price for all of the components, it's almost three hundred dollars.
Personally, I would love to have a mini computer everywhere I go. A Chromebook is ok. But I guess you need to take into consideration that it is NOT ment for programming. I have found several IDE's and found none of them have a debugger or a way to execute my code.
I did some thinking and I'm starting to wonder if it is worth it.
It's a hand held computer with ubuntu on it. What's the worse that can happen? I don't solder the battery correctly and the whole thing explodes in my hands? Yeah that's pretty likely. Another reason I look at getting it is because there is so much fucking theft at my school it's hard to believe we don't have armed gunmen at every corner since everyone is always sober or high as shit.
Having an 11.6 inch Chromebook also puts me at risk of getting mugged, because who the fuck wouldn't want to try and pawn a laptop for drug money? At least with a handheld I could keep it in my pocket where I know it'll be safe.
What do you guys think?
Should I build this little thing or keep my current Chromebook but try to keep it safe?

Have you ever worked for an organization that is not specialized in software development because that is not their main line of business, however, their products are software applications?

If you are, then hi you and me are in the same boat. Currently I have a nice manager and I'm acting as dev lead the strange thing I have a peer that is supposed to be lead as well but I cannot define his position....

In theory he should be scrum master / resource manager which fails at both terribly.

I ended up implementing Agile in the team and deciding what goes and not into the sprint based on quality while this guy just try to squeeze stuff into the sprint, the more the better even with all kinds or problems...

Honestly I'm not sure why he is still in the team since it seems like he only drains the budget, doesn't understand a thing about the products he is working on and every single idea he has is horrible.

Every meeting I have with him I always ended up asking myself "How can somebody be that stupid?" The lack of technical knowledge and even common sense is over 9000 in this one...

It might sound bitter from my end but after two years of dealing with this stupidness of getting people in software development that have no idea what software development is and understand the intricacies of it just because they did an access database or are good at excel is nonsense.

I'm at the verge of quitting and the only thing that is keeping me here is my manager and the fact that the products I am working with are pretty interesting.

Sorry for the long rant but I had to get it out of my chest before it explodes and I directly call out this person.

Not looking for suggestions but if anybody want to chime in go ahead.

Clearing the backlog before the sun explodes.

I've been working on a problem for the last few hours and not getting anywhere ... so here are a jokes ... coz im bored

What do you get when you cross an insomniac, dyslexic, and an agnostic?

Someone who stays up all night wondering if there really is a dog.
-----
I went to a bookstore and asked the saleswoman, "where's the self-help section?" She said if she told me, it would defeat the purpose.
-----
I'm addicted to drinking brake fluid , it's ok I can stop when I want
-----
what type of monkey explodes - a Baboom
-----
my brother has. taken being sent to jail really. He has been refusing food and drink, spitting and scratching anyone who comes near and he smeared the walls with his s**t.

I'm not inviting him to monopoly night again.

panic() in golang. Aptly describes the state of every developer when code explodes.