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 - "false reports"
-
Senior development manager in my org posted a rant in slack about how all our issues with app development are from
“Constantly moving goalposts from version to version of Xcode”
It took me a few minutes to calm myself down and not reply. So I’ll vent here to myself as a form of therapy instead.
Reality Check:
- You frequently discuss the fact that you don’t like following any of apples standards or app development guidelines. Bit rich to say the goalposts are moving when you have your back to them.
- We have a custom everything (navigation stack handler, table view like control etc). There’s nothing in these that can’t be done with the native ones. All that wasted dev time is on you guys.
- Last week a guy held a session about all the memory leaks he found in these custom libraries/controls. Again, your teams don’t know the basic fundamentals of the language or programming in general really. Not sure how that’s apples fault.
- Your “great emphasis on unit testing” has gotten us 21% coverage on iOS and an Android team recently said to us “yeah looks like the tests won’t compile. Well we haven’t touched them in like a year. Just ignore them”. Stability of the app is definitely on you and the team.
- Having half the app in react-native and half in native (split between objective-c and swift) is making nobodies life easier.
- The company forces us to use a custom built CI/CD solution that regularly runs out of memory, reports false negatives and has no specific mobile features built in. Did apple force this on us too?
- Shut the fuck up5 -
!dev
Last week I watched a DIY video where at the end the guy dumped detergent water on the grass. I kindly commented it's a €150 fine. Their response was on the lines of "Oh yeah, Mr Proper? And what would you say if I told you I spray my whole garden with soap to get rid of weeds, huh?".
Well, you dumb fuck, I don't care what you do, I wasn't attacking you, I was being *nice* and warned you about the fucking fine that you're going to fucking pay because your channel name is your first and last name and your video shows the street and the house number but whatever.
Today I couldn't log into my YouTube account. Why was that, you might ask? Well, because the dumb fuck paid the fucking fine and assumed I was the one that ratted, so he made a video about it and his dumb fuck audience falsely reported all of my videos for child abuse and promoting terrorism.
I only upload unboxing videos that debunk scummy "deals". 🤦♂️11 -
What's the point of using the tracking then?
Or why don't you just show me the 3 weeks date as estimated arrival date instead of the wrong date showing on the tracking report currently?
Adding 7 days is fuck simple.
Why give wrong reports and false hope?4 -
Built a Svelte app year ago and it's broken today.
This is not the case with Windows. You can still run a app built on 1999 today.
Opened an issue on their repo requesting that they should add backwards compatibility.
No later than 5 seconds. It got closed and locked with this comment,
"Welcome to development when you don't write your entire stack yourself by hand.
Please open helpful bug reports or don't open any at all."
This is what every FOSS project got as defense. They think since they work for free, they can do what the fuck they want.
The defense is false because they put their OSS project on their resume and in return they get hired for full time work or consulting.
I fucking sue you Svelte if I had money to hire expensive lawyers. This time you are just lucky.38 -
me vs my job at mnc laggard part 9/n . previous @ https://devrant.com/rants/6602068/...
====
I think i have now realised why working at corporate MNC sucks: they are reluctant to make a good product for their end users.
- they first come up with feature without a proper planning and research.
- then they are in a rush to release it to live audience by ignoring the possible issues that could arise
- when they see it fail, they are like, okay with that and blame it as a failed experiment
- instead of removing/disabling it, they are okay to keep it remain alive in the app, even if it causes customer inconveneience.
- meanwhile, they put false reports for their higher managers as a success and when an enhancement/modification comes for that feature from the higher up, they again start the loop by pushing a new feature without proper planning and a rush
as a dev, it fuckin kills me. I joined in the middle of one of these ugly loops. The app has a camera feature where the camera will generate voices to take pictures and record video , like "goto next car view" , "close the bonnet and focus", etc while the user follows instructions.
the ticket for me was to just add a flash button to this camera. But the more i dive into it, the more i hate it:
- the existing camera implementation provides api for toggling a camera flash, but when i attached it with a ui button, it would not work
- the existing implementation will send images /videos as direct payload data, resulting in generating very large payload curls . our app has a curl logger and it starts crashing.
- the existing implementation also crashes at uploading videos.
So where does it trouble me?well, I have a ticket to add just a fucking button, but i will have to replace the whole camera module and start from scratch. also the crash causing loggers will need some workarounds, otherwise i could not check the apis. and my manager will be like "why are you taking so long to add a flashlight?" and i would be like "coz i wanna put this flashlight up your -2