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

  • TheCee@programming.dev
    link
    fedilink
    arrow-up
    19
    ·
    1 year ago

    Hard to tell without knowing some details.

    Maybe they are incompetent or lazy. Maybe they don’t expect the project to last that long. Maybe they are seniors that know your suggested architecture doesn’t actually add to maintainability but increases connascences.

    How would we know, OP.

    • LittleLily@shinobu.cloud
      link
      fedilink
      arrow-up
      17
      ·
      edit-2
      1 year ago

      Also to add that “well known principles and approaches” doesn’t always equal good, readable, maintainable code; especially when it comes to a lot of OOP principles. Abstracting everything into a Factory/Decorator/whatever pattern you might think is the best approach after having only worked with OOP principles your whole career is almost always not what’s actually the best way to structure things. In fact the code OP is complaining about may not even be that bad, it might just look so to someone who has no familiarity with any programming practices (like FP) that are outside their bubble.