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 release day"
-
I quit and my last day is next week.
Apparently management has decided that I should spend my last day implementing a new feature for a customer where I have been the only developer, and release it to production (without first implementing it in test) the same day. A feature that potentially could cripple a whole workflow if done wrong.
Of course I advised not to release untested code to production on a friday, just before the only person that knows how it works leaves the company. But no, “the customer reaaaaaally wants it before summer, so just be careful not to write any bugs”.
I’m not saying that I’m intentionally gonna write bad code - but if I do, I’m not gonna pick up the phone when it calls.17 -
My day.
6 am: 2yo woke up
8:30 am: start work (from home)
11 am: go get breakfast/lunch
11:30 am: work call. while driving. Learn nothing new.
12:00 noon: infuriatingly slow errand
12:30 pm: work call. Learn nothing new.
1 pm: finally get to eat. It's cold. And terrible.
6 pm: 2yo finally goes to sleep (missed nap)
9:20 pm: 2yo wakes up screaming.
9:30 pm: find 3 or 4 tablespoons of leftover tuna in the fridge. No bread.
10:45 pm: I finally finish my work (super-urgent friday-morning release of a next-Wednesday-morning deadline... Yeah idfk.)
11:29 pm: 2yo stops yelling and screaming and goes back to sleep
11:39 pm: finish writing this while in bed.
11:40 pm: Sleep?10 -
Yesterday (or the day before that depending on your timezone and day-night schedule - this Friday) my OnePlus 6T arrived. After only 2 days of time between placing the order and actually getting the phone, quite impressive!
The DHL guy asked me upon receipt - is it the OnePlus 6T? - Yes it is!! - "An amazing device it is!", he said. And honestly.. he couldn't be more right.
I might be a bit biased on this because after all I did just spend €630 on this phone. But it feels so snappy, high quality, the 8GB of RAM is just.. it blows my mind. But I'm sure that the other reviews did this sort of jazz already.
The things that set this phone apart for me though were the following.
When I get a new phone or tablet, usually the first thing I do is rooting it. This one was no different, about an hour after receipt it was successfully rooted and loaded with Magisk. Currently I'm still in the phase of "getting to know the phone", wherein fuckups are usual. This time again being no different - I removed some apps and apparently did something to it that the search engines - both Google and DuckDuckGo - didn't quite like, as both of them would crash upon application launch. Me in full panic mode of course, desperately trying to find the stock ROM (which doesn't seem to be present in its usual form) or a new set of GApps (which didn't resolve the issue). OnePlus does seem to offer its OTA updates in zip archives though. So I downloaded its latest update (same as what was on the device) and applied it.
That's when the nerdgasm happened.
The "update" was simply a matter of going into the settings, tapping this and that and applying the update. No recovery, no unrooting, no nothing. The update just went like that despite the phone being rooted and just having had TWRP flashed to it. I always wanted this sort of thing, which even the Nexus couldn't offer - having the cake and eating it too. Being able to root the device and muck around with it while still being able to update the device timely without too many hurdles. This fucking thing does it!!!
That is to say, after my initial nerdgasm I did find that it bulldozed over my su binary (effectively unrooting the thing), custom emoji I've set (iOS 12 because fuck Google's most recent emoji set) and some other things. But those are easy to install back, much more so than it would've been to download a whole Android release and dirty flash it, as it was on the Nexus.
Other than that, battery life, dash charging (edit: on that topic, it does remain cool like a cucumber despite getting 15-20W of power jammed into it, quite impressive!), snappiness, the usual jazz.. eh, as I said earlier that's the usual reviewer stuff. But this feature of being able to upgrade the phone while it's modified, that's something which seems to be severely underrated by those.
Oh and during kernel builds, I couldn't quite get the source to work - probably due to my lack of experience with builds of Android kernels - but I did find that this phone actually exposes its kernel config through /proc/config.gz as it should. None of my MediaTek devices do this, so that's something that I found really appealing. Always nice to see when a manufacturer exposes this information to give you a stock sort of config that you can be rest assured will work configuration-wise. And it allows you to see what the stock kernel is actually built with, which again is really nice. I quite like this! It really encourages further development.11 -
Doesn't work
I hate my life
fuck this shit
Oh I used the wrong list
*jumps from the top of the mountain* -
Funny how I can go all day not being able to think of anyone that bad, but then when I remember THAT ONE GUY from a group project in college, I can't stop ranting.
highlights:
- He micromanaged our group without adding any value on his end
- Scheduled 2 hour meetings on Friday evenings to show us his work so we could "learn and take notes"
- when the group finally reached out and asked if we could work differently, he completely shut down. like stopped replying and working completely.
- last night we were putting together our presentation, he bailed because he had an 8-HOUR date with someone he just met....nevermind that we had our calendar set a month prior
- prior to that date, he submitted code to our final release that was riddled with bugs, so I stayed up all night debugging and rewriting his parts
</rant>2 -
If any of you have been following my last few rants, you'll know I've been working on a project with a particularly difficult client, trying to meet wholly unrealistic deadlines with only one other developer.
The situation has reached the climax. The client had a call with our project manager and boss on Monday to discuss things. Despite them still not having paid a single bill since October, they've demanded the release date be moved to the 6th April. Apparently we'd agreed to release on this date, despite making no such promises, the (optimistic) deadline we were working towards has always been, since it was set about 2 weeks ago, the 16th April.
Apparently AWS migration won't take as long as we think it will, because the designers that do the CSS for this project say so, despite knowing nothing about the architecture of the requirements of the system once live (like if backups are required and what of).
The bottom line is that client is ending development with us the day after the project goes live to give it to their own in-house team. If they want us to work more after the date, they have to buy blocks of days.
To make things better, a large part of new functionality relies on an external API we can't even begin to do learning tests with, let alone integrate due to back-office errors on their end. They've had since Friday to give us our token, yet here we are.
Something tells me my holidays booked for for the first week of April are going by the wayside.4 -
My tl sits in The room next to me.
Today he came in to me and asked me how it looked with The release.
I asked him What he meant by that.
"Well, we had release on friday, but you never contacted me about it."
Me: "What? Friday? Since when did we have releases with two weeks inbetween? And why havent I gotten this news?"
Tl: "Well, we don't usualy, but you know... Any way, can you have it done by today?"
Me, 10sec away from a cardiac arrest: "NO, are you insane? You have to tell me about this earlier than the same day."
Tl: "Yeah, but there's been so much work recently.. Well, we'll talk later."
Omfg...6 -
Today I released the next versions two of my company's Android projects. Today was a good day.
Also, releasing on a Friday afternoon FTW! (they are beta releases, so I'm good).1 -
So here it is. Apple release, second round.
This time, uploads to AppStoreConnect took 3 hours and 40 minutes. Submission of the app was at 0.04, just after the planned launch day. Android submission tomorrow.
Tomorrow, and Friday are public holidays.
I'll have to work those, at best being able to not work on the weekend. The client has already told me he's calling me tomorrow morning to talk about things.
I don't want praise, but I'd like him to respect that while I may just be a lowly developer, I would like to have a life.
When are the happy times coming? -
Two architectures to support, on one everything went smoothly, other one I spend since Monday till yesterday 2am to make it work. Now time for half-day meeting and if it compiles in the meantime, I can release today before leaving work. Sounds like a solid plan, Friday afternoon release. What could go wrong? And I hoped it will work nicelly on Monday, latest Tuesday.
-
Some background:
About 2 months ago, my company wanted to build a micro service that will be used to integrate 3 of our products with external ticketing systems.
So, I was asked to take on this task. Design the service, ensure extendability and universality between our products (all have very different use cases, data models and their own sets of services).
Two weeks of meetings with multiple stakeholders and tech leads. Got the okay by 4-6 people. Built the thing with one other guy in a manner of a week. Stress tested it against one ticketing service that is used in a product my team is developing.
Everyone is happy.
Fast forward to last Thursday night.
“Email from human X”: hey, I extended the shared micro service for ticketing to add support for one of clients ghetto ticketing systems. Review my PR please. P.S. release date is Monday and I am on a personal day on Friday.
I’m thinking. Cool I know this guy. He helped me design this API. He must’ve done good. . . *looks at code* . . . work..... it’s due... Monday? Huh? Personal day? Huh?
So not to shit on the day. He did add much needed support for bear tokens and generalized some of the environment variables. Cleaned up some code. But.... big no no no...
The original code was written with a factory pattern in mind. The solution is supposed to handle communication to multiple 3rd parties, but using the same interfaces.
What did this guy do wrong? Well other than the fact that he basically put me in a spot where if I reject his code, it will look like I’m blocking progress on his code...
His “implementation” is literally copy-paste the entire class. Add 3 be urls to his specific implementation of the API.
Now we have
POST /ticket
PUT /ticket
POST /ticket-scripted
PUT /ticket-scripted
POST /callback
The latter 3 are his additions... only the last one should have been added in reality... why not just add a type to the payload of the post/put? Is he expecting us to write new endpoints for every damn integration? At this rate we might as well not have this component...
But seriously this cheeses me... especially since Monday is my day off! So not only do I have to reject this code. I also have to have a call now with him on my fucking day off!!!!
Arghhhhhh1