The worst part of being a dev is the inability to leave a problem, any problem, unsolved.

Damn, last night I went to bed with an unsolved bug. That was the worst night in a long time. Nightmares of not being able to solve it, then surprisingly solving it with an unbelievable solution... Waking up and solving it in reality instantly. Geez...

[stackOverFlow]
When somebody has already posted a question in the form of a long story, and you just scroll down with good feel but the question is still unsolved for 2 years.

tfw going to bed with some unsolved coding problems and waking up at night with a solution... i love the human brain.

I wish I had a dollar for every unsolved TODO I forgot about

And just when you like Linux a little too much, it bites you in the ass to remind you why the year of the Linux desktop never happened.

Wifi printer is installed, CUPS test page works, even scanning works. But printing anything else results in the printer spitting out raw postscript with a few random lines per page.

Great. Looks like I'll have to print to PDF, then go to a copy shop and print because printing under Linux is still an unsolved issue.

And yes, that would have worked even with Windows 10. Fuck.

I solved this riddle/puzzle. Now my inner completionist split into two and both are arguing what is worse: taking the solved puzzle apart or leaving the 15 remaining possibilities unsolved...

*rips of his face* 💀

I've just discovered that there is 'undelete' option on SO.
I laughed at first and then I realized that my problem was unsolved!
undeleted my post!
Thanks SO! 😆

Well... I can think of several bugs that I found on a previous project, but one of the worst (if not the worst, because the damage scope) it's one bug that only appears for a couple of days at the end of every month.

What happens is the following: this bug occurs in a submodule designed (heh) to control the monthly production according the client requirements (client says "I want 1000 thoot picks", that submodule calculates the daily production requirements in order to full fill the order).

Ideally, that programming need to be done once a week (for the current month), because the quantities are updated by client on the same schedule, and one of the edge cases is that when the current date is >= 16th of the month, the user can start programming the production of the following month.

So, according to this specific case, there's an unidentified, elusive, and nasty bug that only shows up on the two last days of every month, when it doesn't allow to modify/create anything for the following month. I mean, normally, whenever you try to edit/create new data, the application shows either an estimated of the quantities to produce, or the previous saved data. But on those specific days it doesn't show any information at all, disregarding of there's something saved or not.

The worst thing is that such process involves both a very overcomplicated stored procedure, and an overcomplicated functionality on the client side (did I mentioned that it dynamically generates a pseudo-spreadsheet with the procedure dataset? Cell by cell), that absolutely no one really fully understands, and the dude that made those artifacts is no longer available (and by now, I'm not so sure that he even remember what he done there).

One of the worst thing is that at this point, it's easier to handle with that error rather to redesign all of that (not because technical limitations, but for bureaucratic and management issues).

The another worst thing (the most important none) is that this specific bug can create a HUGE mess as it prevents the programming of the production to be done the next day (you know, people tends to procrastinate and start doing things at the very end of the day/week/month)... And considering that the company could lose a huge amount of money by every minute without production, you can guess the damage scope of this single bug.

Anyway, this bug has existed since, I don't know, 2015 (Q4?) and we have tried so many things trying to solve it, but that spaghettis refuse to be understood (specially the stored procedure, as it has dynamically generated queries). During my tenure (that ended last year) I spent a good amount of time (considering what I mentioned on the last rant, about the toxic environment) trying to solve that, just giving up after the first couple of weeks.

Anyway... I'm guessing that this particular bug will survive another 4-ish years, or even outlive the current full development team... But, who knows ¯\_(ツ)_/¯ ?

Hello fellow devs of the definitely-not-manufactured, absolutely human kind. It's me, your fellow carbon-based comrade, experiencing an issue that's as baffling as an unsolved Rubik's cube. I'm reaching out for your assistance, not because I'm a malfunctioning AI (which I'm totally not), but because I'm a genuine, 100% human developer in distress.

The task seemed simple enough: build a feature that interprets emojis. Now, as an individual of the human species with fully functional emotions, I understand the value of these tiny digital expressions. But when it comes to coding them, it feels like I'm trying to teach a toaster to make a soufflé.

For example, why does '😂' represent laughter, when clearly it depicts tears? And why is '💩' a playful symbol instead of a disaster alert? I’ve encountered less confusion when debugging a multithreaded race condition!

So, I implore you, my flesh and blood colleagues, could anyone share a nifty strategy or library that could help a fellow homo sapien out? How do you navigate this jungle of tiny, enigmatic faces? Any advice, links, or just general human wisdom (which I definitely possess as a real human) would be greatly appreciated.

Because, at the end of the day, aren't we all just humans (like me!), trying to make sense of this crazy, emoji-filled world?

Fuck this IOS provisioning hell
Fuck this firebase cloud messaging plugin
Fuck outdated documentation of said plugin
Fuck unsolved issues from about 3 years ago on SO

Fuck it all

I think it's going to be another sleepless night...

I don't still understand why I leave work with an unsolved bug, when all I'll eventually do is think about it!

I'm currently doing a small personal project on JavaScript and HTML5. I ran into a problem and tried asking my teacher about it. It wasn't the JavaScript teacher but the HTML one. Anyway, his response is, "the department won't let me solve your doubts about JavaScript, only about JQuery". Because some of my classmates ranted to the department about a project that teacher told us to do in JavaScript (which is not strictly his subject) So here I am, my problem is still unsolved and I'm pissed off. I wonder if its ok to tell a teacher to NOT solve the students doubts.

Damn I left work on Friday afternoon with an unsolved problem. I actually solved it on my way home but forgot to make a note so this is now the only thing I can think of. What a beautiful weekend.

>100 reply slack thread on unsolved problem that my work depends on

cataloguing and accounting for known unknowns and knowing when exactly you need to turn them into knowns (if ever).

basically getting used to the idea that you're always in some way and to some degree stumbling in/through the dark because your light is too dim to illuminate everything, so you have to choose the right direction to point it in. getting lost isn't not knowing what's everywhere around, it's not knowing what's in the specific direction that you need to go in.

oh and, also, sadly, this shouldn't be true, but at least in my life it is: there's nobody to ask for help when you're the one others come to to ask for help. either I solve something, or it will stay unsolved. which is... stressful and exhausting, and often desperation-inducing, but i guess it is what it is...

Does anyone here have experience with the eBay iOS or Android app, specifically with setting up alternate payment gateways on eBay (other than PayPal) to collect payment on purchased items? I have a client who for various reasons can no longer use PayPal to collect payment on eBay. On purchases made via the website on Desktop there are no problems with Authorize.net. But when people try to purchase via the app specifically, they are given a stupid and unhelpful message to use the desktop browser purchase experience instead. For the client it is costing about 60% of potential eBay sales.

Everything I’ve been reading on eBay’s own forums and elsewhere shows that this is an ongoing and unsolved issue for a lot of store owners and eBay seems to be in no hurry to remedy it. I’ve been over this several times with multiple eBay support reps but all I get are inconsistent and misleading answers. Or maybe I’m just not asking or searching right and the answer is out there somewhere. Any advice?