Yesterday, in a meeting with project stakeholders and a dev was demoing his software when an un-handled exception occurred, causing the app to crash.

Dev: “Oh..that’s weird. Doesn’t do that on my machine. Better look at the log”
- Dev looks at the log and sees the exception was a divide by zero error.
Dev: “Ohhh…yea…the average price calculation, it’s a bug in the database.”
<I burst out laughing>
Me: “That’s funny.”
<Dev manager was not laughing>
DevMgr: “What’s funny about bugs in the database?”
Me: “Divide by zero exceptions are not an indication of a data error, it’s a bug in the code.”
Dev: “Uhh…how so? The price factor is zero, which comes from a table, so that’s a bug in the database”
Me: “Jim, will you have sales with a price factor of zero?”
StakeholderJim: “Yea, for add-on items that we’re not putting on sale. Hats, gloves, things like that.”
Dev: “Steve, did anyone tell you the factor could be zero?”
DBA-Steve: “Uh...no…just that the value couldn’t be null. You guys can put whatever you want.”
DevMgr: “So, how will you fix this bug?”
DBA-Steve: “Bug? …oh…um…I guess I could default the value to 1.”
Dev: “What if the user types in a zero? Can you switch it to a 1?”
Me: “Or you check the factor value before you try to divide. That will fix the exception and Steve won’t have to do anything.”
<awkward couple of seconds of silence>
DevMgr: “Lets wrap this up. Steve, go ahead and make the necessary database changes to make sure the factor is never zero.”
StakeholderJim: “That doesn’t sound right. Add-on items should never have a factor. A value of 1 could screw up the average.”
Dev: “Don’t worry, we’ll know the difference.”
<everyone seems happy and leaves the meeting>

I completely lost any sort of brain power to say anything after Dev said that. All the little voices kept saying were ‘WTF? WTF just happened? No really…W T F just happened!?’ over and over. I still have no idea on how to articulate to anyone with any sort of sense about what happened. Thanks DevRant for letting me rant.

Good Morning!, its time for practiseSafeHex's most incompetent co-worker!

Todays contestant is a very special one.

*sitcom audience: WHY?*

Glad you asked, you see if you were to look at his linkedin profile, you would see a job title unlike any you've seen before.

*sitcom audience oooooooohhhhhh*

were not talking software developer, engineer, tech lead, designer, CTO, CEO or anything like that, No No our new entrant "G" surpasses all of those with the title ..... "Software extraordinaire".

*sitcom audience laughs hysterically*

I KNOW!, wtf does that even mean! as a previous dev-ranter pointed out does this mean he IS quality code? I'd say he's more like a trash can ... where his code belongs

*ba dum tsssss*

Ok ok, lets get on with the show, heres some reasons why "G" is on the show:

One of G's tasks was to build an analytics gathering library for iOS, similar to google analytics where you track pages and events (we couldn't use google's). G was SO good at this job he implemented 2 features we didn't even ask for:

- If the library was unable to load its config file (for any reason) it would throw an uncatchable system integrity error, crashing the app.
- If anything was passed into any of the functions that wasn't expected (null, empty array etc.) it would crash the app as it was "more efficient" to not do any sanity checks inside the library.

This caused a lot of issues as some of the data needed to come from the clients server. The day we launched the app, within the first 3 hours we had over 40k crash logs and a VERY angry client.

Now, what makes this story important is not the bugs themselves, come on how many times have we all done something stupid? No the issue here was G defended all of this as the right thing to do!

.. and no he wasn't stoned or drunk!

G claimed if he couldn't get the right settings / params he wouldn't be able to track the event and then our CEO wouldn't have our usage data. To which I replied:

"So your solution was to not give the client an app instead? ... which also doesn't give the CEO his data".

He got very angry and asked me "what would you do then?". I offered a solution something like why not have a default tag for "error" or "unknown" where if theres an issue, we send up whatever we have, plus the file name and store it somewhere else. I was told I was being ridiculous as it wasn't built to track anything like that and that would never work ... his solution? ... pull the library out of the app and forget it.

... once again giving everyone no data.

G later moved onto another cross-platform style project. Backend team were particularly unhappy as they got no spec of what needed to be done. All they knew was it was a single endpoint dealing with very complex model. There was no Java classes, super classes, abstract classes or even interfaces, just this huge chunk of mocked data. So myself and the lead sat down with him, and asked where the interfaces for the backend where, or designs / architecture for them etc.

His response, to this day frightens me ... not makes me angry, not bewilders me ... scares the living shit out of me that people like this exist in the world and have successful careers.

G: "hhhmmm, I know how to build an interface, but i've never understood them ... Like lets say I have an interface, what now? how does that help me in any way? I can't physically use it, does it not just use up time building it for no reason?"

us: "... ... how are the backend team suppose to understand the model, its types, integrate it into the other systems?"

G: "Can I not just tell them and they can write it down?"

**
I'll just pause here for a moment, as you'll likely need to read that again out of sheer disbelief
**

I've never seen someone die inside the way the lead did. He started a syllable and his face just dropped, eyes glazed over and he instantly lost all the will to live. He replied:

" wel ............... it doesn't matter ... its not important ... I have to go, good luck with the project"

*killed the screen share and left the room*

now I know you are all dying in suspense to know what happened to that project, I can drop the shocking bombshell that it was in fact cancelled. Thankfully only ~350 man hours were spent on it

... yep, not a typo.

G's crowning achievement however will go down in history. VERY long story short, backend got deployed to the server and EVERYTHING broke. Lead investigated, found mistakes and config issues on every second line, load balancer wasn't even starting up. When asked had this been tested before it was deployed:

G: "Yeah I tested it on my machine, it worked fine"

lead: "... and on the server?"

G: "no, my machine will do the same thing"

lead: "do you have a load balancer and multiple VM's?"

G: "no, but Java is Java"

... and with that its time to end todays episode. Will G be our most incompetent? ... maybe.

Tune in later for more practiceSafeHex's most incompetent co-worker!!!

Hey everyone - I just wanted to update our Android users on the push notification crash that has been occurring.

The good news is the issue should be fixed in the update I just pushed out (should be available in the Google Play Store within a few hours). We apologize for the crashes and thank everyone for their patience.

I'm still looking in to what actually happened here. Our GCM library hasn't been updated in a while and all of a sudden a specific case started failing. I'll continue to look in to how that seemingly happened with no changes in the app. Some other users of the library started experiencing the same issue.

PM: Bro send me latest version of the app
Me: But I"m not finished with x feature and it will crash the app in its current situation
PM: No problem bro just want to test

*5 minutes later*
PM: Bro app is crashing when I do x
Inner Me: YOU PEACE OF SHIT I TOLD YOU IT WILL CRASH!
Actual Me: throw a ticket I'll handle it later.

Try to click quickly on this button multiple times and the play store will crash. If you implement this sort button on your own app this will crash too. #google_guidelines 😡

My morning (RO = remote office):

Me: Your xxx implementation is very strange.
RO: Yes we are following a new example from experts in this field. See this link.

Me: Paragraph 1, use xxx class in these situations. Were not doing that.
RO: Yes we had problems with that, we decided to skip that.

Me: Paragraph 2, always use xxx when accessing data. Were not doing that.
RO: Yes that create many bugs, we skipped that.

Me: This section on debugging says to enable this flag while in development to allow the IDE to alert you to issues.
RO: Yes this causes the app to crash constantly. So we took it out.
Me: ... because its finding issues ... and telling you where the problem is, with an error message.

... your not following the experts at all.

RO: We are!, please read the link we provided.

... this will be discussed on my exit interview

devRant Android users - if you are a user who can consistently reproduce a devRant app crash and wouldn't mind helping me please let me know. You can comment here or email me at david@devrant.io

I'm trying to get rid of a couple of remaining crashes that seem to be happening in the Android app but we've never really been able to reproduce any of them. Thanks!

FOUR DAYS

Tomorrow will be the FOURTH FUCKING DAY spent trying to get this piece of shit iOS simulator to not crash the app.

I’VE TRIED EVERYTHING.

FUCK APPLE. FUCK XCODE. FUCK IOS😠😤😠😤😠😤😠😤😠😤

Steve Jobs was a twat, and the IPhone X garbage piece of technology

TL;DR: Fuck you Apple.

10:30 PM, parent needs iPhone update to update Messenger. How hard can this be?
Need to update iPhone from 9.x to latest, which is so outdated it still required iTunes. Fk.

Boot iTunes on Windows 10 pc that is at least 10 years old.
Completely unresponsive
Crash in task manager
Launch and is completely unresponsive. (Also starts playing unrequested music.. Oh joy..)
Fuck this, go to apple.com to download iTunes exe
Gives me some Microsoft store link. Fuck that shit, just give me the executable
Google “iTunes download”. click around on shitty Apple website. Success.
Control panel. Uninstall iTunes. (Takes forever, but it works)
Restart required (of fucking course).
2 eternities later. Run iTunes exe. Restart required. Fk.
Only 1 eternity later. Run iTunes, connect iPhone.
Actually detects the device. (holy shit, a miracle)
Starts syncing an empty library to the phone. Ya, fuck that.
Google. Disable option. Connect phone. Find option to update.
Update started. Going nowhere fast. Time for a walk at 1:00 AM punching the air.
Come back. Generic error message: Update failed (-1). Phone is stuck installing update. (O shit)
1x hard reset
2x hard reset
Google. Find Apple forum with exact question. Absolutely useless replies. (I expected no less)
Google recovery mode. Get into recovery mode.
Receive message: “You can update, but if it fails, you will have to reset to factory settings”. Fuck it, here we go.
Update runs (faster this time). Fails again. Same bullshit error message. (Goddammit, fuck. This might actually be bad.)
Disconnect phone.
… It boots latest iOS version. (holy shit, there is a god)
Immediately kill iTunes. Fuck that shit.
Parents share Apple account
Sign in, 2FA required.
Fat finger the code.
Restart “welcome” process.
Will not send code. What. The. Fuck.
Requests access code on other parent’s iPhone.
No code present. What???
Try restarting welcome process again. No dice. (Of course)
Set code on other parent’s iPhone.
Get message “Code is easy to guess”. Ya. IDGAF
Use code on newly updated iPhone. Some success.
Requires reset of password.
Password cannot be the same as old password (Goddammit)
Change password.
Welcome process done.
Sign in again on same phone after welcome process done in settings. (Nice.)
Sign in again on other phone with updated password
Update Messenger.
Update hangs. Needs more space.
Delete shit.
Update frozen in App Store (Really??)
Restart iPhone.
Update Messenger.
Update complete past 2. Well that was easy.

Apple, fuck you.
Some call Android unintuitive, but I look at the settings app on iPhone and realize you aren’t any better.
This company hasn’t been innovative since 2007. Over 1000 USD for a phone? Are you fucking kidding me?
Updating an iPhone from iOS 9.x is probably uncommon anymore. But this is a fucking joke. Fix your shit.
Shit like this is why I’ll never again own an Apple product. I have HAD IT with the joke of a business.

Thanks for reading.

> Customer logs Jira ticket claiming app is not working
< I restart the app, investigate and explain tht their server has issues
ø Client closes the ticket as Resolved
-- a couple of days pass by ---

> Customer logs Jira ticket claiming app is not working
< I restart the app, investigate and explain tht their server has issues
ø Client closes the ticket as Resolved
-- a couple of days pass by ---

> Customer logs Jira ticket claiming app is not working
< I restart the app, investigate and explain tht their server has issues
ø Client closes the ticket as Resolved
-- a couple of days pass by ---
<...>

< I log a JIRA ticket explaining what and how is wrong with the server with suggestions how to fix the problem so the app will not crash any longer (client own the server, has his own sysadmins -- I don't even had permissions to open syslog.. had to hack dmesg on their PROD server to pin-point the issue)
> no reaction from customer for weeks. I ping the ticket

× app crashes again

> no reaction from customer for weeks. I ping the ticket
> customer leaves a comment that their sysadmins are looking at it trying to figure out what might be wrong (ignoring what I wrote in ticket's description??? srsly?)

× app crashes again
< I post detail investigation details: snips from logs, screenshots, everything with crystal clear explanations.

> no reaction for weeks
......

well that's fun..

So apparently due to an extremely talkative x input driver and an error in a certain app, I've been running an emergent keylogger on my computer for half a year. On every keypress event, the driver would call the app, the app would segfault, the driver would log the incident including the event to /var/log and then crash, and the app would restart the worker. I noticed this when I started wondering why /var/log is over 100GB in size.

!rant & story_time
This happend to the startup I was working for at ~2011. I was a junior Android dev, working on a very popular app.
During experiments for a new feature, I discovered that the system AlarmManager has a serious bug - you can set a repeating alarm with interval=0ms. If your app takes more then 1 ms to handle the Intent, then the AlarmManager will start to fill up the intent Queue, with unexpected results to the OS. causing it to slow down, and reboot when it ran out of Ram. Why? my guess was that because the AlarmManager was part of the OS, then any issues caused by it caused the system process to ran out of ram, crashing it, and the whole system with it. the real kicker was that even after a reboot, the AlarmManager still had Intents queued, causing the device to bootloop for a while, untill the queue was cleared. My boss decided to report the problem to google, as this was an issue in the OS. I built an example app, that caused the crash 10-30 seconds after starting, and submitted to Google. Google responded later that day with "not an issue, no one will ever do this".
Well... At this point I decided to review the autoupdate feature in our app, to make sure this will not happen to us. We just released a new feature where a user can set an update schedule option in the app settings - where you could setup a daily, weekly, or hourly update for the app. after reviewing it, It looked good, and the issue was not triggered in the manual QA I did. So, it was all good. And we released an updated version to the store.
After we did an update-install, we discoverd that, there was a provlem reading the previous version SharedPrefs value for the update schdule settings, and the value defaulted to 0...
the result was, our app caused all our users to go into a bootloop, and because the alarm was reset when the devices booted up, the bootloop could only be solved in a factory reset, or removing our app, before the device rebooted, and then waiting a few reboot cycles.
We lost 50 places in the market, and it took us 6 months to get back to where we were.

It was not my fault, but it sucked big time!

I broke off a long term relationship recently and today I deleted the text conversation with my ex. With 13000 messages being deleted at once I managed to crash my texting app for a whole 10 minutes.

Fuck Apple and its review system

So, this started in december. We wanted to publsih an app, after years of development.

Submit to review, and passes on the first try. Well, what do you know. We are on manual release option, so we can release together with the android counterpart. Well yes, but someone notices that the app name is not what was aggreed (App Name instead of AppName). Okay, should be easy, submit the same app, just the name changed. If it passed once, it will pass again, right? HAH

Rejected, because the description, why we use the device’s camera is too general. Well... its the purpose of the app... but whatever, i read the guidelines, okay, its actually documented with exapmles. BUT THEN WHY THE FUCK COULDNT YOU SAY THAT ON THE FIRST UPLOAD?

Whatever, fix it, new version, accepted, ready to release just in time.

It doesindeed roll out,but of course, we notice that the app has a giant issue, but only on specific phones. None of our test phones had this problem, but those who have, essentially cannot use our program. Nasty as it is, the fix is really easy, done in 5 minutes. Upload it asap, literally nothing changed from user point of view, except now it doesnt crash on said devices. Meanwhile 1 star reviews are arriving from these users - of course with all the right. Apple should allow this patch quickly, right? HAH

THE REAL BULLSHIT COMES NOW

With only config files changed, the same binary uploaded we get rejected? What now? Lets read it. “Metadata rejected, no need to upload new binary”.... oh fine only the store page is wrong? Easy. Read the message, what went wrong. “Referencing third party content is nit permitted on the app store” meaning that no android test device should be shown. Fine, your rules. They even send a picutre of the offending element. BUT ITS NOT EVEN ON THE STORE. THATS A SCREENSHOT OF THE APP. HOW IS THAT METADATA? I ask about this, and i get a reply, from either a bot, or a person who cant speak or read english, and only pasted a sample answer, repeating the previous message. WTF. Fine, i guess you are dumb, but since they stop replying to our queries, do the only sensible thing, re-record the offending tutorial video that actually contained an android device. This is about 2 weeks, after the first try to apply a simple patch to a broken app. And still, how did it pass the review 2 times?

Whatever, reupload again, play the waiting game for a week, when the promised average wait time is 2 days, they hit us with a message, that they want to know what patent we use in our apps core functionality. WTF WHY NOW? It didnt bother you for a month, let it release ti production and now you delay a simple patch for this? We send them what they know. Aaaaand they reply: sorry we need more time to review your app. FUUUUUUCKKK YOUUU. You are reviewing a PATCH with close to zero functional change!!! Then, this shit goes on, every week we ask about an ETA, always asking for patience... at the end it took another 3 weeks... so december 15 to jan 21 in total...

FOR. A. SINGLE. FUCKING. PATCH

Bottom line is what is infurating, apple cares that there is an android device in the tutorial video, but they dont care that a significant percentage of our users simply cannot use the app.

Im done

My project at work (an electron/angular desktop app) has an exceedingly rare bug that causes it to crash-to-desktop while loading. Nothing about the bug makes sense, and there's no way to catch or detect it until the next run, and it happens 100% of the time for affected users.

There have been six confirmed cases so far (out of 500k+ users), and nothing linking them together. None of the fixes discovered by those users have worked for other affected users.

The worst part?
I was the first of those cases. I inadvertently fixed it for myself and haven't been able to reproduce it since.

I'm stumped!

```We discovered that your app contains hidden features. Attempting to hide features, functionality or content in your app is considered egregious behavior and can lead to removal from the Apple Developer Program.```
- Apple App Store Publishing Team

.

ARE U FU KINV KIDDING ME

THAT IS THE COMPLETE REASON WHY YOU REJECTED MY APP?

THE SAME GODDAMN BUILD THAT WAS SUBMITTED ON GOOGLE PLAY FOR ANDROID GOT APPROVED IN 10 MINUTES

IS THE SAME BUILD VERSION THAT GOT REJECTED 3 DAYS AFTER REVIEW ON THE APP STORE

BECAUSE "THEY THINK" I HAVE HIDDEN FEATURES LOL WHAT ARE FU🤡🤡KING INSANE🤡 YO😂😂🤡🤡

THIS REJECTION REASON IS LIKE A SHITTY USER REVIEW

"omg baby girl this app is best" *1 star"

OR

"I have a crash pls fix its not work this app cz crashs n not fixes fck u developers fix it these prblms !!!!🍆🍆🍆👅👅👅💦💦💦💨🌬🌬🌬" *1 star*

AND GET THIS RN !!!!

RN !!!!!!

THEY EVEN *THREAT ME* TO BAN MY APPLE DEVELOPER PROGRAM ACCOUNT WHICH I. P A I D. F O R. $ 100 USD

BECAUSE MY APP HaS 'HIDDEN FEATURES'

THERE ARE NOOO9OO FI KING HIDDEN FEATURES U MTHHHFRRFKERSS I WILL CUMBLAST ALL OF UR APPLE HOLES INTO UR ASSHOLES AND GIVE BIRTH TO THE MAGGOTS🤡GROWING FROM WITHIN🤡UR FKIG ASSHOLE CZ ALL OF YALL R FKIN ASSHOLES🤡ANYWAY🤡THEN MY FKIG HOT CUM🤡WILL EXPLODE💦OUT OF YOUR🤡ASS AND U WILL BE CLOWNS FOREBER🤡I WORKED WAY TOO HARD TO DESERVE AN UNNECESSARY REJECTION THAT HAS A VAGUE REASON OF WHY IT WAS REJSCTED🤡🤡🤡

juuuuuuu

🤡hehe

When you develop and test your (Android) app on lower end devices, thinking that if it works on low end devices, it will work on higher end devices too.
And you get crash reports from the higher end (huh! Flagship grade) devices only.

Python. Ok, so it's a really cool language, as a scripting language it's awesome, quick to write.

When it's been used to make full fledged oop programs that you suddenly have to maintain things like duck typing become problematic. Looking at an object fuck knows what methods are available. Worse still when some bastard that thinks he's being clever doesn't bother declaring any object attributes and instead overrides the __set_attr method to dynamically add them as they are used there is no hope for the poor sod that has to maintain it later.

I've also now worked out I'm at least the 3rd person having been given the task of maintaining it, i spent a day changing CLI options wondering why they didn't do anything but occasionally crash the app. I've now found a few thousand lines deep that someone had hard-coded these values because they couldn't work out where to get the CLI args from!

I've gained a new appreciation for nominative, strictly typed languages.

So one rant reminded me of a situation I whent through like 10 years ago...
I'm not a dev but I do small programs from time to time...
One time I was hired to pass a phone book list from paper to a ms Access 97 database...
On my old laptop I could only add 3 to 5 records cause MS access doesn't clean after itself and would crash...

So I made an app (in vb6) , to easily make records, was fast, light and well tabbed.
But now I needed a form to edit the last record when I made a mistake...
Then I wanted a form to check all the records I made.
Well that gave me an idea and presented the software to the client... A cheesy price was agreed for my first freelance sell...
After a month making it perfect and knowing the problems the client would had I made a admin form to merge all the databases and check for each record if it would exist.... I knew the client would have problems to merge hundreds of databases....
When it was done... The client told me he didn't need the software anymore.... So I gave it to a friend to use as an client dabatase software... It was perfect for him.
One month later the client called me because he couldn't merge the databases...
I told him I was already working in a company. That my software was ready to solve his problem, but I got mad and deleted everything...
He had to pay almost 20 times more for a software company to make the same software but worst... Mine would merge and check all the databases in a folder... Their's had to pick one by one and didn't check for duplicates... So he had to pay even more for another program to delete duplicates...

That's why I didn't follow programming as a freelance... Lots of regrets today...
Could be working at home, instead had a burn out this week cause of overwork...

Sorry for the long rant.

Freelance project I was working on was deployed. Without my knowledge. At 11pm. Their in-house "tech guy" thought that the preview build i gave them was good enough for deployment. Massive bug, broke their api endpoints.
Got a call at 2 in the morning,asking for a fix. I told them how it was their fault and the App they deployed had TESTING written right on the main screen.
They promised additional payment to get me to fix it asap.
Went through the commit history (thank goodness their tech guy knew git, fuck him for committing on production though) and the crash reports.
Removed three lines. All became right with the world again. 😎

App: *Crashes*
Every Android user in the universe: I MUST SCREENSHOT IT AND SEND TO DEVELOPER, SYSTEM CRASH DIALOG WILL DEFINITELY HELP TO FIX THAT

Thanks to @sain2424, we found a really weird bug in devRantron.

One of the user that commented on or upvoted his rant has deleted that account. So when the notification component was trying to fetch the user's avatar to show the notification, it was failling and causing the app to crash.

@Cyanite the bugs you reported is fixed as well. Please update 🙃 🙃

Me: "Oh, I see the problem.... Ctrl ^C"

App: "Received interrupt signal. Ignoring."

Me: "That's not how this works. I tell you to quit, and you quit. M'kay pumpkin? ... Ctrl ^C Ctrl ^C Ctrl ^C ....."

App: "Received interrupt signal. Ignoring."
App: "Received interrupt signal. Ignoring."
App: "Received interrupt signal. Ignoring."

Me: "Stubborn piece of crap."

App: "Crash."

The story of the shittiest, FUCKING WORST day of work.

TLDR: shitty day at work, car crash to end the day.

So, let tell you about what could possibly be the worst day I had since I started working.

This morning, my alarm didn't work, woke up 30 minutes before an appointment I had with a client.

Arrived late at the client, as I start deploying. They don't have any way to transfer the deployment package to the secured server. Lost 45 minutes there.

Deployment goes pretty well. My client asks me to stay while they load some data into the app. Everything's pretty easy to work out. Just need to input 3 CSV with the correct format (which the client defined since the beginning).
I end up watching an Excel Macro called "Brigitte" (I'm not fucking kinding, could'nt have thought of that) work for 4 hours straight. Files are badly formatted and don't work.

Troubbleshooting thoses files with a fucking loader that does not tell you anything about why it failed (our fault on that one)

I leave the client at 7:30pm, going back at work, leave at 9pm.

At this point, I just want to buy some food, go home and watch series.

But NO, A FUCKING MORRON OF A BUS DRIVER had to switch lanes as I was overtaking him. Getting me crushed between the bus and the concrete blocks.

Cops were fucking dickheads, being very mean even tho I was still shaking from the adrenaline.

In conclusion, the day could have been worst. The devs at the clients are pretty cool guys and we actually had some fun troubleshooting. At work, there was still one of my colleagues who cheered me up telling me about his day.
And when I think of it, I could have got really hurt (or even worst) in the crash.

A bad day is a bad day, tomorrow morning I'm still going to get up and go to a job I love, with people I love working with.

Very big rant (sorry about that if someone's still reading)

Someone help me, this app keeps crashing on me. I need someone to help me interpret this crash log.

😂😂😂😂😂😂😂

Before becoming a developer, I used to work as a sales rep at this company that spent a good amount of time building what they believed to be an innovative state-of-the-art “code generator”. It was basically a scaffolding tool for generating software.

They were using it to auto generate customized iOS and Android native mobile app templates, along with a web backed.

The problem was that the generated code was shit, and the developers on the team basically spent more time fixing bugs than if they had built everything from scratch. But their passion for the product meant they just kept using it.

For some reason they never fixed issues in the original templates, so basically all the bugs that were found, kept showing up with each new app!

I have never seen apps like this that essentially had more bugs than features. Opening more than 10 app screen meant the app would freeze and crash. Sign up forms were actually dummy forms. The list goes on...

All the apps had the same shitty UI. For example, Product pages had a product image area that was like 5% of the screen view!

Last but not least, apps had a backend IP address hardcoded pointing to a server with an IP address that was temporary. So one day they had to restart the server and suddenly all customer apps stopped working and required a software update to work!

It was amazing seeing how a team of 3 developers trying to fix messy autogenerated code, couldn’t accomplish what was essentially a website on an app that I managed to build in my free time.

That’s how I knew it was time to quit my job and code full time.

10 PM (after a very busy working day), CTO calls me and tells me: "We decided to hand in the new version to [random client] one week earlier, so they can test it."
Me: "I don't think is a good idea, the app is still unstable, we started working in it yesterday, it *will* crash"
CTO: "Don't you worry, at least they know we are working on it"
20 minutes later
CTO: "WTF why did you make my app crash?! I can't send this to a client!"

Told you. That is why that code is on develop and not on master.

Why you should always backup.

Nearly a year ago I developed a whole project (iOS, tvOS, watchOS), but I never backed it up because I had a recent machine and thought the chance that something happens to the disk is so small I didn’t backup. But then my mac didn’t start correctly. So I needed to reset it. Lose the project, some other files but not much else. Then I recoded the project and backed it up on multiple places. But a little later, I was writing another app, again didn’t copy again... This time I deleted the wrong folder and deleted the trash, was gone too. So from then I learned to copy everything I coded. All projects I work on, I keep a copy of on an external disk, GitHub and Bitbucket. Assuming they wont crash all at the same time 😉.

So I recommend everyone to backup all your code. Even if it’s only 500 lines. Losing it is hard...

In 2010, it was my first client project. Our architect was not from iOS background, we had editable pdfs in our app. Those were pretty rich pdfs with inline HD images. iPads that time were not too fast and couldn't handle big gb pdf loaded into memory. App would crash randomly running out of memory. We fixed it by paginating pdf, it wasn't out of the world but considering it was my first mobile project and no one to guide, I thought it was pretty cool what we did there

Sorry, I crashed the app!

This “Auto save” feature in the latest app version is buggy..
-> new rant
-> prefilled with previous rant..

Anyway, here my actual rant begins.

Apple, go fuck yourself, seriously.. put your trillion dollars way up your arse...

Moved to Ireland, want to switch country..
“If you want to switch countries, cancel your Apple Music subscription first”..
so be it. Cancelled it..
“Your subscription will be cancelled in 28 days”.

FUCK YOU, YOU COCK SUCKING BASTARDS!!
I NEED TO SWITCH THE STORE TO BE ABLE TO DOWNLOAD BANKING APPS AND STUFF LIKE THAT..

But ok, I’m screwed in this regard..

Suddenly iMessage stopped working. This is kind of a big deal because I have unlimited data but only unlimited sms to Irish numbers and I need to communicate with people in Switzerland and Germany..
Internet works so I try to turn iMessage off and in again. But that doesn’t work.. i can only reactivate iMessage via WiFi.

So I go back to the hotel, reactivate iMessage..
“Verifying imessage” >> google..
Leads me to an Apple forum: “the verification of iMessage can take up to 24h”.

Are you fucking kidding me? I’m in a new country and rely on this overpriced shit..

Fun but sad fact, I have a second phone with me. IPhone 4 with iOS 7 and that thing WORKS!!

If this is where the future is going we’re all gonna die very soon.. plains crash, power plants explode but hey, at least they have data about it and it looks shiny. That’s all that matters..

Another reason to switch to android..

MacOs fucked me up so I already switched to windows + Linux. Next one will be getting rid of iOS, they don’t build small phones anymore anyway..

Me: Runs app

*Crash with error*

Me: Changes one thing, then runs again

*Crash with different error in another part of code*

Me: Fixes that error and runs again

*A FATAL ERROR HAS BEEN DETECTED BY THE JAVA RUNTIME ENVIRONMENT*

Me: Runs app again, "Maybe it was just a hiccup."

*A FATAL ERROR HAS BEEN DETECTED BY THE JAVA RUNTIME ENVIRONMENT*

Me: Chucks laptop out window. Goes to gaming PC to play Dark Souls 3, because it's less angering than this.

"Stop throwing errors in your library! They cause my app to crash"

Who amongst us hasn't hear of the popular maxim: "Fail late even after you know something is wrong, and then make sure the failure cascades over the whole app in mysterious ways"

I hate silicon valley.

They enable so much of the state's and federal government's bullshit, the corporations and the banks subversion and destruction of society.

It's time to pop their fucking tech bubble.

From here on out, any time you hear or read the words 'startup', be sure to comment with "you mean speculative marketing investments?"

Because most tech runs on shit-tier semi-polished iterations of glorified CRUD anyway, thats all most of it is. And it 100% relies on grabbing network share through massive advertising and presence campaigns. A lot of vc money is being flushed straight down the toilet and this is a point to emphasize. Crash the fucking tech sector. Do it.

It'll have a knock on effect to the advertising space, which will put the hurt on google's bottom line when they and their ilk are already under pressure for all the poisonous, monopolist shit they pull like helping china build their surveillance tech.

Extra points for emphasizing "pot-fueled ideas sketched out on napkins while sitting in fucking chipotle, in unwashed sweater vests, originated by guys who are fresh out of college and never ran a business in their life. 90% of them fail in the first year. VCs and investor are losing their shirts." etc.

The entire dishonest fucking trade relies on other people's money, being bought out in either techno land-grabs or turf-protection e.x. atlassian acquiring trello, a **glorified todo app**.

Thats the business model. Hell go build your own and make a buck.

Build your own. Build something better and most of all... *fuck silicon valley*.

Let it burn, let burn, let it burn.

Spent 2 hours last night (leaving an hour late) with the IT guy hunting down a problem that affected at least 12 other teams. It didn't crash the app, but did prevent MANY scripts from working, and thus nothing could be committed.
I found the culprit, made a solution, and posted in the email chain my solution. (it required a code review and a client-side update)
Someone responded asking for another dev to confirm my report. That dev did and them dumbed it down for those who can't understand programming talk. Then EVERY EMAIL after that thanked that dev for "fixing the root problem" and "solving their scripts".
And just now, the PO for the bug was replaced to that dev's team. (previously was my team's PO)

Amazing! My joke functionality worked and the server delivered it's content successfully to the client. The joke: malloc is wrapped to give that message and retry IMMEDIATELY. Expectation is that the computer that was already in panic mode gets even fucked up more because it's out of memory. My malloc is literally while((ptr=malloc()} == NULL) { show_warning()
;malloc();}. Imagine if it didn't give that warning, I would've never known that a malloc failed. Who checks their freaking malloc result? You should, but i do not see much people doing it.

The previous crash on screen is what happens if you're doing a get instead of a post. I just declare my server app indestructible btw. Ffs!

Worst code I ever had to touch: a React application, createClass era, before redux was a thing, that had everything in one fucking component.

Every fucking thing.

This was a simple video chat application, but still. The component's code included:

- Views (contact list and video call screen) and logic to switch between them;
- All application state;
- API calls;
- Websocket message handling;
- WebRTC logic (getUserMedia and p2p streaming).

This app was built by one person in one month for a demo. That person left the company after the demo and I had to maintain that mess without zero React knowledge (I was doing angular at that time). On his last day he gave me a crash course and an overview of how the app worked.

Around that time I attended a few meetups and a conference with talks about React. That, my curiosity and ability to learn by refactoring helped me a lot when I had to add new features and fix bugs in that app.

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.

So, I work in a game development studio, right?
We're trying to launch the title on as many platforms as reasonable, because as a social VR app we're kinda rowing upstream.
So far, Steam and Oculus have been fairly reasonable, if oddly broken and inconsistent.
Enter store 3.
Basically no in-game transaction support (our asking prompted them to *start* developing it. No, it's not very complete). No patch-update system (You want an update? Gotta download the whole fsckin' thing!). No beta-testing functionality for most of their stuff ("Just write the code like the example, it will work, trust us!"). No tools besides the buggy SDK (Wanna upload that new build? Say hello to this page in your web browser!).
So, in other words: Fun.

We've been trying to get actively launched for two months now. Keep in mind that the build has been up on Steam and Oculus for over a year and half a year (respectively), so the actual binary functionality is, presumably fine.

The best feedback we get back tends to be "Well, when we click the Launch button it crashes, so fail."
Meanwhile we're going back and forth, dealing with other-side-of-the-world timezone lag, trying to figure out what is so different from their machines as ours. Eventually we get them to start sending logs (and no, Windows Event logs are not sufficient for GAMES, where did you even get that idea????) except the logs indicate that the program is getting killed so terribly that the engine's built-in crash handler can't even kick in to generate memory dumps or even know it died.

All this boils down to today, where I get a screenshot of their latest attempt.

I just can't even right now.

I have a 4S I leave lying around and most apps are dogs on it or crash.

Not DevRant app, though. Pretty solid. Impressive job.

Android flow I’ve found(fixed in android 8, working on 7.1.1):
To make app uninstallable by the normal user make the app device administrator, add “android.permission.SYSTEM_ALERT_WINDOW” to the manifest and make sure it’s not granted by the user.
Now when you try to uninstall the app, it tells you to disable it from device administrators but the device administrator disable dialog is System Window handled by the app itself and if the app has this permission but not granted, settings will crash with SecurityException leaving the app untouched.

Feeling better after knowing other apps do crash as well, not only the app I'm developing

I need a programmer girlfriend who will actually understand the pain of a crash in live app...

Managers don't understand that there will ALWAYS be bugs shipped to production, no matter how hard you try to prevent or test against them.

Devs: lol

inb4 any comments really, i've seen facebook, instagram, and all the 'big players' crash and have bugs multiple times before, so don't go around swinging your dick like your company's software has no known bugs (don't even get me started on the devrant mobile app) I'm just saying bugs are a fact of software

PO1: Hey, PO2 just told me that he experiences a lot of crashes in our iOS app!

Me: Whoa! The app hasn’t had any crashes since ages. The testers haven’t reported crashes either. (Me in panic mode). I will ask PO2 about some details about the crashes.

Me to PO2: So, can you please describe me when the crash happens?

PO2: (long story about error messages and UI quirks and how he force quits the app to make them disappear)

Me: OK thanks for that info. Those are definitely valid problems that we have not encountered yet. But none of them are crashes. So are there any other problems that cause crashes?

PO2: Yes and no. (Long story and more problems)

Me: ok we need to investigate that. But are there crashes?

PO2: (Something that doesn’t answer the question)

Me: I need to ask explicitly again: Are there actual crashes where the app closes itself automatically?

PO2: No, that has never happened.

We code hard in these cubicles

My style’s nerd-chic, I’m a programmin’ freak

We code hard in these cubicles

Only two hours to your deadline?

Don’t sweat my technique.

Sippin’ morning coffee with that JAVA swirl.

Born to code; my first words were “Hello World”

Since 95, been JAVA codin’ stayin’ proud

Started on floppy disks, now we take it to the cloud.

On my desktop, JAVA’s what’s bobbin’ and weavin’

We got another winning app before I get to OddEven.

Blazin’ code like a forest fire, climbin’ a tree

Setting standards like I Triple E….
Boot it on up, I use the force like Luke,

Got so much love for my homeboy Duke.

GNU Public Licensed, it’s open source,

Stop by my desk when you need a crash course

Written once and my script runs anywhere,

Straight thuggin’, mean muggin’ in my Aeron chair.

All the best lines of code, you know I wrote ‘em

I’ll run you out of town on your dial-up modem.

Cause…
We code hard in these cubicles

Me and my crew code hyphy hardcore

We code hard in these cubicles

It’s been more than 10 years since I’ve seen the 404.

Inheriting a project can make me go beeee-serk

Ain’t got four hours to transfer their Framework.

The cleaners killed the lights, Man, that ain’t nice,

Gonna knock this program out, just like Kimbo Slice

I program all night, just like a champ,

Look alive under this IKEA lamp.

I code HARDER in the midnight hour,

E7 on the vending machine fuels my power.

Ps3 to Smartphones, our code use never ends,

JAVA’s there when I beat you in “Words with Friends”.

My developing skills are so fresh please discuss,

You better step your game up on that C++.

We know better than to use Dot N-E-T,

Even Dan Brown can’t code as hard as me.

You know JAVA’s gettin’ bigger, that’s a promise not a threat,

Let me code it on your brain

We code hard in these cubicles,

it’s the core component…of what we implement.

We code hard in these cubicles,
Straight to your JAVA Runtime Environment.

We code hard in these cubicles,
Keep the syntax light and the algorithm tight.

We code hard in these cubicles,

Gotta use JAVA if it’s gonna run right.

We code hard in these cubicles

JAVA keeps adapting, you know it’s built to last.

We code hard in these cubicles,

Robust and secure, so our swag’s on blast

CODE HARD

Worked with a team of interns learning Swift. They had a really tight deadline, so they decided if they were not sure what the app should do if a nil showed up, they would just force unwrap and let it crash.

TIL you can crash a Tomcat request processing if the app reads request bodies using a reader() and you feed it a json body with an innocent nbsp :) the whole request processing just goes *pooooft*

reminds me of an ios bug which could brick the phone if it received an sms with weird chars.

These lynch-pin-bugs where a single byte/char in the right place at the right time can tear things down, are so subtle and fascinate me for some reason :)

My JS app can crash IE11. Totally reproducable.

Had a fun debugging session to find out how this is triggered. Happens inside a deeply recursive call in a library I'm using which redraws the DOM.

Found a hacky workaround to avoid that as I see no real solution. It's not like I'm responsible for fixing IE. These are the days where I'm happy I'm mainly a backend dev...

Old story, happened some way back. I worked part-time for a small web development company that did between other things something called SharePoint development, basically .net webforms with shit glitter on top of it.

The most weird part of it, was the fact that we were working on vms that hosted the app, it was our dev, test and staging environment, as well as were we showed the client the polished turd.

Did I say that it was on a vm? Well it was on a remote vm, that each of use had access to it, through our domain accounts, and they couldn't configure the windows server to accept more than two or three users at once to be connected.

That was our test enviroment and dev enviroment, sooo showing the app to the client meant for the rest of us to not write any code because it might crash or get stuck.

The app was accessible and discoverable by url and through google search from outside, I dont think that should have been allowed.

The most disastrous part was that we had NO source versioning whatsoever, just plain old copy and paste in different folders.
Deploying to client meant remoting to the clients host or whatever it was, and manually copying the source files

If someone wanted to debug the application you had to shout, and you also could hear it, in the office: "I'm debugging!" or "I'm deploying!". Because we were on the same machine, there was only one process with the server and it meant that if you debug or deployed it would block it for the others.

Should I talk about code quality? Maybe not.

hey guys yesterday I got roasted cuz I was using a pc instead of Mac for development work and this was my reply. For me I don't gonna spend 2000+ $ only for 1 sec faster app loading and only for writing codes if someone willing to spend lot of money then they have completely command on there system Mac is very overpriced and overprotective it doest allow dual boot tell u what Mac sucks in 4k video editing,games,it don't even support maya or 3ds max rendering on Mac is gonna hit you hard , and there is same for linux but because it's free I don't much care about it but it is extremely crash and error prone I've installed Ubuntu nearly 20+ computer and after few days some kind of internal error occurred if u cancelled any ongoing installation it's going to hijack your system not let order program to install unless you manually clean that shit out ,yea Unix systems have bit faster app opening time and I appreciate that .
For nerds like me it's not only about coding stuff I like to do crazy stuffs

Happiness is when your application runs without crashing.

Just ranting cause the devRant iOS app keeps crashing randomly when I open rants at times, after crash same rant opens fine.
A lot of “rant” on that sentence.

Yesterday, my team had a react crash-course workshop.
It was like "you have to import a couple of libs, use 'em in different react elements you pull up and Tadaaaa! Magic is happening and your app works".
This workshop was the pinnacle of "intense".

I understood 60% of the stuff.
My team-mates about 15%.

So react is the front-end technology of choice after our architectural-team. The other teams have to use this the technology for their UIs.
This will be a lot of fun ^^

It is 7:46PM...
I started debugging at 10:30AM...
.Net native making my app crash at startup... even before the logger can write anything...

Just now, I find out it is because of a 3rd party lib...

"Going crazy" can't even begin to describe today...

I really didn't need this shit today... just not today...

Yesterday I had to register my new credit card with a national payment app (MobilePay) and it kept giving me error 32, which says "a technical error happened please try again"... Real fucking useful u peace of shit app 😠

Turns out, after a bit of research, that it will sometime crash if you language is not set to a european language. Guess what? I had mine set to English... English (US)... 😧

Like, what the fuck is that? Why would you check if a person might be from EU, be checking the language setting?
Get your shit together 😑

So I made an update to my React Native app. I changed UI of a couple of screen, added a few animations here and there, refactored how my graphQL resolvers work in the backend(no breaking changes), changed how data gets loaded into the database etc.

It worked in dev so I figured hey let's deploy it. Today is(was because it's now 3am but more on that later) a national holiday so no one goes to work so no one will use my app so I have an entire day to deploy.

I started at 15:00(because i woke up at 13:00 lol). I tested the update once again in dev and proceeded to deploy it to prod. I merged backend to master, built docker images, did migrations on the db, restarted docker-compose with new images. And now for the app. I run ./gradlew assembleRelease and it starts complaining that react-native-gesture-handler is not installed. Ugh, rm -rf node_modules && yarn install. It worked. But now gradlew crashes and logs don't tell me anything. Google tells me to change a bunch of gradle settings but none of them work. Fast forward 5h, it's around 20:00 and I isolated the issue to, again, react-native-gesture-handler. They updated from 2.2.4 to 2.3.0 which didn't fucking compile. 2 more hours passed (now 22:00) and I got v2.3.1 working which fixed the problem in 2.3.0 but made my app crash on startup. YOUR FUCKING LIBRARY GETS 250K WEEKLY DOWNLOADS AND YOU DONT EVEN BOTHER CHECKING IF IT COMPILES IN PROD ON ANDROID?! WHAT THE FUCK software-mansion?

After I solved that, my app didn't crash. Now it threw an error "Type errors: Network Request Failed" every time I fetch my legacy REST API(older parts use rest and newer use graphql. I'll refactor that in the next update). I'll spare you the debugging hell i went through but another 5h passed. Its 3am. My config had misspelled url to prod but good for dev... I hate myself and even more so react-native-gesture-handler.

Is it just my phone or does the devRant app like to crash when you spend more than a few minutes in another app? Also I don't get notifications anymore

If anyone has any reasoning behind why these happen (since sometime in August I believe), I'd really appreciate it.

Whenever anyone asks me why I dislike C++ I'm just going to point to this current app I'm working. Had a unit test with an extern method declaration that had 7 or 8 different parameters. No big. Problem is that the ACTUAL definition of the method had 1 less parameter than the extern declaration. It worked perfectly fine in x86. Ported to x64, compiled fine, hard crash at runtime. Debugger not a super lot of help. Took me a couple days to figure that one out. Also I am broke so I can't even drink the pain away. Neat.

Lessions I learned so far from my first big node/npm project with tons of users:
1) If you didn't build something for a while, expect 3 hours of resolving version conflicts for every two weeks since the last build.
2) Even if the tests pass, run the containers on your own machine and make sure that the app doesn't randomly crash before deploying
3) Even if the app seemed to work on your own machine, run the tests again in an environment mimicking prod at most 15 minutes before replacing the running containers.
4) Even if all else indicates that the app will work, only ever deploy if you expect to be available within the 4 hours following a deployment.
5) Don't use shrinkwrap for anything other than locking every version down completely. A partial shrinkwrap will produce bugs that are dependent on the exact hour you built the app _and_ the shrinkwrap file, and therefore no one will ever have seen them other than you.
6) Avoid gyp, and generally try not to interface too much with anything that doesn't run on node. If parts of your solution use very different toolchains, your problems will be approximately proportional to the amount of code. And you'd be surprised just how much code you're running. (otherwise it's more logarithmic because the more code the less likely a new assumption is unique)
7) Do not update webpack or its plugins or anything they might call unless you absolutely need to
8) Containers are cool but the alpine ones are pretty much useless if you have even just one gyp module.
9) There's always another cache. To save yourself a lot of pain, include the build time in every file or its name that the browser can download, and compare these to a fresh build while debugging to assert that the bug is still present in the code you're reading
+1) Although it may look like it, SQLite is far from a simple solution because the code and the bindings aren't maintained. In fact, it'll probably be more time consuming than using a proper database.

The iOS DevRant app is so bad, sometimes it just crashes when I try to open a rant... wth DevRant how can you fuck this up so badly?

I submitted to the bug reporter many times and they don’t do much...

I don’t know why/how, but some guy in my team put the node_modules folder on GitHub.

This person ran *npx create-react-app* and for whatever reason probably DELETED the .gitignore.

I had to fix it of course, and in the meanwhile I forgot to switch branches before changing everything, making git crash because switching branches with +4 million lines of code deleted was too much.

Why don't they let experienced front-end devs initialize projects? I don’t understand.

To me this is one of the most interesting topics. I always dream about creating the perfect programming class (not aimed at absolute beginners though, in the end there should be some usable software artifact), because I had to teach myself at least half of the skills I need everyday.

The goal of the class, which has at least to be a semester long, is to be able to create industry-ready software projects with a distributed architecture (i.e. client-server).

The important thing is to have a central theme over the whole class. Which means you should go through the software lifecycle at least once.

Let's say the class consists of 10 Units à ~3 hours (with breaks ofc) and takes place once a week, because that is the absolute minimum time to enable the students to do their homework.

1. Project setup, explanation of the whole toolchain. Init repositories, create SSH keys for github/bitbucket, git crash course (provide a cheat sheet).
Create a hello world web app with $framework. Run the web server, let the students poke around with it. Let them push their projects to their repositories.
The remainder of the lesson is for Q&A, technical problems and so on.

Homework: Read the docs of $framework. Do some commits, just alter the HTML & CSS a bit, give them your personal touch.
For the homework, provide a $chat channel/forum/mailing list or whatever for questions where not only the the teacher should help, but also the students help each other.

2. Setup of CI/Build automation. This is one of the hardest parts for the teacher/uni because the university must provide the necessary hardware for it, which costs money. But the students faces when they see that a push to master automatically triggers a build and deploys it to the right place where they can reach it from the web is priceless.
This is one recurring point over the whole course, as there will be more software artifacts beside the web app, which need to be added to the build process. I do not want to go deeper here, whether you use Jenkins, or Travis or whatev and Ansible or Puppet or whatev for automation. You probably have some docker container set up for this, because this is a very tedious task for initial setup, probably way out of proportion. But in the end there needs to be a running web service for every student which they can reach over a personal URL. Depending on the students interest on the topic it may be also better to setup this already before the first class starts and only introduce them to all the concepts in a theory block and do some more coding in the second half.

Homework: Use $framework to extend your web app. Make it a bit more user interactive with buttons, forms or the like. As we still have no backend here, you can output to alert or something.

3. Create a minimal backend with $backendFramework. Only to have something which speaks with the frontend so you can create API calls going back and forth. Also create a DB, relational or not. Discuss DB schema/model and answer student questions.

Homework: Create a form which gets transformed into JSON and sent to the backend, backend stores the user information in the DB and should also provide a query to view the entry.

4. Introduce mobile apps. As it would probably too much to introduce them both to iOS and Android, something like React Native (or whatever the most popular platform-agnostic framework is then) may come in handy. Do the same as with the minimal web app and add the build artifacts to CI. Also talk about getting software to the app/play store (a common question) and signing apps.

Homework: Use the view API call from the backend to show the data on the mobile. Play around with the mobile project to display it in a nice way.

5. Introduction to refactoring (yes, really), if we are really talking about JS here, mention things like typescript, flow, elm, reason and everything with types which compiles to JS. Types make it so much easier to refactor growing codebases and imho everybody should use it.
Flowtype would make it probably easier to get gradually introduced in the already existing codebase (and it plays nice with react native) but I want to be abstract here, so that is just a suggestion (and 100% typed languages such as ELM or Reason have so much nicer errors).
Also discuss other helpful tools like linters, formatters.

Homework: Introduce types to all your API calls and some important functions.

6. Introduction to (unit) tests. Similar as above.
Homework: Write a unit test for your form.

(TBC)

I thought the Devrant app crash problem was fixed? Three times this morning I went to reply to a rant and then the app crashed. Can no longer find the rants and my brilliant contributions remain unrealized. ;)

So I have flashed and rooted (superSU) lineageOS 14.1 thats running android 7.1.2 on my phone and now I read that this will trip safetynet and won't allow things like netflix, banking apps or pokemon go - I tried to install netflix and it worked, tried pokemon go and after granting GPS via privacy guard it worked too.

But still it seems that if I would now flash Xposed (which I didn't find a good build for 7.1.2 yet anyway) that it would actually then start tripping those protections and that I should go with "systemless root" via magisk.

How does magisk compare to superSU? I loved root some years ago because of xprivacy, adfree etc. which are actually modifying system files as far as I know and I would like to go as "extreme" as denying camera usage to apps, but not making them crash, so just like xprivacy has fake IMEI I would like to show just a black image served to the app, I remember there was an xposed module doing that, but how far can magisk compare there?

And most importantly is there a way to just hide superSU and xposed from all those detections?

React native never fails to amuse me!
For fuck sake few seconds difference in time between development machine and my phone causes the app to crash on long tap!

The solution on their GitHub was to fix time difference between Android and mac 🤦🏼‍♂️

What... The.... FUCK!

So I decided to challenge myself as an Android newbie by competing at an hackathon held in my school, which ran for 3 hours.

That's how when I decided to test run the app during the hackathon, the app always crashed upon launching it. Spent some time trying to debug it but I couldn't just resolve the issue at that point(Its currently on my To-do list).

I now decided to start a new project all over again, after about 1 hour had gone 😑.

So yeah that's my first rant. I'm expecting more 😂.

Sometimes angular can be really damn annoying with it's "Error handling".

When just one component has an error (For example using an non-existent form-control) it'll not only crash the component like it should, but the entire app.

whyyyyy do you do this to me

I dunno how this happened, but this browser in VisualWorks decided to crash for like no reason (it wasn't even running the app), and is impossible to close. At all. Like there is only one process.

Why, Smalltalk, why?

Dear Xcode,

You are a lovely IDE. Especially when an app crashes and the crash stops once I restart you. I am your friend forever.

Yours always,

Slick mouth/Pissed Off Developer

More and more, I am getting frustrated/depressed from the attitude of our customers who complain, moan and get angry about issues in their infrastructure, while at the same time, refusing to pay more so the issues could be mitigated.

Like, a client's angry with us today for having one of their non-production-critical databases inaccessible for... Hmm... About 8 hours now (So a whole workday).

Like... I get it, some of your employees couldn't work with it offline, but like... What the hell do we do? You keep data from as far back as several years ago in there, without partitioning, without exports, in a mix of innodb and myisam, so when the DB crashes, and its replication has to be reset from zero, reimporting all the data takes hours upon hours, and importing .sql files just takes time.

Or another client who got angry when their app fell out of the internet, cuz one of their myisam-based log tables crashed, and had to be repaired, with data spanning several years back, meaning it took hours to fix...

The more I work with these "basic" and "simple" infrastructure designs that is *not* redundant, or HA, the more I wonder -- How do the big names out there do it? How do you design systems with fault tolerance so a single DB table crash doesn't lead to the whole app getting inaccessible?

We have... One, exactly one, client, who uses MariaDB with Gallera, and that cluster is *amazing*, it just keeps chugging along, without a care in the world. But it cost them quite a lot, as they had to buy 3 DB servers, instead of 1...

Ever happened,.. ? the whole Application crash due to a bug in one of the libraries used and you skim through the code a million times, make a billion changes but the app still crashes.

WTF?
Just found this code:
"It is assumed that all 'static final String'-Attributes of this class are a key in the property file (which is validated by reflection)."

SO REFACTORING YOUR FUCKING MAGIC NUMBERS WITH A MEANINGFUL CONSTANT MADE THE APP CRASH. ASSHOLE.

Am currently handling a very bad code, once you add any feature the app crash and you have to fix the whole POKER application ( as you know poker is a really complicated and everything related to each other). The app crash and every single line of code goes wrong. As well i do barely have a break and am working overtime and during the weekend.
In addition to all of this i have a very complicated design and animation to the chips. Adding to this am the only developer working on this project.

Summing-up am working 10 to 11 hours per day 7 days a week. And still the manager is dissing me as if am not a good developer.

I feel so bad, i cant describe how am currently feeling.

So guys do you believe handling a very bad code might reflect your coding skills ?

My answer to their survey -->

What, if anything, do you most _dislike_ about Firebase In-App Messaging?

Come on, have you sit a normal dev, completely new to this push notification thing and ask him to make run a simple app like the flutter firebase_messaging plugin example? For sure you did not oh dear brain dead moron that found his college degree in a Linux magazine 'Ruby special edition'.

Every-f**kin thing about that Firebase is loose end. I read all Medium articles, your utterly soporific documentation that never ends, I am actually running the flutter plugin example firebase_messaging. Nothing works or is referenced correctly: nothing. You really go blind eyes in life... you guys; right? Oh, there is a flimsy workaround in the 100th post under the Github issue number 10 thousand... lets close the crash report. If I did not change 50 meaningless lines in gradle-what-not files to make your brick-of-puke to work, I did not changed a single one.

I dream of you, looking at all those nonsense config files, with cross side eyes and some small but constant sweat, sweat that stinks piss btw, leaving your eyes because you see the end, the absolute total fuckup coming. The day where all that thick stinky shit will become beyond salvation; blurred by infinite uncontrolled and skewed complexity; your creation, your pathetic brain exposed for us all.

For sure I am not the first one to complain... your whole thing, from the first to last quark that constitute it, is irrelevant; a never ending pile of non sense. Someone with all the world contained sabotage determination would not have done lower. Thank you for making me loose hours down deep your shit show. So appreciated.

The setup is: servers, your crap-as-a-service and some mobile devices. For Christ sake, sending 100 bytes as a little [ beep beep + 'hello kitty' ] is not fucking rocket science. Yet you fuckin push it to be a grinding task ... for eternity!!!

You know what, you should invent and require another, new, useless key-value called 'Registration API Key Plugin ID Service' that we have to generate and sync on two machines, everyday, using something obscure shit like a 'Gradle terminal'. Maybe also you could deprecate another key, rename another one to make things worst and I propose to choose a new hash function that we have to compile ourselves. A good candidate would be a C buggy source code from some random Github hacker... who has injected some platform dependent SIMD code (he works on PowerPC and have not test on x64); you know, the guy you admire because he is so much more lowlife that you and has all the Pokemon on his desk. Well that guy just finished a really really rapid hash function... over GPU in a server less fashion... we have an API for it. Every new user will gain 3ms for every new key. WOW, Imagine the gain over millions of users!!! Push that in the official pipe fucktard!.. What are you waiting for? Wait, no, change the whole service name and infrastructure. Move everything to CLSG (cloud lambda service ... by Google); that is it, brilliant!

And Oh, yeah, to secure the whole void, bury the doc for the new hash under 3000 words, lost between v2, v1 and some other deprecated doc that also have 3000 and are still first result on Google. Finally I think about it, let go the doc, fuck it... a tutorial, for 'weak ass' right.
One last thing, rewrite all your tech in the latest new in house language, split everything in 'femto services' => ( one assembly operation by OS process ) and finally cramp all those in containers... Agile, for sure it has to be Agile. Users will really appreciate the improvements of your mandatory service.

Currently having very funny project lead, who gives on the spot estimates for 9 years old very pathetic quality code having Android app in security domain. Memory leaks, bad practices, typos, CVEs etc. you name it we have it in our source of the app.

Since 5-6 sprints of our project, almost 50% of user stories were incomplete due to under estimations.

Basically everyone in management were almost sleeping since last 7-8 years about code quality & now suddenly when new Dev & QA team is here they wanted us to fix everything ASAP.

Most humourous thing is product owner is aware about importance of unit test cases, but don't want to allocate user stories for that at the time of sprint planning as code is almost freezed according to him for current release.

Actually, since last release he had done the same thing for each sprint, around 18 months were passed still he hadn't spared single day for unit testing.

Recently app crash issue was found in version upgrade scenario as QAs were much tired by testing hundreds of basic trivial test cases manually & server side testing too, so they can't do actual needful testing & which is tougher to automate for Dev.

Recently when team's old Macbook Pros got expired higher management has allocated Intel Mac minis by saying that few people of organization are misusing Macbooks. So for just few people everyone has to suffer now as there is no flexibility in frequent changing between WFH & WFO. 1 out of those Mac minis faced overheating & in repair since 6 months.

Out of 4 Devs & 3 QAs, all 3 QAs & 2 Devs had left gradually.

I think it's time to say goodbye 😔

Just checked on AltRant in the App Store Connect dashboard, and got a nasty surprise: a pile (22 in total) of crashes, all of them because of things I never thought would cause a crash...

Thank you for all the feedback, today I am going on an army exam. After that - bugfixes are supposed to arrive soon.

I have a dream, that one day, a major update of my app will have no bugs and/or crash reports within 24hrs of its release. ;_;

Type a long ass rant just for the app to crash when you hit post sucks. -_-

I've gone from my app crashing at a certain point to VS crashing at that specific point.. Not sure if I'm moving forward.. lol But maybe I can make Windows crash next..

Still as a scholar who has had his intership I decided that I was finally confident enough in my ability to apply for a small part-time programming job. I had an internship at a cool exhausting place with tons of expertise and I've proven myselve over there. So now I wanted a job on the side. Nothing special, just something that would make a little money with programming instead of washing dishes at the restaurant.

So I started at this small internet based startup (2 or 3 progammers) as a backend-oriented programmer. The working hours were amazingly compatible with my school schedule.

The lead dev also sounded like a smart guy. He had worked as a backend guy for years and had code running on verry critical public infrastructure that if it were to fail we'd be evacuated from our homes.

As a first asignment I got an isolated task to make an importer for some kind of file format that needed integration. So I asked for access to the code. I didn't get it since they were going to re-do the entire backend based on the code I wrote. I just needed to parse the file in a usable object structure. So I found out that the file format was horrible and made a quite nice set of objects that were nice. At the end of the first week or so I asked if I could get access to the code again, so I could integrate it. Answer was no. The lead dev would do that. I could however get access to my private repository.

Next week a new intern was taken to build a multiplatform responsive app. Only downside was that all the stuff he had ever done was php based websites. It wasn't going anywhere anytime soon, but I figured that that was where internships were for. So I ended up helping him a lot and taught him some concepts of OOP and S.O.L.I.D. and the occasional 30 minute rants of IndexOutOfRangeException, ArgumentException and such.

So one day he asked me how to parse a json string and retrieve a specific field out of it.
I gave him something like the following to start with:
"
JObject json;
if(!JObject.TryParse(jsonString, out json))
{
//handle error
}
string value;
if(!json.tryget("foo", out value).../// code continues
"

but then the main dev stepped in and proposed the following since it wouldn't crash on an API change:
"
dynamic json = new JObject(jsonString);
string value = json.myJsonValue;
"

After me trying to explain to him that this was a bad choise for about 15 minutes because of all kinds of reasons I just gave up. I was verry mad that this young boy was forced to use bad programming pracises while he was clearly still learning. I know I shouldn't pick up certain practises. But that boy didn't.

Almost everytime the main dev was at the office I had such a mindboggling experience.

After that I got a new assignment.
I had to write another xml file format parser.
Of course I couldn't have any access to our current code because... it was unnecesary. We were going to use my code as a total replacement for the backend again.
And for some reason classes generated from XSD weren't clear enough so after carefull research I literally wrapped xsd generated code in equivalent classes.

At that moment, I realized I made some code that was totally useless since it wasn't compatible with any form of their API or any of the other backend code. (I haven't seen their API. I didn't have access to the source.) And since I could've just pushed them generated XSD's that would've produced thesame datastructure I felt like I was a cheat. I also didn't like that I wasn't allowed to install even the most basic tooling. (git client or, Ide refactoring plugins, spelling checker etc...)

Now I was also told that I couldn't discuss issues with the new guy anymore since it was a waste of my valuable time, and they were afraid that I taught him wrong concepts.

This was the time that my first paycheck came in so I quitted my job.
I haven't seen any of the features that I've worked on. :)

I don't often have reasons to rant, but today is the one.

We had a deadline to finish a project, because today people are being trained on it. I've been working my ass off on it for a year now.

I "finished" about 2 weeks ago, meaning QA could start for real 2 weeks ago. As you can imagine for a project this long, there was bugs. Lots of them.

We did our best to fix most of them, or find work-arounds we could use during the demo.

Let's just say it isn't going great so far. We have several known bugs, which at some point may crash the app, a very low confidence in the fact that it's going to work well.

Oh and obviously the client is one who already use heavily the solution. Today we figured we never tested on a device with 0% disk space. Files are cut partway because of that, and obviously things crash.

I have a feeling there will be yelling sometime soon.

Right now I'm enjoying the calm before the storm, with coffee in hand.

Why do people still continue to promise dates to clients, after me telling them for 5 years not to do that?

We are a 2 devs team, with 11 apps on 2 platforms, 2 back-ends (one is legacy) and obviously our marketing site, which doubles up as e-commerce. We just can't promise anything, because any emergency reduce our development bandwith for new features either to 50% or 0%. There are so much known bugs it's not funny anymore, and we don't even have time to solve those.

To add insult to injury, at the beginning of the month, the SaaS provider for our legacy back-end (which have not been maintained for 2 years now) decided we had to update to PHP7.1 before 1st October. If we don't do anything, on monday this thing is broken. I hate that thing, and I hate having to maintain it even though I was promised I wouldn't have to ever have anything to do on it.

Monday will be "fun"...

I was writing a random rant about something that happened to me this morning, and the app decide to crash a second before I could post it.
I get it devRant, my stories aren't interesting, but you could at least have crash at the beginning and not after I have already spent half an hour writing the story :(

Anyone else using DevRant on iOS 16.0?

It crashes about 1-3 times a day. I haven’t been able to intentionally reproduce. The app just closes.
This never happened in previous versions.

I’m not an iOS dev so not sure how I can help prepare for public release. I’m not even sure if it is the OS, but since it worked with last iOS, I’m guessing.

Some of the events when it crashed.
1. Browsing comments on someone’s post
2. Double tapping to like a comment (it might be the rant as well, I don’t exactly remember)
3. Opening a rant from the list of rants.

Cannot reproduce. For example, relaunching the app and opening the same rant again didn’t cause a crash.

@dfox is it a known issue to have crashes on iOS when visiting the notifications tab?

If not here’s what I can gather: When opening the notifications menu, app will crash after the devRant logo wobbles 3-4 times. After reopening the app and repeating the process about 3-5 times, the app will load into the notifications menu. However, when tapping on any individual notification, it will often crash after the same 3-4 wobbles of the devRant logo.

Now, I’m not a mobile developer (Nor a react developer, if you guys are using react) but here’s some things that I would think might cause this:
- An unhandled exception?
- If you use multiple server instances, they may be out of sync?

Not sure what it could be tbh. But I hope this helps, keep up the great work!

Modified stuff on production server without checking documentation, because I was cocky and tought that I remembered everything. The worst thing is, that right after that I took a lunch break and only realised what have I done after that. For an hour or so anyone who opened our app experienced an instant crash...

Any remote crash reporter for angular 7 apps u suggest guys ? I will go live soon with a web app and need to see stacktrace or whatever usable info if anything goes wrong.

whenever I take extended brakes from reading whats on devrant the initial reopen of the app leads to a immediate crash. Android nougat.

I like the UWP idea, and in general how UWP look like.. But holy shit they suck.. It takes me fucking 2 minutes to open an UWP app it crashes at least once in those two minutes. And when I open them, its just a matter of time when it will crash.. Lets talk about Skype UWP, love the design, hate the perfomance. You know when Skype syncs? When I open it and wait a minute for it to be usable, and then it updates conversation.. Then.. And only then.. Whaf the fuck is wrong with it? The platform or developers? I fucking hope they improve with, and I don't think I'm the only one with this problem..

Was having a good and ahead of schedule...should have seen the foreboding omens..=(

Unity is the worst! Every single version of it has some kind of bug that prevents some piece of what I'm working on to be buggy. 5.3.4 seems the most stable, as far as the app working, but likes to crash on me several times a day on Mac OS. I'm really tired of this.