Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "fireworks"
Happiness is not getting any server issue/downtime notifications while you're outside on a bridge watching fireworks ❤😊5
My first job: The Mystery of The Powered-Down Server
I paid my way through college by working every-other-semester in the Cooperative-Education Program my school provided. My first job was with a small company (now defunct) which made some of the very first optical-storage robotic storage systems. I honestly forgot what I was "officially" hired for at first, but I quickly moved up into the kernel device-driver team and was quite happy there.
It was primarily a Solaris shop, with a smattering of IBM AIX RS/6000. It was one of these ill-fated RS/6000 machines which (by no fault of its own) plays a major role in this story.
One day, I came to work to find my team-leader in quite a tizzy -- cursing and ranting about our VAR selling us bad equipment; about how IBM just doesn't make good hardware like they did in the good old days; about how back when _he_ was in charge of buying equipment this wouldn't happen, and on and on and on.
Our primary AIX dev server was powered off when he arrived. He booted it up, checked logs and was running self-diagnostics, but absolutely nothing so far indicated why the machine had shut down. We blew a couple of hours trying to figure out what happened, to no avail. Eventually, with other deadlines looming, we just chalked it up be something we'll look into more later.
Several days went by, with the usual day-to-day comings and goings; no surprises.
Then, next week, it happened again.
My team-leader was LIVID. The same server was hard-down again when he came in; no explanation. He opened a ticket with IBM and put in a call to our VAR rep, demanding answers -- how could they sell us bad equipment -- why isn't there any indication of what's failing -- someone must come out here and fix this NOW, and on and on and on.
(As a quick aside, in case it's not clearly coming through between-the-lines, our team leader was always a little bit "over to top" for me. He was the kind of person who "got things done," and as long as you stayed on his good side, you could just watch the fireworks most days - but it became pretty exhausting sometimes).
Back our story -
An IBM CE comes out and does a full on-site hardware diagnostic -- tears the whole server down, runs through everything one part a time. Absolutely. Nothing. Wrong.
I recall, at some point of all this, making the comment "It's almost like someone just pulls the plug on it -- like the power just, poof, goes away."
My team-leader demands the CE replace the power supply, even though it appeared to be operating normally. He does, at our cost, of course.
Another weeks goes by and all is forgotten in the swamp of work we have to do.
Until one day, the next week... Yes, you guessed it... It happens again. The server is down. Heads are exploding (will at least one head we all know by now). With all the screaming going on, the entire office staff should have comped some Advil.
My team-leader demands the facilities team do a full diagnostic on the UPS system and assure we aren't getting drop-outs on the power system. They do the diagnostic. They also review the logs for the power/load distribution to the entire lab and office spaces. Nothing is amiss.
This would also be a good time draw the picture of where this server is -- this particular server is not in the actual server room, it's out in the office area. That's on purpose, since it is connected to a demo robotics cabinet we use for testing and POC work. And customer demos. This will date me, but these were the days when robotic storage was new and VERY exciting to watch...
So, this is basically a couple of big boxes out on the office floor, with power cables running into a special power-drop near the middle of the room. That information might seem superfluous now, but will come into play shortly in our story.
So, we still have no answer to what's causing the server problems, but we all have work to do, so we keep plugging away, hoping for the best.
The team leader is insisting the VAR swap in a new server.
One night, we (the device-driver team) are working late, burning the midnight oil, right there in the office, and we bear witness to something I will never forget.
The cleaning staff came in.
Anxious for a brief distraction from our marathon of debugging, we stopped to watch them set up and start cleaning the office for a bit.
Then, friends, I Am Not Making This Up(tm)... I watched one of the cleaning staff walk right over to that beautiful RS/6000 dev server, dwarfed in shadow beside that huge robotic disc enclosure... and yank the server power cable right out of the dedicated power drop. And plug in their vacuum cleaner. And vacuum the floor.
We each looked at one-another, slowly, in bewilderment... and then went home, after a brief discussion on the way out the door.
You see, our team-leader wasn't with us that night; so before we left, we all agreed to come in late the next day. Very late indeed.9
Dabbling in 3D modeling, I noticed the top of one of these fireworks has polygons visible while the others are shaded smoothly. Good job, Clash of Clans...13
New years eve plans:
Partying with friends ✖
Getting wasted ✖
Shooting fireworks ✖
Reading godot documentation ✔7
This is my most ridiculous meeting in my long career. The crazy thing is I have witnessed this scenario play out many times during my career. Sometimes it sits in waiting for a few years but then BOOM there it is again and again. In each case the person that fell into the insidious trap was smart and savvy but somehow it just happened. The outcomes were really embarrassing and in some cases career damaging. Other times, it was sort of humorous. I could see this happening to me and I never want it to happen to you.
Once upon a time in a land not so far away there was a Kickoff Meeting for an offsite work area recovery exercise being planned for our Oklahoma locations. Eleven Oklahoma high ranking senior executives were on this webinar plus three Enterprise IT Directors (Ellen, Jim and Bob) who would support the business from the systems side throughout the exercise.
The plan was for Sam Otto, our Midwest Director of Business Continuity to host this webinar. Sam had hands-on experience recovering to our third party recovery site vendor and he always did a great job. He motivated people to attend the exercise with the coolest breakfasts and lunches you could imagine. Donuts, bagels, pizza, wings, scrumptious salads, sandwiches, beverages and desserts. He was great with people and made it a lot of fun.
At the last minute Charles 'Don't Call Me Charlie' Ego-Smith, the Global Business Continuity Senior Vice President, decided to grand-stand Sam. He demanded the reins to the webinar. Pulled a last-minute power-play and made himself the host and presenter. You have probably seen the move at some point in your career. I guess the old saying, 'be careful what you wish for' has some truth to it - read on and let me know if you devRanters agree...
So, Charlie, I mean Charles, begins hosting the session and greets all of the attendees. Hey, good so far! He starts showing some slides in the PowerPoint presentation and he fields a few questions, comments and requests from the Oklahoma executives. The usual easy to handle requests such as, 'what if we are too busy to do recover all systems', 'what if we recover all of our processes from home', 'what if we have high profile visitors that month?' Hey you can't blame them for trying. You are probably thinking to yourself, 'been there - heard that!' But luckily our experienced team had anticipated the push-back. Fortunately, Senior Management 'had our backs' and committed that all processes and systems must participate and test - so these were just softball requests, 'easy-peasy' to handle. But wait, we are just getting started!
Now the fireworks begin. Bob, one if the Enterprise IT directors started asking a bunch of questions. Well, Charles had somewhat of a history with Bob from previous exercises and did not take kindly to Bob's string of questions. Charles started getting defensive and while Bob was speaking Charles started IM'ing. He's firing off one filthy message after another to me and our teammate Sam.
'This idiot Bob is the biggest pain in the ass that I ever worked with'; 'he doesn't know shit', 'he never shuts the f up', 'I wanna go over to his office and kick his f'in ass...!'
Unfortunately...the idiot Charles had control of the webinar and was sharing his screen so every message he sent was seen by all of the attendees! Yeah, everyone including Bob and the Senior Oklahoma executives! We could not instant message him to stop as everyone would have seen our warnings, so we tried to call Charles' cell phone and text him but he did not pick up. He just kept firing ridiculously embarrassing dirty IM messages and I guess we were all so stunned we just sat there bewildered. We finally bit the bullet and IM'ed him to STOP ALREADY!!! Whoa, talk about an embarrassing silence!
I really felt sorry for Bob. He is a good guy. Deservedly, Charlie 'Yes I am going to call you CHARLIE' got in big time hot water after the webinar with upper management. For one reason or another he only lasted another year or so at our company. Maybe this event played a part in his demise.
So, the morale is, if you use IM - turn it off during a webinar if you are the host. If you must use it, be really careful what you say, who you say it to and pray nothing embarrassing or personal is sent to you for everyone to see.
Quick Update - During the past couple of months I participated on many webinars with enterprise software vendors trying to sell me expensive solutions. Most of the vendors had their IM going while doing webinars and training. Some very embarrassing things came flying across our screens. You learn a lot reading those messages when they pop-up on the presenters' screen, both personal and business related. Some even complaints from customers!
My advice to employees and vendors is to sign-out of IM before hosting a webinar. Otherwise, it just might destroy your credibility and possibly your career.6
People are so annoying.
It's 12 so finally, happy new year!
I'm trying to spend my new year by reading and there are annoying idiots outside have a country from 10 to 1 until it was 12 am.
Now they have fireworks and are screaming at the top of their lungs with music...
Looks like I won't have a peaceful night.16
Who needs fireworks if the sound of angry consumers after deleting a production database is as resounding as the sound of war itself
I've programmed my pi to launch fireworks whenever a post of mine reaches 150 ++'s
Now I need some testers9
Happy fourth of July everyone...my code hitting production is just like fireworks, doesn't take long before it blows up
Sorry for the long rant, sorry if I'm a mess writing, but I need to let this out somehow.
I'm currently working as a freelance developer for a company here. I was hired to work as a front-end developer, mostly React stuff.
Suddenly, the back end developers left the project because they were offered better opportunities, and this meant chaos, as we're currently migrating an old project and building an MVP of what we're going to offer.
I sensed more danger coming, so I was preparing to leave the boat too, as it felt like a LOT of stress would come if I stood here.
Well, just when I was preparing myself, CEO looks into my LinkedIn page and sees I worked as a back end developer before, and using PHP too, which is the language our project's built in.
He organizes a quick meeting and throws my name as a developer for our project, telling me that I could work on it, and everyone agreed.
Everyone, except me, because I didn't know he looked into it and had this "emergency" meeting (mostly WhatsApp message exchange).
The case is, now that they spread this news, my name is on it and I HAVE to work on our project acting as, somehow, a developer and makeshift CTO.
It feels like a fucking leash, like "now you do this or else...".
Under other circumstances, I'd be jumping and throwing fireworks in my room right now.
Although I did build the f*cking project alone (which is quite a feature for my resumé), it's a mammoth of a project, I'm borderline crazy AND there's still data to migrate from the old model to the new.
The problem is: the people who recorded that data (which includes adresses, locations, user information) did it like they wipe their asses, there's no standards, some important data are missing and I have to validate more than 6k addresses.
I just don't know what to do. I would hire people too, but I joined this because I needed the money, so I can't.
It's hard, I'm lost, it's crazy, I'm crazy.
Sometimes my brain just stops, and I can't do anything code-related. And it makes me mad, because I LOVE to code!
This piece of crap is taking away one of the things I love the most, with a piece of my sanity and health too.
How I wish I could just send'em all to hell.
The company may be small right now. But the higher ups, they're kinda "big", and that would make my life hell if I just throw the towel now.
I don't know nothing anymore.15
My december salary is delayed for a year (i’ll get paid around 2 or 3 january).
This broke af fireworks pic is how my new year looks like.
P.S Pic is stolen from facebook4
People filming fn fireworks with their goddamn phones is exactly why we should invent proper EMP device4
This semester our project for college was to create a simple board game for linux/windows, we were a group of four (actually three because one of us didn't contribute at all then gave up mid semester), I coded the game with my friend who was in the same group (pieces, board, AI, saving and loading ... ) and the other member chose to make the graphical interface because "He already coded a similar game". HE FUCKED IT UP SO MUCH THAT I'M EMBARRASSED TO SHOW IT TO MY GRANDPARENTS. Just to give you an idea, here's what it looks when you save a game (left picture is if something wrong happens, the right one is when you successfully save the game, it even has a grammar mistake (réussi instead of réussie) ).6
My dad was an IT and as a kid when our NES broke and I couldn't play Mario he showed me F-22 lightning (an aerial combat game) and I thought the missiles were fireworks. I always called it the airplanes and fireworks game. Good memories.
A made a realtime collaborative fireworks webapp ;) Happy 4th of July! It uses websockets on a Node.js server.6
// I could not post it yesterday coz #devrant
Am I the only person here who really but really started to hate fireworks?
Everyone is shooting, I can't even play because it is so loud outside and do not try to open windows coz you will die from poisoning in seconds...2
PROTIP: If you go outdoors for recreation and you happen to be hiking in dry country where there is obviously a lot of potential tinder around you, don't be a dumbass and light off fireworks.
The lingering smell of burning is not conducive to creating software.
With the AQI north of 170, the building's HVAC can't keep up.1
When you work with a client who will only use Fireworks for graphics but you only have one dying old machine with a licensed copy and Adobe won't give you keys even though you bought them years ago (and can prove it!) and you can't buy new keys because they don't sell them and even if we had them we can't download it any more.
WTF Adobe!! It's a dead product! We don't want support or anything. Just give us the feckin' keys and the bloody installer!!4
Hello my dear friend. I hate you. You are asking me why? You know exactly why.
Also I hate you for ugly, custom fonts without Polish letters and you fucking are mad at me why some letters look different?
Last thing. If you ever again ask me why a website (look again at projects you are giving to me) is looking different on mobile, then I swear I will fucking rape you. (but maybe I will maybe kill you instead)