Thank you dear mr. boss for fucking up our master branch by adding local changes to a 2 months outdated master branch (250 FUCKING COMMITS BEHIND), pull the remote and then just push without resolving any conflicts!!!1!!!

But thank you so much for sending me an email at 10pm asking me to resolve the conflicts.

It is 3 in the morning and it took 1 hour to get it clean.

Sometimes I want to break some necks...

LinkedIn is an alternative reality unhooked from the rest of the world, where hypocrisy and arrogance meet, creating Leaders, Experts and Analysts.

- Every company is an industry leader globally.
- Every offer is life-changing.
- Every normal person suddenly is an expert in his field
- Each candidate is an expert in time management, customer relationships, and software development priorities.
- They are all happy to share their achievements in a disinterested way
- They all deal with important issues, with great reflections on the meaning of life and reality around us
- Each written post usually starts with a question followed by a life experience
- Companies are dynamic, they change their internal processes on a daily basis

Please shoot me, I've had enough of this shit.

- Few companies are leaders globally
- The offers you make are traps and I always have to look for where the bullshit is.
- You're not an expert in your field if you've been doing the same thing for 10 years without moving your ass out of that chair.
- If you were a time management expert, I wouldn't have to call you every week for unresolved tasks, and I wouldn't even have to do 150 meetings to postpone the goals set. Exactly what is your experience with the customer? Because by heart shutting up and always saying yes is not a good way to get the job done.
- I have great news for you. Nobody gives a shit about your work successes. At most they're envious.
- If you really are such a deep and introspective person... how the fuck is it that working with you is hell?
- Copying a quote from a website and then building a narrative on it doesn't automatically make you a superstar
- Companies, especially the largest ones, take years to change and if they do it is because there is the economic motivation behind it, not because they are visionaries.

This rant was written by scrolling through my LinkedIn feed.

What keeps me up at night?
Unresolved merge conflicts.

That feeling when you have been finding what is wrong for hours just to find that your problem is also an unresolved issue on github

*git push*

"There are 27 unresolved merge conflicts"

.NET drinking game:
* Drink every time IntelliSense refuses to tell you what the actual error is because it's too busy choking on lambda syntax from a decade ago
* Take a shot every time you discover a closed, unresolved Github issue discussing your current showstopping build/CI problem
* Finish your drink every time the solution to your problem involves either manual edits to your CSPROJ (or whatever) file, or creating a new project altogether and copying all your fucking files over

Happy Friday! For all you programmers that have unresolved bugs, best of luck on fixing them before 5! :)

I hate it when I pick a library that seems popular, has a ton of stars on GitHub, a ton of downloads, used seemingly everywhere, only to find out months later that it's SHIT. I found bugs that made me doubt anyone is actually using this fucking thing. Your GitHub stars mean nothing.

So now it's either rewriting the entire codebase to a different library, or fixing it. Serves me right for not checking the unresolved issues first.

I was asked to fix a critical issue which had high visibility among the higher ups and were blocking QA from testing.

My dev lead (who was more like a dev manager) was having one of his insecure moments of “I need to get credit for helping fix this”, probably because he steals the oxygen from those who actually deserve to be alive and he knows he should be fired, slowly...over a BBQ.

For the next few days, I was bombarded with requests for status updates. Idea after idea of what I could do to fix the issue was hurled at me when all I needed was time to make the fix.

Dev Lead: “Dev X says he knows what the problem is and it’s a simple code fix and should be quick.” (Dev X is in the room as well)

Me: “Tell me, have you actually looked into the issue? Then you know that there are several race conditions causing this issue and the error only manifests itself during a Jenkins build and not locally. In order to know if you’ve fixed it, you have to run the Jenkins job each time which is a lengthy process.”

Dev X: “I don’t know how to access Jenkins.”

And so it continued. Just so you know, I’ve worked at controlling my anger over the years, usually triggered by asinine comments and decisions. I trained for many years with Buddhist monks atop remote mountain ranges, meditated for days under waterfalls, contemplated life in solitude as I crossed the desert, and spent many phone calls talking to Microsoft enterprise support while smiling.

But the next day, I lost my shit.

I had been working out quite a bit too so I could have probably flipped around ten large tables before I got tired. And I’m talking long tables you’d need two people to move.

For context, unresolved comments in our pull request process block the ability to merge. My code was ready and I had two other devs review and approve my code already, but my dev lead, who has never seen the code base, gave up trying to learn how to build the app, and hasn’t coded in years, decided to comment on my pull request that upper management has been waiting on and that he himself has been hounding me about.

Two stood out to me. I read them slowly.

“I think you should name this unit test better” (That unit test existed before my PR)

“This function was deleted and moved to this other file, just so people know”

A devil greeted me when I entered hell. He was quite understanding. It turns out he was also a dev.

!rant

Going to the gym really helps with concentration and may give you time to focus on things that are unresolved on your codebase.

It will also make you sexy as hell. Being sexy as all hell is good and gold.

Remember that

So for our current Hybrid application in Cordova, we are using few open source PLUGINS

One of the plugins have some known unresolved issues, stopping us to customize our App

Now my Client and Project Manager want me to personally CALL that guy (original developer) and TELL HIM to resolve the issue in '3 days, before Monday'

God save me :/

Probably had my worst half-week ever this week.

Customer's CRM system, the read and edit masks just...stopped existing on last week friday. CRM fell back on some default masks for the dataset. No way to create new masks directly without putting the whole system upside down.
We couldn't do anything anyway because they reported the issue literally as we all were about to leave for weekend and our boss was like "Ah nah, well do it next week."
Our brains were already fried anyway...
I mail the reporter that we've registered their issue, will investigate and report back ASAP once we've got news.

Monday rolls around, I'm whacking my head against their system trying to figure the fuck out, what went wrong and how to solve it, I come up empty; Not that terrible since the masks only stopped existing in the webclient version of the system and they can still use the windows client, so they can still work.

Tuesday rolls around, I'm at an on site training for an ERP system with my boss at a remote company. Get an email in midst of the training, I was doing protocol.
Guy from the afflicted company goes and tells me that the issue has somehow spread to his colleague and him...IN THE WINDOWS CLIENT.

I'm fucking flabbergasted, so to speak, since the masks for the windows client and the web client are totally isolated from one another.
After we're back at our company, I investigate, less efficiently this time because my brain got fried at the training. I come up empty again.

NOW TODAY: Discuss further proceedings with my boss, he's not pissed at me or anything, just to say, but we're both worried, obviously.

Then at 10:20, a guy from the afflicted company mails me in an annoyed tone that the masks are still broken.

11:00, we figure out a workaround so the windows client users can at least work again, albeit limited.

11:10, I mail the guy, telling him that although we're still not able to fully work everything out and are still investigating, we've made a workaround so they can at least work again.

11:20, the guy mails me in a pissed tone around the lines of "This is very very important and must be fixed ASAP or else we'll not be able to work at all [...]"
And I think like "Dude I literally just told you like 8 minutes ago that there's are workaround so you'll be able to at least work again..."

Forward the mail to boss, we meet up quickly to discuss how in God's name we can deescalate this mfer.

11:31, the guy mails me again, all apologetically this time "Stop! All is good, I just now fully read you mail, thanks for implementing the workaround, nothing will come to a standstill [...]"

BRUH CAN YOU NOT FUCKING READ BEFORE ESCALATING SHIT

Fuck customers. Dumb fucking cretins unable to fucking read.

The issue is still unresolved. Support of the CRM software lets us sit on our collective asses and wait.

There is no such thing as stable software, it's a myth.

Every corporate software is like an ever-decaying semi-corpse of a brain dead patient slowly getting worse and worse but not fucking dying.

Rant over.

I'm getting to the point where every time I encounter a new bug to fix I die a little inside. So tired of stuff not working and as soon as I get one thing fixed another blows up. Unresolved problems and open loops keep me awake all night. I sometimes want to switch careers but what else is there for me after more than 2 decades of this? I guess I could flip burgers and mow lawns. The burger flippers make about what I made in my last job and the guy who mows my lawn makes twice that much.

I scoured my memory, and realized that I have never had a fight with another developer in all my years. Yes, there have been debates, but they were logical. There are even a few unresolved debates, due to preference and ideology, but never anything with enough emotion to be called a fight.
That's pretty cool. We are smart people and can discuss important issues without resorting to petty bickering.

I dont. I am a struggling junior whos back at mobile dev after 2 years of a break while working on that 2 for 2 years prior. I dont know. I get addicted to problem solving and also some unresolved childhood traumas are driving me to tryhard and sacrifice personal life in order to perform better in my job. I am afraid of failure so I will sacrifice everything whaf I can to be better.

When I search for anything programming-related on Google, I realize how many different meanings a word can have. Adding more words to specify context sometimes even makes it worse and it often makes results more unspecific and unrelated. And when I find something that exactly matches my case, it's an unresolved question from 2017 or 2006.

I haven't coded anything for months now, maybe 1.5 to 2 years even, because I was struggling with depression and unresolved issues. I'm still not out of it, and I'm not seeing anyone for now because of quarantine, but I've been taking antidepressants during the last months (prescribed by a doctor) and they're beginning to have a good effect. I'm feeling better by the day, and I'm looking forward to seeing a professional and getting better without the medication after the end of the coronacrisis (which isn't something I would have thought sometime ago, so that's encouraging).

Anyway, today I took my laptop and started coding again, and I really liked it, but it really felt like my mind was fucking rusted after all this time. It took me like 3 hours to write 60 limes of code. I know that by keeping coding a bit everyday I will find my old skills again, but I was wondering if you had any tip to ease the start, like doing code exercises, or trying to make a simple project. I'll take any tip to get back on the train again, as quickly and smoothly as possible.

Second question : please comfort me and tell me I'm not the only one who is suffering or has suffered from rusted mind syndrome.

If you could solve *one* of the major unresolved problems in computer science, which one would you choose and *why*?

Hyuk hyuk hyuk

Folks,
I've copied a folder(size: 10.7GB) to external HD, and it's occupying 154GB on external disk.

yes, the folder has a lot of small files in it. but ..

Surprisingly, the same folder occupy 10.8GB on internal HD. and that drive is not compressed.

I defragmented external HD, problem still unresolved.
* allocation unit size is default(4096B) on both the disks. both are NTFS

Plz, help me, explain me... :-(

Your code quality is pajeet tier.

You consistently make poor design and architectural choices.

Your project has maintained 50 plus unresolved bugs for about 6 months, and yet you're consistently under delivering against what you commit to.

Other developers refuse to work with you.

So tell me again how you feel you're an effective lead developer

Story of my life:

1. Complete project to 90+%
2. Add that "one last feature"
3. Hit unresolved bug buried deep in one of the project's core requirements.

I hate arguments for the following reasons:

1) I suck at them
2) they can get out of hand
3) their context may be pointless
4) they cause unnecessary pain
5) they end unresolved (sometimes)

Gitlab issues and their mile long conversations are driving my crazy.

I just wanted to find out if a fcking feature exists. Oh, there is a ticket ... ah cool opened 4 years ago ... still unresolved?!

Thats fine, maybe they are planing shit. But no, their discussion lasts for freaking years. And than it just gets lost or fcking closed. I mean what the hack?!

Sometimes even paying customers are getting freaking ignored or like ... ugh might be a cool feature, but plz fck off ...

That happened to me so many freaking times. Its driving me crazy!

Statically linking to qt5 is quickly driving me fucking insane.

I've a list of unresolved dependencies during linking longer than a really long fucking list. Ugh.

Cmake, why can't you save me?

Think I'll just go back to dynamic and build on each needed system.

Fucking linker options on Ubuntu. Somehow it seems to have --as-needed turned on by default. This leads to stripping libraries we had referenced in our target_link_libraries. Then our application won't start because of the unresolved libraries it cannot find in the Rpath, although they would be there. Thank you clever fox.
Now we have to add another stupid linker flag, just to run again.

first of all fuck this stupid website and deleting your rant if you aren't signed up
second of all fuck fetch
curl gives me a readable json object
axios gives me a readable json object
fetch gives me what should be a readable json object, but looks more like a set in python instead
[{"id":"1"},{"id":"2"}] curl and axios reply with this
meanwhile fetch
{
[
{"id":"1"},
{"id":"2"}
],
{various symbol objects}
}
how am I supposed to get my data out of a fetch? I see people call response[0] or using some strange amalgamation of
fetch().then().then((data) => {}) but data in this results in an unresolved promise for some inexplicable reason. (nextjs)
also fuck nextjs I want to go back to hardcoding everything in html
also fuck modern web development and businesses in general, they ruined the internet.

So apparently it’s been an unresolved issue in IntelliJ for the past 4 years that sometimes debugging gradle tasks just fails silently. Found a number of workarounds online for old versions but they since removed the options in settings that fixed the issue? Fuck you jetbrains

One nightmarish project that was doomed from the beginning, had me as the sole developer. I could hardly sleep when we began testing on a separate test system, but with (nearly) all the config stored in shared memory and copied from the production system, I dreaded, half awake, that the production server data base connection was still configured in the test system and that it was shooting all it's test data repeatedly to prod.

Finally drove to company in middle of the night at 4 o'clock. Checked everything was OK, tried to sleep 3 hours before the start of the work day.

This system also had the most hideous memory corruption in some shared memory that was used across several processes and should have been thoroughly protected by a mutex, but somehow, sometimes this crucial map, that was used to speed up the access to all the customer data just contained garbage.

Still haunts me to that day. (Like xkcd's unresolved tension of a non-matching parenthesis - an unresolved bug.