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

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

[–] amenji@fosstodon.org 4 points 1 year ago

@amotoohno @Kubenqpl

The way I look at this, it's all about incentive.

If the product you're working on is a SaaS product, and the way you design your architecture aren't allowing you to be agile and flexible in order to respond to changing business requirements quickly, you'll lose clients.

OTOH, if you're an outsourced dev working on an internal org's application. Your likely reaction would be: "Who cares? I'm still being paid."

It's all about incentive.