this post was submitted on 21 Jul 2023
43 points (100.0% liked)

Programming

13376 readers
1 users here now

All things programming and coding related. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 1 year ago
MODERATORS
alyaza@beehaw.org
Hexorg@beehaw.org
remington@beehaw.org
43
Why do I always need to rationalize use of proper architecture? (szmer.info)
submitted 1 year ago by Kubenqpl@szmer.info to c/programming@beehaw.org
17 comments fedilink hide all child comments
 

Why is it so in mobile development that 90% of projects does not have proper architecture, and when there is one, devs complain about it. I don't see it being a case for other technologies of development, only mobile. In mobile the project always has spaghetti code, barely any abstraction it is developed just to be finished as quickly as possible and that's it. And when there is clean architecture introduced, everyone complains. Why is it just a case in mobile development?

Just disclaimer: It is not like the architecture in project is completely new invention, it uses well known principles and approaches

you are viewing a single comment's thread
view the rest of the comments
[–] lemmyvore@feddit.nl 2 points 1 year ago* (last edited 1 year ago)

You should be able to point out multiple concrete issues with arcane code, like ramp-up difficulty for new people, knowledge being concentrated in the heads of developers and is lost when they leave, maintenance costs etc.

But tbh if the code is fast and scales well it's typically not an architectural issue if it's ugly and unmaintainable.

If they don't care about that it's their prerogative. There's usually a decision maker assuming technical debt and technical risk. Just make sure you have proof of pointing it out (email is usually best, most companies purge their chats periodically nowadays).