Details
-
AboutGraduating soon but already working as a dev
-
SkillsPython, C#, js (mainly)
-
LocationAustralia
Joined devRant on 11/18/2017
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
As a long-time iPhone user, I am really sorry to say it but I think Apple has completed their transition to being a company that is incompetent when it comes to software development and software development processes.
I’ve grown tired of hearing some developers tell me about Apple’s scale and how software development is hard and how bugs should be expected. All of those are true, but like most rules of law, incompetence and gross negligence trumps all of that.
I’m writing this because of the telugu “bug”/massive, massive security issue in iOS 11.2.5. I personally think it’s one of the worst security issues in the history of modern devices/software in terms of its ease of exploitation, vast reach, and devastating impact if used strategically. But, as a software developer, I would have been able to see past all of that, but Apple has shown their true incompetence on this issue and this isn’t about a bug.
It’s about a company that has a catastrophic bug in their desktop and mobile platforms and haven’t been able to, or cared to, patch it in the 3 or so days it’s been known about. It’s about a company, who as of a view days ago, hasn’t followed the basic software development process of removing an update (11.2.5) that was found to be flawed and broken. Bugs happen, but that kind of incompetence is cultural and isn’t a mistake and it certainly isn’t something that people should try to justify.
This has also shown Apple’s gross incompetence in terms of software QA. This isn’t the first time a non-standard character has crashed iOS. Why would a competent software company implement a step in their QA, after the previous incident(s), to specifically test for issues like this? While Android has its issues too and I know some here don’t like Google, no one can deny that Google at least has a solid and far superior QA process compared to Apple.
Why am I writing this? Because I’m fed up. Apple has completely lost its way. devRant was inaccessible to iOS users a couple of times because of this bug and I know many, many other apps and websites that feature user-generated content experienced the same thing. It’s catastrophic. Many times we get sidetracked and really into security issues, like meltdown/spectre that are exponentially harder to take advantage of than this one. This issue can be exploited by a 3 year old. I bet no one can produce a case where a security issue was this exploitable yet this ignored on a whole.
Alas, here we are, days later, and the incompetent leadership at Apple has still not patched one of the worst security bugs the world has ever seen.81 -
I call my git repos the field hospital.
I didn't finish my studies, but I seem to be the most qualified person to pick up the scalpel. Big corner of body bags. New brilliant ideas arrive, I do what I can with the time I have. Sometimes something survives, but it's usually too heavily mutilated to fully function. Unfinished refactorings develop into hardened scar tissue, the feature creep starts festering and leaking.
I should get better at triaging, just deleting old crap, pick one project and nurse it back to health.
But it's not easy to start with fresh focus, when your keyboard is still soaked in booze and the blood and tears of all the victims you've butchered.3 -
My old employer used to used a highly complex people management system, made up of around fifteen or so different tools and packages. Apparently this had been the case for decades, so in my spare time, I wrote an entirely bespoke, extensible HR web application that could be easily modified without changing the code. It even supported the weird spider web management structure.
I took it to my area manager, who pushed it up the chain. Apparently the country representative liked it a lot, so decided to bring me on board for an implementation and test case. Fast forward a few months, and people are singing praises. I get a huge promotion, with a sizeable pay bump to match.
Sadly, most of my country was sold out to another org, who decided pretty much straight off to make 90% of us redundant. Last I heard, though, my app is now in use in almost every operating country around the world. Not bad for something I wrote in my spare time.
I'm waiting for them to need modifications, because I never had time to complete the documentation...4 -
Once in university I needed to write a simple program in c++ and upload it to online complier which would pass test inputs. It was homework, but I was bored during the next lecture, so I wrote the program.
On my phone.
Directly into the "paste" window in browser.
It wasn't comfortable at all, so I wrote everything in one line.
And got bonus points from lecturer later.
After some questions, ofc, like "wtf why everything is in one line"3 -
Anyone here relaxes by cooking a dish?
I use normal vegetable oil, and lots of it. Don’t judge me.16 -
Good news: Today my app reached 1 million daily users. 😃😃😃💰
Bad news: It started out as a side project and my shitty code is not scaling well at all. 🙃19 -
So I had a very long team viewer session with my colleague and after 3 hours we were finished and I went straight to pornhub after the session. But the problem was that I forget to close the team viewer session and 30 minutes later I saw him disconnect. FML, I’ll see him tomorrow11
-
Tech support to my friend:
Friend: Root my phone!
Me: why
Friend: play store is not working
Me: why do u want to root for that?
Friend: is there any other option?
Me: give me ur phone
After 20 sec ...
Me: Sign in to ur Google account 😐😐3 -
What if we fed all rants and comments on devRant to a neural network trained to write rants and comments on others?10
-
I cannot spell for shit, so my coworker keeps commenting on my pull requests with spelling fixes...
Decided to buy this for him today...12