The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I'm not sure exactly what you're asking about. My worst *coding* experience?
Probably one of the innumerable death marches I've been involved in. Pick one.
(I used to consult, and was often involved in project rescue, so i've been involved in a lot of failed projects - it's not fun)
In recent memory, strictly in debugging terms, I ran into an issue in my parser code with a particular grammar and the issue only cropped up after over a minute of lalr(1) table generation so each time i started the debugger i had to wait over a minute to get something useful to debug.
it took me awhile to track down that bug. as i recall, there was nothing wrong with that section of code, it was something upstream that was causing the problem.
Dealing with a test environment that took an unbecoming length of time to configure.
It was such a PITA that I routinely checked in code untested, which was definitely frowned on if it caused problems. Thankfully it rarely did, and never in a way that couldn't easily be patched (the product had no-restart patching, even in deployed software, forty years ago). I had developed an in-house application framework, so it couldn't be tested without knowing how to configure the test environment for whichever applications might be affected by the latest changes. I could have asked that the test group put someone on call, but it was hard enough to convince some folks that I should work on an application framework, not customer features. So I simply inspected my code carefully, checked it in with fingers crossed, and took the flak when it caused sanity tests to fail. On balance, it ended up being far cheaper to do it that way, but it was such a violation of The Process that it would never have been officially countenanced.
Being told that all my SQL had to be on a single line, and not formatted.
It would be as readable as formatted SQL, which is true if you just read out aloud the sentence. Wrote a VS plugin that would show a formatted SQL statement after selecting it and pressing a button. Wasn't allowed to copy/paste that formatted statement into code though, it had to be on a single line. Lots of scrolling just to read the statement wouldn't matter, that was preferred to people "wasting time" on formatting.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
The first time I went on a customer trip with my boss. I was an intern at the time. We were writing a control system for part of a manufacturing line. At one point, a part of the application I had written stopped working. I couldn't understand what was wrong, my boss was getting pissed, and the customer was looking unimpressed. We spent hours going over this and not getting anywhere. Finally, I went back and compared the code we were running to my original copy. They were different, and I hadn't made the changes. When I showed it to my boss, he admitted changing some things because he didn't like how I did part of it. When we put my code back, the application started working again.
I didn't say more than a half-dozen words to the guy the whole 10-hour drive home.
Spending a beautifully sunny Saturday morning in the cold server room of Skopje airport, because the (redundant) servers weren't communicating with each other, only to find that it was because the installation engineers hadn't followed my very clear, very detailed instructions on installing the Synaptic software.
They hadn't bothered following the section on configuring exceptions for Synaptic's internal firewall, so the servers weren't being allowed to talk to each other.
As is typical, once I'd found the problem, it took only a couple of minutes to fix -- but the day was ruined.
I wanna be a eunuchs developer! Pass me a bread knife!
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
Depends on the software you use - I find I have to power cycle from time to time on the Surface where it sleep /hibernates most of the time. If I don't, I lose the mouse pointer.
And hibernate can be a PITA if you have network shares onto a power-saving NAS - if it goes into low-power mode and spins the disks down, Windows doesn't always reconnect them properly. The same with access to SQL via the Desktop machine, even if no apps accessing it are open when the Surface is hibernated.
Herself also has "odd problems" with her Jigsaw app - sleep or hibernate with it running full screen and it always comes back with a blank screen, which is annoying to say the least.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
I'd be blaming the disk controller doing a bad job of power management rather than the OS. And frankly, based on my own experience, I've had much worse luck recovering from sleep sessions than hibernating.
My desktop systems run 24/7 (and have for years), but I always let my laptops hibernate - especially the older ones that otherwise take a long time to do a full reboot. Maybe I'm just lucky, but I've never encountered the sort of situation you're describing.
And I'll bring this up just because I hate them with a passion: Are your drives by any chance misfortune Seagate?