That reminds me of one reason I got out of mobile app development, totally forgot about until now
Often times the hiring managers wanted to see something more akin to a portfolio, like an art project, for apps that many times didn’t exist anymore or have a production server up anymore
But the more arbitrary metric was trying to be sure that I worked on anything “big”
And the 8-12 megabyte package sizes - which I spent a lot of time optimizing with many competence inspiring techniques - would signal that the app or service or userbase wasn't big. Which had nothing to do with anything, could have hundreds of millions of downloads and users
In that space there is a huuuge incentive for bloatware
I have never experienced nor heard of a hiring manager determining the outcome of a candidate based on the MB of an app they worked on. I would run away from working for a company like that.
> I would run away from working for a company like that
although a form of affirmation about my experience, and caked in privilege, my experience is that a company that does one odd thing during an interview process isn't indicative of anything. actual job and team I’m on can be fine
Often times the hiring managers wanted to see something more akin to a portfolio, like an art project, for apps that many times didn’t exist anymore or have a production server up anymore
But the more arbitrary metric was trying to be sure that I worked on anything “big”
And the 8-12 megabyte package sizes - which I spent a lot of time optimizing with many competence inspiring techniques - would signal that the app or service or userbase wasn't big. Which had nothing to do with anything, could have hundreds of millions of downloads and users
In that space there is a huuuge incentive for bloatware