Fedora's warnings are on point

you know it

Act I

Me (Lead Developer), Boss (Head of IT), CEO

> enter stage left CEO

CEO > "Alright Boss, give it to me straight. Are we going to be able to release app x by this date?"

Boss > "Yup we'll have a beta release on that date"

> exit stage right CEO

Me > types long email to Boss outlining exactly why we won't be able to release app x anywhere near that date, beta or otherwise, because:
1. We have a development team of 2
2. I've never developed an iOS app before
3. Developer 2 is still trying to understand git, because
3a. Developer 2 isn't even a developer (but he's doing iOS front-end so w/e)
4. We don't have the required database systems in place
5. Or CRM
6. Or CPQ
7. We'll need to conduct a security audit

Boss > "yeah, but CEO is gonna need to hear that date a few more times before he can fully understand"

Me > *internally screaming BUT YOU HAVEN'T TOLD HIM THAT AT ALL*
"ok cool just glad we're on the same page on that one"

My biggest pet peeve at the moment is people without any development experience using version numbers.

Me: "Communicating a release date for the feature towards clients is dangerous, we have a developer shortage, and currently don't really have enough capacity to..."

Manager: "What we release next month doesn't have to be perfect, it is just a v1"

Me: "You mean it's a beta? If that's the case, could you maybe differentiate the requirements of the beta, let's call it a 0.1.0, versus the 1.0.0-rc, the release candidate?"

*Feature is eventually merged into production, barely in a beta state*

Manager: "So I have some ideas for the v2"

Me: "You mean 1.0.0"

Manager: "Let's compromise and call it v1.5"

Me: "Let's compromise, you stop communicating release dates, AND you stop using version numbers..."

Manager: "That's not a compromise..."

Me: "...I wasn't finished... And I won't respond to the recruiter who just offered me a better paying job"

Firefox Quantum is the only software in beta stage I know of, that is more stable than the release one. I have to admit that I am somewhat of a fanboy when it comes to Firefox since I have been using it for the past 12 years. I never admitted it's quirks even though I secretly knew chrome had a better performance and stability lately. This rebirth gives me so much hope! YES! Firefox is not dieing!

Only 90s kids will remember this:

"Release"

I HOPED I WOULDN'T BE BALD AS MY DAD BUT AT THIS RATE I WILL BE HAIRLESS FROM TEARING IT OUT ON MY BLOODY OWN

I got hired for cleaning up a 2 year project of rushed spaghetti code , where they previously only had 1 programmer aND HE WROTE 37 THOUSAND LINES OF CODE!

OH WE NEED A NEW FEATURE?! LEMME JUST RESEARCH THIS COMMENT-LESS CRAP FOR MULTIPLE MILLENIA BEFORE I CAN GRASP WHAT THE FLYING FRICKIN FRIDGE CODE DOES

To top it off, I've about ONE MONTH LEFT BEFORE BETA RELEASE TO FIX THE CODE!

I'm super grateful for this job as it's my first programming job BUT I'M GONNA SET THE REPOSITORY ON FIRE SOON AAAAHHHHHH

HOW CAN YOU, THE PREVIOUS PROGRAMMER, WORK IN THIS ENVIRONMENT WHERE MOSTLY ALL FILES ARE +2000 ROWS OF UNDOCUMENTED CODE

OH AND JUST GOT A MESSAGE FROM THE PREVIOUS PROGRAMMER:
"You can just remove the unused code and refractor it some, izi"

IZI MY SHITTY POOP CAR
AAAAAAAAAAAAAAAHHHHH!!!

Now with that out of the way, how would you recommend handling a stressful release deadline?

COVID variants should adopt a semantic versioning, rather than using greek alphabetics.
COVID v.19.2.34
COVID V.22.1 Beta (testing in US)
COVID v.22 release 1 (being tested somewhere in London)
COVID v.22 nightly builds (still brewing in China)

After 8 iTunes Testflight Beta approvals for my app ... better still, I got hte app approved for the App Store a week ago to "de-risk" our "final submission" ... That's 9 approvals for my app, and we're ready to submit version 1.0.0 and actually release on the store. We take last week approved app and "developer reject" if to make room for the final tweaked version (minor tweaks, minor bugfixes). Submit version 1.0.0., plenty of time before it needs to be released.

But, what's this? "Meta Data rejected" for v1.0.0 because some piece of shit at Apple wants to watch a video of the app working with our hardware. What about the previous 9 approvals with the demo account connected to the demo hardware?

So we send a video within 1 hour of their unexpected request about the very foundational fucntionality of our app. That was 24 hours ago and these fucking assholes haven't even responded, no sign of when they will trouble themselves to respond. Pure limbo.

All the work up to this point was to "de-risk" their infamously shitty review process and all of it was in vain because it's somehow brand new information that our app works with our hardware.

Holy fuck, what a bunch of power-tripping assholes. All I can do is pace around and review the previous 2 months in my head to figure out what I could have done better. But I could not possibly have expected that after all the Testflight Beta approvals and after the recent App Store approval, that they would suddenly doubt that our software actually works with our hardware!!!!!

FUCK YOU APPLE!!!! FUCK YOU WITH ALL MY HEART!!!!!!

This is a friend's story:

So I've been trying to upload a free sticker pack for iMessage to AppStore for a while now. Why "trying"? because it keeps getting declined for the silliest reasons. It's nothing complex: just a bunch of our company's stickers about dev life. "Stickers for devs, from devs."

The first time Apple has declined the app because of the overall design, the second time it was because we used iMessage in the title. But this time it makes no sense at all. This is the message I got from Apple:

"Your app contains references to test, trial, demo, beta, pre-release or other incomplete content.
Specifically, some of your app’s stickers have “beta” references."

Huh? Check out the pic - one of our dev-related stickers says "still in beta". I guess Apple took that way too literally. Good thing they didn't tell me my app was too buggy because it has a sticker of a bug which says "it's not a bug, it's a feature"...

On second thought, what if AppStore is a modern-day Genie? Maybe I should add a sticker that says "Apple owns me $20 million in stock"? Or just one that says "Apple approves this sticker pack".

#Thisneverhappens_on_googleplay #appstore_make_a_wish #rookout

Two years ago, I developed an security app for Android as a school project. I didn't like teamwork at school (you know, you do all the work and everyone else is getting the same grade you receive, specially if you are the nerd of the class), actually I hated it, so I made it alone.

Its name was "Alex" and was a simple "panic button". You can configure two emergency emails and phone numbers (contacts only, not police) and, if you're in danger, you just have to press the button and the app is gonna send two messages/emails to your contacts: the first one, to tell where are you (GPS, only the name of the place) and that you're in problems. The second one with an audio/photo file of the situation.

Sounds like a great app, and I tested it few times. The reason I didn't continue with this is that I got my first job and I had not time, and that, tree or four months later, the government (of the city) launched a similar app. Less sophisticated, but I think it's still useful: "No estoy sola"(I'm not alone). I haven't tested it cause I don't trust on the authorities, I'd preffer to send my location to a friend through messenger app instead.

I don't know if I should re-work this app (I didn't released it, I just have the beta) or work on something else. I'm afraid that, if I release it, someone could die or get kidnapped because of a bug or something going wrong with the app :c What do you think?

The app I'm using right now... devRant unofficial UWP.

It started by chance, I wanted since years to release an app for Windows 10, but never something like this.
I found devRant in 2016 and I just wanted to use it on my Lumia 950, so I opened Visual Studio and created a very simple client to get data from the web version.
After a few builds I decided to release it on the Microsoft Store as "devFeed (Beta)" (a bit later renamed to "devRant unofficial UWP").

Today, after almost 2 years, thanks to the huge support from @dfox and all the users, I'm releasing the 55th update. 😁

Thanks!

Yet another unstable beta, released to our customers 😥

The company bought an iPad so I can test my work on a real device, but I can’t use it because the latest iPadOS beta release isn’t compatible with the latest Xcode 11 beta release 😒

When I got the current job I started to work on an Android app that a coworker which left the company was doing.
The app was ready at about 40% and was barely usable, it lacked a lot of features and multithreading so with a huge amount of data it used to crash (Android doesn't allow you to make the app freeze for more than 2-3 seconds, it considers that the app is not responding anymore).
After a week or two the work to do was still huge, but one day one of my coworkers came in and ask me if I was able to release a beta for a client the same day... Unexpected deadline.
I spent 8 hour fixing as many bugs as possible and adding multithreading in the most weak parts.
I did it but it was so stressful and the result wasn't even great. In fact I finished the stable version 7 months later.

1 - Spend 6 months building an app with Flutter
2 - Try to add in-app purchase. Must upload an apk to google console and register a product
3 - Must launch the app so the product is activated
4 - Console complains apk must contain 64 bits version
5 - Go to the issues tab on github and find a solution
6 - Implement the solution, recompile and send 2 apk files to Console
7 - Did not work...
8 - Find out maybe the console will allow just on closed alpha and beyond
9 - Put apks on closed alpha and fail because the Console wants a new apks with increased version codes...
10 - Recompile and send apks
11 - Console won't allow launching unless the format is using the new App Bundle
12 - Flutter does not support App Bundle with 32 and 64 bits...
13 - See issue about it saying the possible fix is in beta version, just need to update... What could go wrong?

I just wanted to release a damn app

I hate that shit

NodeJS 10.0.0 is out.

The biggest features I see is the release of N-API. I always wanted to use that but never did as it was in beta. It will be exiciting to use it with a new project!

A project I've been a part of for two years finally exited beta this morning! It was so exciting watching it grow and and change into what it is today. The project in question is Storj.io. A decentralized cloud storage. When I first joined the project, literally all it did was create junk files to take up space. Now it is a thriving network storinf over a petabyte of data without the possibility of it ever going offline.

step 1) open and browse producthunt for new dev tools to use and try out
.
step 2) opens dev tool/app's website *ooh nice landing page*
.
step 3) tries to find api and documentation, scrolls to bottom of the webpage
.
step 4) "we are still in private beta, sign up to be notified about the final release!"
.
step 5) lol *sighs* bookmarks tab before closing it
.
step 6) repeat step 1
.
.

Ubuntu 18.04 official release today!

And if it sucks, switching to Manjaro. It freezes on me once, and I'm done. I've been using the beta and it's been AWFUL (I know it was a beta, but I wanna use my computer w/o random freezes)

When a service has not yet seen release of version 1, and you are asked to start using version two which is still in beta like version one 🤦🏼‍♂️

Project: Angular 11

Package doc 2.1: For Angular 13+
Package release 2.1: For Angular 12+

Me: Well, this package solve our problem but it need Angular 12 or 13 to run, so do we go for 13 ?

Team: yep,the update is on schedule so take it and update it later.

Me: We can also go to 14 directly.
Team: No, we prefer LTS version

...some weeks later...

Team: Update to 13 complete !

Me: Yes ! Let's go !

...Install package 2.1...

... Compilation...

🚫 Angular 14 is required for version 2.1

Me: are you fu***** kidding?

Final word: please, keep a good documentation on version requirements 😁

(The package has currently a 3.x in beta to solve the 2.1 angular 14 problem because why not 🤷)

TLDR; macOS wouldn’t update to the version I needed because I have a 3rd party SSD. All I needed was a firmware update only found deep within a google search and a secondary SO answer.

I have a video edit project this weekend. No big deal.

Except that the Final Cut Pro project was saved in the latest version of FCPX, for which I need latest MacOS version

As a music producer on the side, I had heard the new file system of MacOS High Sierra would possibly break audio plugins. I didn’t bother updating until now. Looked further into plugin problem, it would be simply a broken hard link which I can easily fix. No big deal.

Except that I have upgraded my MBP SSD from 256gb to this 3rd party 480gb SSD. macOS does not recognize this SSD as compatible with update. No big deal. Simple google search for a terminal command would do the trick.

Except that I found and tried several solutions, including wasting an entire hour updating the original ssd and booting from that to try to update it.

Nothing worked, but deep down in the google search, found in a secondary answer on SO, there was a link for a beta release of a firmware update for the SSD that took two minutes to install, and I was finally able to update.

That firmware update needs to be more prominent everywhere. Wasted well over 3-4 hours updating crap, swapping out SSDs, and googling when all I needed was a fucking firmware update.

Hi!

Im planning to switch for a remote company. I have 2 years of internship and 1 year of full time experience.

I also have some GitHub repos where I played around with JS frameworks and I will soon release the beta version of a puzzle game I made with React Naive in my freetime.

Im also planning on creating a simple website for myself on GitHub pages.

Would this be enough for a mid-level fully remote frontend developer position?

Thanks for the answers in advance!

Holy shit! Samsung is literally on fire these days... Firstly, they release the Linux on Dex beta with Ubuntu support and now they announced the new UI for their next phones which is fucking amazing in my opinion.

Do you guys version pre-release projects (Beta, Alpha) as for instance “Beta 0.9”, or “Beta 1.9”? I’m asking because I don’t know which one seems more clear

Hey everyone!

Me and my team have been working very hard to create this programming language which people thought impossible to make. After years of work/research and hard-work we are now announcing the first beta release of this programming language. This programming language which we call "English_Code" is going to be revolutionary since it understands any English sentences. Now the programmers can finally code in English without learning the if-else, loops and other syntax keywords. Errors will be shown in pure English and your managers can now understand your code.

Anyway, let us know what you think, and we hope you enjoy!

"Gmail was launched as an invitation-only beta release on April 1, 2004 and it became available to the general public on February 7, 2007, though still with beta status."

Then read this, and consider the date. And the fact about how blatant the intent was. I can't believe I never thought about it.

In a world of Alpha, Beta, and Sigma males, be a Stable Release Male.

Spends 9 months on the side developing a library for analysis of a specific programming language. No help, entirely my own work. There's various tools built upon this library. Incorporates project management, an effective build system capable of parallel and distributed builds, a packaging system...

Beta release the library. Wait four months. Ask the community for who's been using it so I can get feedback and other comments. Majority of the comments follow a specific pattern.

"You don't support X, how dare you!?"

One, this is free software, pay me if you want specific things.
Two, I'm the only developer of a project usually undertaken by a small team.
Three, yes it does you fucking invalid... Every fucking time someone claims it doesn't support some feature, it's something I've already written and validated. I swear to fucking God users can't find something themselves and instead of checking the Wiki or asking for help, they blindly assume they can't make mistakes and it must be my defect.

The project started as a series of individual prototypes. The client the wanted a beta app for a few selected clients, and someone had the great idea of just merging the prototypes into a single app. The attitude of the devs was always "whatever, this will be rebuilt for public release"

Over one year later, and after many different developers touched the project, the client wants it to go live, there was never a rebuild, and there won't be one until a few months after it goes live, and the project is buggier than it ever was.

A rebuild would have been quicker and safer than fixing the huge backlog of bugs, still the client won't accept a rebuild.

A few people already quit over this project and I think I will be the next one to hand in my resignation.

Mozilla, can you release your stupid UI updates once they're actually out of beta? The UI seems fine I guess, I don't care.

But why the fuck is the browser freezing up at least twice a day now? And why the fuck does it then restart with 1-2 fewer tabs but an additional tab that I had open half a week ago?

Maybe next time don't fire a quarter of your employees and then pay out the gain to your shitty CEO. If I wanted crashing browsers by shady companies there would be enough competition.

Without a doubt it has to be the internal company search engine/file finding tool @thewamz and I wrote.

The company has a wide UNC network with files scattered all over the place and they need a way to keep track of where the files get moved to (they can and do get moved). The original tool was written in Java/Tomcat and didn't use any frameworks or utilities beyond custom written ones, no orms, and the SQL was just raw strings. The program didn't take into account that files might be moved or deleted so it never removed anything from the database, it just kept adding files and never removing them.

It however never stores files itself, just links to files elsewhere on the UNC network.

It took six months to get it into what might be a stable beta or release candidate state. The user interface is good, very simple and intuitive, the whole thing was rewritten in python/django, there were issues with utf 8 (and mysql not fully supporting utf 8 in its own utf 8 mode), we added a regex search mode (which was sorely lacking), the search used to take up to fifteen minutes however we sped it up to less than a minute (worst case when a user simply puts "^$" as the regex search). It has a multi threaded design which does some checks to ensure it doesn't spawn too many threads and get stuck in constant Gil switching. Still some bugs to fix, like moving the processing of results returned by the server in a web worker so that the content widget doesn't lock up processing millions of search results and moving the back end to use asynchronous python might gain a performance boost. But on the whole I think the system is ready to replace the older system that all the users are frustrated with and constantly complain about.

However the annoying bit is... How to actually get the new system online, while I am responsible for the development of tools and their maintenance, I am not responsible for their initial deployment and that means I have no idea when (or even if) my new tool will even ever be released :/

I’ve been working on a update for config tool for a mod. The user asked me if I could add something like “note area” where you could write down anything... So I added it! It even appeared in one public beta build.
But then I’ve realized “wait, why the heck do I need it”. So in the next release it was gone.

To the reactjs-centered fucks who develop the popular web component viewing software called storybook: have you ever heard about semver?
89 alpha/beta/rc releases for a minor update 6.3 -> 6.4 with "100's of fixes and enhancements" "in preparation of the HUGE 7.0 release". Gee I wonder will it have 1000's of bugfixes? How bug-ridden is this software?
Every minor upgrade since 5.x is backwards-incompatible and requires a day of frustration finding out in how many more fucking NPM packages you split your codebase just because it's cool. I know move fast and break things, but some of us have other things to do than resolving node_modules incompatibilities you know. "No just hit 'npx sb upgrade' you say". I did, I really did! And the browser showed a blank screen of death with tons of cryptic React errors, it really did! Thank God you abstracted away all your dependencies in that sb command, now you can't even read the docs about what could have gone wrong with a specific sub-package. You have @storybook/html but the docs redirect to React pages, so good luck if you use something else

This is so sad... like.. the IDEA of storybook is great. But why did faith put the capacity to develop such a tool into the hands of people who think the world centers around React and JSX.. HTML should have been the default, and then you build on top of that for your fav framework, not the other way around

deciding at what point to release the beta of your software. you will always find thing you think need to be in there before launch but it never ends and have to bite the bullet and expect some complaints. I planned on launching 3 months ago :(

So Thursday our first beta client is supposed to go live. Tomorrow there is a team meeting to discuss the status. Team lead wasn't in at work last Thursday and Friday and gave me his work to finish, which I need to proceed with mine. I hardly made progress on it. So now I have to tell him about that tomorrow. And I'm dreading it so hard. More so because for some reason HR/support sits in on our meetings and will be on my ass again I'm not meeting deadlines. I did say last week it looked like it wouldn't be done in time but I was told it just needs to happen because the release date was already announced. So yeah the coming week is going to suck. And I'm on leave myself this coming Friday so I expect people to explode. I know I should just stop caring and get on with job searching but the whole injustice of being set up for failure by others and then being blamed really makes me mad.

So we have spent the last ~3 weeks creating workarounds for bugs that were found during testing against iOS 11 beta 1.
Today I had to go in and undo all the merges because as of beta 7 Apple have fixed the issues we were seeing.
Weeks of effort wasted that could have been spent upskilling or fixing build issues with an app that will have a release due in the coming weeks and we currently know little about.

Quietish team member sits quietly and creates the mother of all APIs, doesn't say much about it, doesn't document what he's done, falls out with the boss, leaves with 2 weeks to go before a beta release.

Already overworked dev/backend support team are plunged into manic bug fixing/business rule implementing/call standardising/chaos.

This is not how one devs.

Not one bit.

iOS public beta: people download it like a new gm release. « Why this shit are not working... » 🤯
Can’t wait two month more? Stupid users!

Trying to get some Angular 2 tutorials but every one I find is based on an older version of Angular; either Beta or early Release Candidate. Ah well, I think this ship has sailed.

Tooday i try to migrate a Drupal 7 to Drupal 8 ... I think that migrate module from drupal8 will work easily... But i remember on Drupal, noting work as expected on this Platform... I run the migration and suprise suprise content type field are off or empty and I don't have any data imported ...

Go to reports check the error message ... Try to get information on Internet hoo yes i remember no fucking documentation anywhere because Yolo i need to release 1626 modules that in beta or alpha after 5 years of development. And i dont give shit anymore.

Now i try use migrate_plus and tools to make my custom importation... Documentation not found or not finish ... Please omg please just shutup and work

Google play console is so fucking confusing, I'm trying to get my app to open beta testing stage, I've completed all the steps and done the full roll out, but the status of the app is still pending publication (3 days), wtf does "Pending publication" means do I need to publish the app for production in order for beta testing release to work, or I have to wait for google to approve the beta release for publish?
I'm lost

!rant
Just looked at ES6 compatibility table and every major browser's latest version supports it above 98%. Except Safari. But Safari 10 Beta is out for developers to test, so as soon as they release Safari 10, I will drop support for non-es6 compatible browsers in my own project. No more transpiling to ES5!

Downside of working with Angular2 today: a lot of online articles are written for depricated beta version or release candidates.

Upside: The official documentation is among the best I've seen

After Years, I've Returned! CEO and Founder of Team/Company Productions HH108!

New Announcements!
new Team Member otogi-cho 🦊🌺
Welcome to the Team!
Otogi-Cho 🦊🌺

Togi is our devloper in charge of Combat systems and polish work.

HH108 Hopes to Post a Working Beta Version of our new game "Filthy Frank'z" With a Post war theme of endless zombies chasing after you a Filthy Frank! (Hotdog) It's up to you and your allies to decide how to win!
We can only express how excited we are to launch this beta release!
In the meantime sit back and realize just how lame life is without this game...ik that's right, you can't!

Beta in current progress (no current release)
Be back soon with more info, screenshots, updates and more!

Release is out now!!!
Just seven month after first beta! I'm so fond of those customer change requests. Now I'm back in the predictable world...