Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "friday's"
-
I worked for over 13 hours yesterday on super-urgent projects. I got so much done it's insane.
Projects:
1) the printer auto-configuration script.
2) changing Stripe from test mode to live mode in production
3) website responsiveness
I finished two within five minutes and pushed to both QA and Production. actually urgent, actually necessary. Easy change.
The printer auto-configure script was honestly fun to write, if very involved. However, the APIs I needed to call to fetch data, create a printer client, etc... none of them were tested, and they were _all_ broken in at least two ways. The CTO (api guy in my previous rant) was slow at fixing them, so getting the APIs working took literally four hours. One of them (test print) still doesn't work.
Responsiveness... this was my first time making a website responsive. Ever. Also, one of the pages I needed to style was very complicated (nested fixed-aspect-ratio + flexbox); I ended up duplicating the markup and hacking the styling together just to make it work. The code is horrible. But! "Friday's the day! it's going live and we're pushing traffic to it!" So, I invested a lot of time and energy into making it ready and as pretty as I could, and finally got it working. That page alone took me two hours.
The site and the printer script (and obv the Stripe change as well) absolutely needed to be done by this morning. Super important.
well.
1) Auto-configure script. Ostensibly we would have an intern come in and configure the printers. However, we have no printers that need configuring, so she did marketing instead. :/ Also, the docs Epson sent us only work for the T88V printer (we have exactly one, which we happened to set up and connect to). They do not work for the T88VI printers, which is what we ordered. and all we'll ever be ordering. So. :/ I'll need to rewrite a large chunk of my code to make this work. Joy :/
2) Stripe Live mode. Nobody even seemed to notice that we were collecting info in Test mode, or that I fixed it. so. um. :/
3) Responsiveness.
Well. That deadline is actually next Wednesday. The marketing won't even start until then, and I haven't even been given the final changes yet (like come on). Also! I asked for a QA review last night before I'd push it to production. One person glanced at it. Nobody else cared. Nobody else cared enough to look in the morning, either, so it's still on QA. Super-important deadline indeed. :/
Honestly?
I feel like Alice (from Dilbert) after she worked frantically on urgent projects that ended up just being cancelled. (That one where Wally smells that lovely buttery-popcorn scent of unnecessary work.)
I worked 13 hours yesterday.
for nothing.
fucking. hell.undefined fuck off we urgently don't need this yet! unnecessary work unsung heroine i'm starting to feel like dark terra.7 -
When I first got in this companie, with 3 other people, one of the first thing they told us was about a "rule" that we never deploy on Friday's or at the end of the day, but no one else in the company knows about it. It's the department's little secret 👌10
-
Trying to get to the weekend like:
If I use the restroom for 10 minutes then make myself some coffe for 5 minutes then
Only 7 hrs and 45 minutes till I can leave! Sweet!1 -
Week to make a decision my ass. Two workdays.
"Hi Agred,
Thanks again for the friday's meeting!
After a short consideration, of course we would like to start working with you :)
[...]
I hope you're still interested in working with us and that we will start working together soon!"
O
M
F
G
Wow. "[...] of course we would like to start working with you". Just wow. This "of course" part really got me.
So, I've only got a month left in my current company. Goodbye working alone! Goodbye being the only person in Java and C# "departments". Goodbye stagnation!
Goodbye, Moonmen6 -
So i just saw a post about not pushing to production on Friday's and that reminded me of something.
A team we are working with (we needed help on something so we got another company to send us a team and do it for us) recently push to production on a Friday at around 5pm.
We didn't know that they had done it until a shit ton of errors started happening and we had no idea why (it was working so far, none of us did anything, so what the fuck is going on).
To make things better, one of my colleagues tried calling them and they wouldn't answer the phone. They knew what they did, so they went home before we could notice it and we had to correct their mistake.
We had everyone calling us saying they had gotten an error, and they needed to get home but couldn't because of it (it messed up a process that only happens at the end of the day before people go home. I can explain more in the comments if anyone is confused, or just wants to know).
Eventually everything was solved, but that was a very stressful ending of the week.
So yeah, don't deploy on Friday's please and thank you7 -
Nothing is more relaxing then finding some really bad code and clean it up in your free time with music in background. Love this kind of Friday's.
-
I look forward to Friday's Nerf dart battles in the office. A great way to blow off the steam that built up during the week.3
-
After a long time waiting for it, I finally got my swag ! Just in time for the Friday's devrant meeting !4
-
I don't understand wtf is happening today..
- in project A, terraform suddenly decided to stop working with kubernetes-related providers -- the CA cert mismatch error. I agree, it should be not working, because there are 2 kube-api severs behind an LB. But why now??? Why was it working for the last 2 months, until NOW????
- in project B, terraform suddenly decided to stop working _correctly_ with kubernetes-related providers -- it doesn't find resources randomly, even though they are available and I can see them via kubectl get. TF_LOG=DEBUG shows terraform sending correct requests to the kube-api, but the response is a 404. wtf... I see those resources present in another terminal window, only using kubectl. wtf....
- my PR in github was commented, I wanted to ask a question seconds later, and I'm getting a 502 from GH
wtf... I can't spot a pattern and that drives me freaking crazy.
Is this the Friday's curse...? IDK4 -
Started a side project.
Learnt flutter and firebase.
Started coding app.
Four months pass by.
App is mostly ready.
Wakes up on Saturday morning.
Updates Android Studio and SDK because, why not?
Build failed!
Dependency depreciation warnings!
Java errors!
Firebase errors!
Emulator stopped running!
Wify is angry with me as we planned shopping but now this. Fortunately, she's also in IT, so she understands..
FML! Spent the entire day stackoverflowing and fixing errors!
8PM evening, I am back to Friday's status. My shoulder and neck hurts but my mind is chilled.6 -
So this past few days of a mix bag of emotions. Friday's weekly deliverables on our first dry run at launch, I squeeze across the line in an embarrassing finish. Decision to proceed with the live run to be delayed, not going to happen if I've got something to say about it.
Next day, vendor on the house my wife has purchased (our first!!) and says we can move the settlement date ahead 4 weeks! Winning!
Monday, meeting with all stakeholders on the fuck up that was my deliverables I'm responsible for, granted a conditional pass. "Don't worry, I got this."
Tuesday, received the results of a technical challenge I've given one of the developer candidates - he smashed it. Keen to give him the job!