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 - "release notes"
This one is about the SJWs in the software development community.
SJWs in general are a bunch of crying assholes.. software developers who are activists in online software dev sites are even worst.
Days ago, my visual studio 2019 RC notified me of a new version so I decided to look at the release notes. It was then when I read the most stupid fix ever included in a change log: "Visual Studio installer welcome image contains offensive element for Chinese."
Do you wanna know what that super offensive element in that image was? A GUY ON A BIKE WEARING A GREEN FUCKING HAT. Apparently in China this means someone's wife or sister is a prostitute.
I clicked on the link to read the actual feedback... and holy shit isn't that Chinese idiot an actual raging cunt.
In his stupid OP he is quoted saying: "this is serious".. FUCK YOU... your entire existence CAN NOT and SHOULD NOT be considered SERIOUS at all you whining dick sucking asshole.
And to make matters worst: a "fix" was released for this within days and immediately made available to everyone.
Motherfucking assholes in Microsoft took this guy's shit seriously and were scared shitless not to offend a snowflake abomination of an excuse of a human being.
Who gives a crap.. if you are offended and you publicly announce it, you are telling everyone that you are a pathetic child who can't control his feelings and wants everyone else to do it for him/her.
Well assholes at Microsoft and the Chinese offended by this shit, removing the green hat is offensive to the Irish people... would you re-instate it? NO YOU WON'T.
Why? well this is easy to answer: Irish people are white. White people, by standards of SJW cucks, can't be offended and reverse racism doesn't exist towards white people.
I hope that Chinese cunt, and if he has a girlfriend which I very much doubt since he had time to make that stupid feedback in the first place, to die slowly, bleeding from every hole and some newly created ones too, while watching his girlfriend get fucked by a high-ranking member of the ruling communist party of his Chinese gov and she is enjoying it and with a big smile on her face just so he can die feeling like the shit human being he is.
People on that feedback thread have urged MS to revert the change, asked MS to direct resources at fixing things that are as trivial as this but yet to be addressed... only MS didn't give a fuck.
Here's the link to the feedback thread for those interested: https://developercommunity.visualstudio.com/...
If that asshole is here on devRant, here me out you raging cunt: I couldn't give a fuck less about you shit feelings or your stupid activism but I do care when idiots like you influence great software (incl. open source projects) just to feel good about yourself, to feel like you've accomplished something this week.
FUCK YOU all the way to hell.
For all other assholes (AKA SJWs) in the software community: software/computers don't give a fuck about your feelings. I'll beat you down to the depths of hell if you come at me with your progressive/equality/political correctness crap any day of the week... you just pick the day and I'm happy to oblige.49
So this chick has been super nice to me for the past few months, and has been trying to push me towards a role in security. She said nothing but wonderful things about it. It’s easy, it’s not much work, it’s relaxing, etc.
I eventually decided I’m burned out enough that something, anything different would be good, and went for it. I’m now officially doing both dev and security. The day I started, she announced that she was leaving the security team and wouldn’t join any other calls. Just flat-out left.
She trained me on doing a security review of this release, which basically amounted to a zoom call where I did all of the work and she directed me on what to do next, ignored everything I said, and treated me like an idiot. It’s apparently an easy release. The work itself? Not difficult, but it’s very involved, very time consuming, and requires a lot of paper trail — copying the same crap to three different places, tagging lots of people, copying their responses and pasting them elsewhere, filing tickets, linking tickets, copying info back and forth to slack, signing off on things, tagging tickets in a specific way, writing up security notes in a very specific format etc. etc. etc. It’s apparently usually very hectic with lots of last-minute changes, devs who simply ignore security requests, etc.
I asked her at the end for a quick writeup because I’m not going to remember everything and we didn’t cover everything that might happen.
Her response: Just remember what you did here, and do it again!
I asked again for her to write up some notes. She said “I would recommend.. you watch the new release’s channel starting Thursday, and then review what we did here, and just do all that again. Oh, and if you have any questions, talk to <security boss> so you get in the habit of asking him instead of me. Okay, bye!”
No handoff doc?
Not willing to answer questions after a day and a half of training?
• She was friendly.
• She pushed me towards security.
• She said the security role was easy and laid-back.
• I eventually accepted.
• She quit the same day.
• The “easy release” took a day and a half of work with her watching, and it has a two-day deadline.
• She treated (and still treats) me like a burden and ignores everything I said or asked.
• The work is anything but laid-back.
• She refuses to spend any extra time on this or write up any notes.
• She refuses to answer any further questions because (quote) “I should get in the habit of asking <security boss> instead of her”
So she smiled, lied, and stabbed me in the back. Now she’s treating me like an annoyance she just wants to go away.
I get that she’s burned out from this, but still, what a fucking bitch. I almost can’t believe she’s acting this way, but I’ve grown to expect it from everyone.
But hey, at least I’m doing something different now, which is what I wanted. The speed at which she showed her true colors, though, holy shit.
“I’m more of a personal motivator than anything,” she says, “and I’m first and foremost a supporter of women developers!” Exactly wrong, every single word of it.
God I hate people like this.21
One of the better filler release notes I guess. Not as good as Slack or Discord but still better than Google.1
Oh, well, of course ...
I thoroughly enjoy that both Google apps have different bullet point styles.1
// devRant unofficial UWP update (v2.0.0-beta7)
After "Active Discussions" (implemented in v2.0.0-beta5), it was time to implement the last missing app section, "Collabs".
This is the biggest update since the start of the public beta, over 100 changes (new features, improvements, fixes).
- Support for Collabs
- Notifs Tabs
- & more... read the entire changelog here: https://jakubsteplowski.com/en/...
Microsoft Store: https://microsoft.com/store/apps/...
I'm really happy to announce that the unofficial UWP client has now 100% of the features available on the official Android and iOS apps (if we don't count Push Notifs 😝 but they will arrive soon too).
It took several months of hard work, but I made it... it's here, it reached the level I wanted to reach since the beginning of this project (May 2016) (if we don't count Push Notifs).
I did it a lot of times, but I think they deserve it everytime, I would like to thank all the people who made this possible, all the active users, who opened issues, suggested features, or just used my app and had fun, posted positives (and negatives, motherfuckers, just kidding, maybe) reviews on Microsoft Store etc.
The entire community who made me want to do this project.
You're amazing guys!
Of course this is not the end of this project, I want to bring the app out of the beta and support it until I will be able to do it, releasing updates almost simultaneously with @dfox and @trogus.
Planned to be done:
- Support for Anniversary Update
- Push Notifs
- Custom Themes
- Close the 15+ issues (features requests, fixes) on the issue tracker on GitHub
- Ranti by @Alice: Your devRant Assistant <- I really hope it will become a thing :)
- Your future suggestions -> post them here: https://github.com/JakubSteplowski/...
Thanks for the attention,
You know it's going to be an interesting day when you see a release note containing "migration" and "cross your fingers" in the same sentence 😅2
Let's share information! Communicate! How do we do it? Via email!
You got question? Send an emai!
You want to share some excel? Send an email!
Not sure who to ask? Send the email to everyone!
Have a 100 message long email thread and then need some help? Send the whole fucking thread to me and just add "what do'ya think?"!
Send some attachment in email and then 2 weeks later refer to it saying "but I sent the file to you!"? Well surely I can remember your special email from the hundreds of email I get every week.
I did complain to the mangers that why the hell do we have these mega-email-threads? Why do you send all the meaningles release notes to the whole company? The anwer is simple: all information needes to be transparent and if you don't need the info, then just don't read the email!
And fuck you, you CEO wanna-be who sends seasonal greetings through his secretary and thinks anyone gives a shit.4
Happiness is: scrolling through the release notes of a software you use and unexpected finding your changes mentioned there 😊1
Dat moment when your contact person phones you and ask If you delete the whole Release Folder...
YEAH SURE I WAS IT BECAUSE I LIKE TO WORK ON WEEKEND
Fyi: FTP with one user for everyone - harhar stupid bricks
So... as a follow-up to my previous rant (https://www.devrant.io/rants/899731)
I happened across this today and started giggling internally.
When your users are this dumb, it's hard to decide between making things obvious (but inviting potential errors) vs. adding a step to reduce the chance of errors (but potentially confusing people).
It would be easier if people actually read release notes...2
Project manager, who i've complained in the past is neglecting critical things that he doesn't want to do, decided today to cancel our weekly planning meeting, to have the below conversation with me 1:1. Its very long, but anyone who has the will to get through it ... please tell me it's not just me. I'm so bewildered and angry.
Side note: His solution to the planning meeting not taking place ... to just not have one and asked everyone to figure it out themselves offline, with no guidance on priorities.
PM: I need to talk to you about some of phrasing you use during collaboration. It's coming across slightly offensive, or angry or something like that.
Me: ok, can you give me an example?
PM: The ticket I opened yesterday, where you closed it with a comment something along the lines of "as discussed several times before, this is an issue with library X, can't be fixed until Y ...".
"As discussed several times" comes across aggressive.
Me: Ok, fair enough, I get quite frustrated when we are under a crunch, working long hours, and I have to keep debugging or responding to the same tickets over and over. I mean, like we do need to solve this problem, I don't think its fair that we just keep ignoring this.
PM: See this is the problem, you never told me.
Me: ... told you what?
PM: That this is a known issue and not to test it.
Me: ..... i'm sorry ..... I did, that was the comment, this is the 4th ticket i've closed about it.
PM: Right but when you sent me this app, you never said "don't test this".
Me: But I told you that, the last 3 times that it won't be in until feature X, which you know is next month.
PM: No, you need to tell me on each internal release what not to test.
Me: But we release multiple times per week internally. Do you really need me to write a big list of "still broken, still broken, still broken, still broken"?
PM: Yes, how else will I know?
Me: This is documented, the last QA contractor we had work for us, wrote a lot of this down. Its in other tickets that are still open, or notes on test cases etc. You were tagged in all of these too. Can you not read those? and not test them unless I say I've fixed them?
PM: No, i'm only filling for QA until we hire a full time. Thats QA's job to read those and maintain those documents.
Me: So you want me to document for you every single release, whats already documented in a different place?
PM: ok we'll come back to this. Speaking of hiring QA. You left a comment on the excel spreadsheet questioning my decision, publicly, thats not ok.
Me: When I asked why my top pick was rejected?
PM: Yes. Its great that you are involved in this, but I have to work closely with this person and I said no, is that not enough?
Me: Well you asked me to participate, reviewing resumes's and interviewing people. And I also have to work extremely close with this person.
PM: Are you doubting my ability to interview or filter people?
Me: ..... well a little bit yeah. You asked me to interview your top pick after you interviewed her and thought she was great. She was very under qualified. And the second resume you picked was missing 50% of the requirements we asked for ... given those two didn't go well, I do think its fair to ask why my top pick was rejected? ... even just to know the reason?
PM: Could you not have asked publicly? face to face?
Me: you tagged me on a google sheet, asking me to review a resume, and rather than tag you back on 2 rows below ... you want me to wait 4 days to ask you at our next face to face? (which you just cancelled for this meeting)
PM: That would have been more appropriate
Me: ..... i'm sorry, i don't want to be rude but thats ridiculous and very nit pick-y. You asked my opinion on one row, I asked yours on another. To say theres anything wrong with that is ridiculous
PM: Well we are going to call another team meeting and discuss all this face to face then, because this isn't working. We need to jump to this other call now, lets leave it here.5
androidx.activity 1.0.0-alpha01 release notes:
"Pending input events (such as clicks) are now canceled in onStop()."
Welcome in 2018! It just took 10 years to fix this ... better late than never 👍1
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.
- 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
Mozilla launched Firefox 72 for Windows, Mac, Linux and Android which includes fingerprinting scripts blocked by default, less annoying notifications and Picture-in-Picture video on macOS and Linux. See the release notes for the details of these features and other changes.
I don't think it should take "years" to develop a card sorting mechanism.
Android devs do you agree?
( This is picked up from the release notes of Trello. )6
When the update schedule for a service you rely on involves sending release notes for major (sometimes breaking) updates on Saturday...in preparation for a release first thing on Monday morning.
So I just noticed while looking at our release notes, we got some new members of our Shanghai team. Their English names are:
Paul, Jonas, and ....
Every time I see his name I sort of chuckle...4
South Africa Release notes version v3.0.2
In 1994 SA underwent one of the biggest system upgrades since 1948. In this new rolling release since the system update called apartheid the system has been annexing resources, locking it down, making it closed source, closing it off community updates and from global updates and minimizing services across the board. On 27 April 1994, the new democratic system update was released with a new system monitor, release resources and balancing efficiency in the system. Though there were remnants of the old code in the system, it was being rewritten by a new generation of users, open source resources were established, giving users the right to choose among themselves how to grow the system , and how to better the experience for all.
In 1999 a new system monitor was created by the users, it wasnt as popular as the ground breaking Madiba release but it was a choice by the community to move forward and grow. The system was stable for a few years, new users were able to develop more on the system, making it more lucrative monetary wise. There were still remnants of the apartheid code but the new generation of developers worked with it making it there own, though they had not yet had admin rights to help change the system, they created a developer culture of their own. A new system resources balancer was introduced called BBEE, that allowed previous disadvantage users more admin rights to other system resources, helping the user base to grow. Though the balancer was biased, and flawed it has helped the system overall to grow and move forward. It has major holes in security and may flood some aspects of the system with more outdated software patches, users have kept it in its system releases until the resource balancer moved the system into a more stable position.
The next interim system monitor release was unexpected, a quiet release that most users did not contribute towards. The system monitor after that nearly brought the system down to a halt, as it was stealing resources from users, using resources for its own gain, and hasn't released any of it back to the system.
The latest user release has been stable. It has brought more interest from users from other countries, it had more monetary advantages than all other releases before. Though it still has flaws, it has tried to balance the system thus far.
Bug report as of 16 Feb 2018
*User experience has been unbalanced since the 1994 release, still leaving some users at a disadvantage.
*The three tier user base that the 1948 release established, creating three main user groups, created a hierarchy of users that are still in effect today, thought the 1994 release tried to balance it out, the user based reversed in its hierarchy, leaving the middle group of users where they were.
*System instability has been at an all time low, allowing users to disable each others accounts, effectively
killing" them off
*Though the infrastructure of the system has been upgraded to global standards ( in some aspects ) expansions are still at an all time low
*Rogue groups of users have been taking most of the infrastructure from established users
*Security services have been heightened among user groups though admins were still able to do as they pleased without being reprimanded
*Female users have been kicked off the system at an alarming rate, the security services have only kicked in recently, but the system admins and system monitor has not done anything about it yet
Bug fixes for a future release:
*Recreating the overall sysadmin team. Removing some admins and bringing others in
*Opening the system more globally to stabilize it more
*Removing and revamping the BBEE system, replacing it with more user documentation, equalizing the user base
*Giving more resources to users that were at a disadvantage during the first release
*Giving the middle group of users more support, documentation and advantages in the system, after removing the security protocols from the user base
*Giving new users who grew up with the post 1994 release more opportunities to help grow the system on a level playing field.
*Establishing the Madiba release principles more efficiently in the current system1
If you give a mouse a cookie is all too real. Started sending out release notes to those who benefit from the changes and they're now asking for access to our ticket system 'just because'2
So here I am coming to the end of the week after getting The Porcupines big web project into production. Pulled a 38 hour straight from Sunday to Monday chopping wood to make the thing fly. Pulled in other programmers and content creators to get the site full of something we did not have a week before. The fun part was having the account manager right there for 30 plus hours and actually seeing what it take to save a project when the client just thinks "it's just code". Now the boss has is asking for a list of all the work out of spec as they are bitching about the extra cost. These were the clients who did not read the functional spec and raked me over the coals after release that the home page did not match the design (the home page matched the design). I warned my team this would happen. They get all swept up in the hype and We can win! frame of mind and you can bet when the bitching starts it will come back to the paperwork you did at the beginning and the change requests and productions systems reports so you can wave it in front of ungrateful clients and not end up sad. Make sure you keep notes and document all of the requests and changes from internal and external even if you do not have to. one day it will save your ass and you will be able to whip it out and be a smiling motherfucker.
This change *shouldn’t* break anything. Please keep your eyes open for strangeness.
Every. Release. Ever.
Is it normal for "enterprise" software to have 14+ pages of known issues in the release notes, including issue descriptions that use phrases like "may lead to data corruption" and "may cause the cluster to crash"??2
What do you think, does Google just have really good code structure that allows re-use at this level, or are they just coordinating release notes?2
CentOS 8.1 has hit the downloads page people's!!!!
I guess it's too early for release notes yet but what ever, I know where my next few days will be spent making sure projects can be lifted up without to much hassle.
Having to explain for the umpteenth time what the difference is between App Release Notes & App Description right before a release.