Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "milestone"
We passed a milestone: 250,000 phpunit testcases.
If it weren't for a heavily parallelized build pipeline which splits it out over 20 servers, it would take about 7.5 hours to complete.
Not hating on PHP, and without tests it would truly be hell...
But still, fucking hell, we outgrew PHP.
Not having a solid type system just means you either accept more bugs, or write thousands of unit tests to guard all the foundational cracks in the system.
On the bright side, I get a coffee break after every commit 😄22
First I wanna say how grateful I am that devRant exists, because my friends either don’t understand this vocab or don’t care lol.
Last week I worked on a pretty large ticket, opened a PR with 54 file changes. Just to follow standards I set the PR milestone to a future release version, but the truth is I didn’t care which version this work ended up in— I just needed it to go into the develop branch asap.
Since it was a large PR there was some expected discussion that prolonged its merging, but in the meantime I started a second branch that depended on some of the work from this branch. I set the new branch’s upstream to develop, fully expecting my PR to merge into develop, since that’s what I set the PR base to.
I completed all the work I could in the new branch, and got two colleagues to approve the initial PR so it would be merged into develop, I could add the finishing touch and get this work done seamlessly before the week was over. They approved, it got merged, I pulled develop, and… my work wasn’t there. I went to look at my PR and someone had changed the base branch to a release branch. It was my boss, who thought he was helping. (Our bosses don’t actually work on the same team as us, so he didn’t know. it’s weird. We have leads that keep track of our work instead.)
I messaged him and told him I really needed this in develop, knowing our release branch won’t be in develop for probably another week. I was very annoyed but didn’t wanna make him feel too bad so I said I’d just merge the release branch into my new branch. So many conflicts I couldn’t see straight. His response was “yeah and you’ll probably have a bunch of package manager conflicts too because that’s in that release.” He was right— I have so many package manager conflicts that I can’t even see how many compiler conflicts there are. I considered cherry picking my changes, but the whole reason I set develop as my upstream was to avoid having any conflicts since I’m working in the same functions, and this would create more.
So I could spend the next (?) days making educated guesses on possibly a thousand conflict resolutions, or I can revert my release branch merge and quietly step back and wait for the release branch to be merged into develop.
I’m sure cherry picking is the best option here but I’m genuinely too annoyed lol, and fortunately my team does not care to notice if I step back and work on something else to kill time until it’s fixed automatically. But I’m still in dire need of a rant because my entire plan was ruined by a well-meaning person who messed with my PR without asking, so here is that rant and I thank you for your time.8
So now that Covid is apparently "gone", management wants us to come to the office to participate in daily team building events to hype up people to commute full time...
but still gotta finish those milestone deliveries while having too many meetings and deadlines.
Murphy is watching us from above with a shit-eating grin.
Had anyone experienced with an impatient boss who require you to complete the project in the month you just recently got hired?
Here's the story, I recently got hired by a company, joined on 1st April 2022, the boss expect me to complete the app for Android and iOS by the end of this month. (An e-commerce applications exactly like shopee.com) Without providing me the Backend ApI , that they mentioned. They just gave me a and expect me to know what's happening at the backend.
He require me to give him a specific date that I can launch the app to play store and Apple store. (From my experience, it take days, weeks or months). He need a milestone of what I need , did , and will do (which predictably that they will reject any new ideas proposed) .
I even considering to quit, but I need opinions. Am I just too sensitive or there's something wrong?18
The scary thing about burnout is that you usually don't realize you are burning out before it's too late.
Personally, at least, I've worked on projects that just felt a little intense at the time, but after taking a step back due to holidays or hitting some milestone I realize I never want to have anything to do with it ever again. One project makes my stomach drop even today every time I see the code; Not because the code is bad, but how it takes me back to how miserable I was without admitting it to myself.
The biggest red flag I look for is when I'm tempted to work on stuff in my free time. When this starts seeming like a solution there's a serious problem with the project that needs to be addressed.2
New JoyRant TestFlight build 11:
* Posting Rants
* Improved Notifications Category selection UI with unread indicators (screenshot attached)
Posting this rant from JoyRant right now 😄
The app is now in a state what I consider to be the first major milestone.
There are still features missing (see github https://github.com/WilhelmOks/...) but the most important and most frequently used stuff is done.
I got assigned a milestone we had delayed twice already. It needs to be ready for tomorrow, it's harsh but doable.
Guy from another team, looks at my folder system during the presentation, something like
"src/views/users/view-all/view-all.template.html" and starts whining "hurr durr this isn't good tho, you should have chosen a significant name, it's impossible to understand what this file does".
Honest thought: if you can't navigate through folders, you shouldn't be writing code in the first place.4
I chose my next milestone as a dev. I’m gonna ask a question on stackoverflow. I just need a question 🤔14
Completely forgot to update what was going on with my potential role shift. Long story short, it was approved by the damagement. That’s nice.
I only have to get to a major milestone in my current giant of an IaC project and transfer enough knowledge to leave it in my current team mates’ hands. Looks like we’ll be there pretty much next week and I can switch at the start of 2023. Life’s good.1
#Suphle Rant 5: Xavi
When I first detailed what it was I was working on to my brother and its expected impact on the industry, I must have done so with an enormous amount of enthusiasm that he impatiently began to request when the dream will be realised. He didn't give a shit about specifics of where I was on the timeline. He kept repeating the same question. Exasperated with the futility of my explanations, I replied that I'd be done by November as this was far beyond my estimated completion date
Every milestone (e.g. my birthday) I've expected it to be ready at has come and gone, including the unrealistic November. My present state of mind is far from the optimistic pioneer I was then. I'm just going with the flow and won't be surprised if it's not officially released by the end of the year
This gonna be me in 2072, convincing anyone who cares to listen that I'm fleshing out the docs and that the reason the release date keeps getting pushed back is because nobody has shown interest in either using or contributing to it