Mobile Engineers: Are any of you still having fun at your job despite AI?
retained text
A little over 3yoe. Kinda quirky, but I spent my first 2 years on mobile SDKs for iOS. It was my absolute complete dream job in every imaginable way. That team got a new manager though and long story short, I had to change to another team. I switched to a fullstack team on a React/Ruby on Rails stack. Coincidentally at around the same time was when most people at my company, myself included, started writing 100% of code via AI. I would go so far as to say that I now "hate" my job, and so I've been contemplating trying to switch back to mobile. But, I'm concerned that in the age of AI, I won't like mobile nearly as much anymore. Basically, I really like to focus on code rather than like server uptime, DB load, load balancing etc. **I fully recognize that AI has killed writing for-loops by hand, but what about code architecture-y things?** Our SDK was based on Redux architecture, and I loved working on that system. I love having debates about where a piece of logic should live in code, which components need to be privy to what information, the most graceful way to accomplish dependency injection, learning about code patterns that enable effective and easy testing etc. People will reference "higher-level skills" that are safe from AI: **is what I described above high enough level?** I feel like typically people couch those discussions in things like the server uptime, DB load, load balancing etc, which again I do not enjoy at all. I think I could still enjoy my job if my AI prompts were like "Create a new reducer as the child of this other reducer and give it xyz state and abc actions and have an action that when y happens emits z result," or, "Create a protocol witness setup with these methods and then create a testing witness with a stubbed version of the network io method that switches upon the url and returns...". **If you are a mobile engineer, is that sort of what your AI usage looks like?** Because on my new team, my AI usage is literal just copy pasting Jira tickets into Cursor and saying "Please implement this, open a draft pr, and then review the PR and implement any feedback items." All of our TS and Ruby code is absolute slop anyway, so it literally doesn't matter what the code looks like AT ALL and literally nobody cares, myself included because Ruby and (shitty) React are so hopelessly gross anyway. If there's a way to write good code in these frameworks, our company doesn't do it. Plus, it's a little hard to explain concisely, but outside of the dashboard/portal UI, we pretty much just write scripts that run top to bottom anyway. Everybody in charge of evaluating me thinks I am doing much, much better ever since I started not looking at the code I put up for review. **Does anybody in any corner of the industry care about thoughtful code architecture at all anymore?** Under the leadership of a new staff engineer, my old mobile SDKs team has said they'll be removing the Redux system in favor of pure OOP hierarchy. They actually asked my opinion on the proposal and I said I'd opine once they issued a more technically-oriented proposal with ideas for alternative architectures. Then the new staff engineer said "What do you mean by alternatives? Anything but \[Redux\] kinda, which uses proper dependency injection, references, chain of calls for better stacks, et cetera." They specifically called out that they think this approach will make it easier for LLMs to contribute to the codebase.
document fetched 2026-09-30 00:24 · canonical https://reddit.com/r/cscareerquestions/comments/1wtf1fo/mobile_engineers_are_any_of_you_still_having_fun