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
Search - "iphone jokes"
-
Did I ever tell you kids about the time I worked for a company that got a contract to develop an iOS application around some object detection software that had been developed by another team?
Company I was working for was a tiny software consultancy, and this was my first ever dev job (I’m at my second now 😅). Nobody at the company has experience building mobile applications but CEO decides that the app should be written in React Native because _he_ knows React Native.
During a meeting with the client, CEO jokes about how easy the ask is and says he could finish it in a weekend. Please note that Head of Engineering had already budgeted a quarter for the work. CEO says we can do it in a week! And moves up the deadline. And only assigns two engineers to project. I am not one of those engineers.
The two engineers that are put on it struggle. A lot. They can’t seem to get the object detection to work at all, and the code that’s already written is in Objective-C. I realize one of the issues is that the engineers on the project can’t read Objective-C because they have no experience with Objective-C or even C. I have experience with C, so I volunteer to take a look at it to try to see what’s going on.
Turns out the problem is that the models are trained on one type of image format and the iPhone camera takes images in a different format.
The end of the week comes, they do not succeed in figuring out the image conversion in React Native. There’s an in-person demo with the customers scheduled for the next Monday. CEO spends the weekend trying to build the app. Only succeeds in locking literally every other engineer out of the project.
They manage to negotiate a second chance where we deliver what we were supposed to deliver at the original schedule.
I spent the weekend looking up how to convert images and figure it would be a lot easier to interface with the Objective-C if we used Swift. Taught myself enough Swift over the weekend to feel dangerous. Spoke to Head of Engineering on Monday and proposed solution — start over in Swift. Volunteer to lead effort. Eventually convince them it’s a good idea (and really, what’s the worst that can happen? If this solves our main problem at the moment, that’s still more progress than the original team made)
Spend the next week working 16 hour days building out application. Meet requirements for next deadline. Save contract.
And that’s ONE of the stories of my first dev job that got me hired as a senior engineer despite only having 10 months of work experience in the industry.11 -
Let me tell you a tale, children. Of how one of the mostly ghastly, horrid pieces of software currently on this earth came to be in its current, pitiful state.
It all began on January 28th, 2015.
On that day, Tim Cook, CEO of Apple, sat leisurely in his office. He had just finished watching a live stream for a conference held by Facebook.
Minutes after the stream ended, he quietly sat in his chair, pondering over what was just shown.
The whole keynote was well done, he thought. But something about it just didn’t sit right with him. It was one specific line uttered by one of the keynote speaker that bothered him.
“React Native will help developers easily write code that will work on both iOS and Android”.
Out of all the talking done throughout that conference, it was that sentence, in particular, that stuck out like a sore thumb t Cook.
Those words began to echo in his head. “...Android”, Tim muttered to himself, gritting his teeth.
He immediately grabbed his Iphone from his pocket, and called the Technical Director of Xcode.
On the phone, the two discussed Xcode as it pertained to Facebook’s latest tool.
“Now, I’m not saying that we shouldn’t provide any support for React Native”, Cook told the director; “Just make it a bit more inconvenient for anyone using React, that’s all”.
The director thought his boss was nuts. Why on earth would you want to intentionally make using an IDE as painful of an experience as possible? But the technical director also knew that, more importantly, he wanted to keep his job.
“...We’ll do our best to make it a total pain in the ass to use React Native in Xcode”, the director told his boss with a shrug.
And so began one of the sickest jokes ever played on developers. A joke so twisted and cruel, it would make even the creator of PHP gasp in abject horror.
Who knew that someone would go out of their way to create an IDE that doesn’t even bloody work half of the time.
And don’t get me started on the absolute piss poor excuse for documentation this thing has.2