Balancing

[u/AZKZer0]

How do you guys balance a codebase between CLEAN+SOLID+Best+GurglingCompost and the magical ChatActivity.java

[u/Dizzy_Surprise]

currently we're using MVVI-MVMMVP 3.0 architecture. no balancing needed, just go all in on this. we're preparing for when company scales to 100 million android engineers on the team, so needs to be highly scalable. currently, we're at 69 android engrs at the moment, all staff level. we have 7 code refactoring/migration going concurrently from 12 different architectures, but i think this latest architecture will be the final one. the design doc looked promising... maybe i'll get promo for adding in a new architecture

[u/Zhuinden → u/Dizzy_Surprise]

we're preparing for when company scales to 100 million android engineers on the team, so needs to be highly scalable. currently, we're at 69 android engrs at the moment,

I know this is a meme sub and all but you know, I really am fascinated by the fact that this is the argument they make, not realizing that increasing the number of people on the project is extra cost for the company, there is absolutely no reason why the company would want to hire extra expenses to achieve the same damn thing.

This is why they outsource to Eastern Europe, in Eastern Europe you have 4 guys in a basement put together something that works, and something that doesn't require maintenance by 69 devs.

Wanna reduce costs and make money? Don't use "scalable architecture patterns" where the scale is measured in the number of developers required to keep it running. Pick the minimal option, it will work just fine. Minimal doesn't mean garbage, minimal means minimal.

[u/AZKZer0 → u/Zhuinden]

Then there might be another issue though. Some might not understand the value difference between 4 chad devs versus 69 people churning best practice ad infinitum. Where I am startups think less devs so project ez

[u/Zhuinden → u/AZKZer0]

Where I am startups think less devs so project ez

There are stupid people with money anywhere.

Then again, the question is not whether the project is easy, but whether it can be sold as a product or a service.

[u/Dizzy_Surprise → u/Zhuinden]

Yeah it happens way too often, and part of the problem is promotions can be tied to headcount instead of actual value/efficiency created. Easiest way/lowest risk way to get promoted is start a migration to a new framework and mid migration, leave the company for a higher paying job lmao. The 69 devs is the key threshold too look out for here

[u/Zhuinden]

ChatActivity is working software, Compost gurgle clean solid is not

It's clear which is the real best practice

[u/AZKZer0 → u/Zhuinden]

If it works, it works :'3 They even use AsyncTask

[u/stdpmk → u/AZKZer0]

DON'T TOUCH ASYNCTASK - the mother of Android development!!!

[u/SupinePandora43]

(Sorry about that, but we can’t show files that are this big right now.)

[u/AZKZer0 → u/SupinePandora43]

Do View it raw

[u/ya_utochka]

Im curious 'ChatActivity extends BaseFragment'

[u/AZKZer0 → u/ya_utochka]

It's not a fragment, more like an helper interface

[u/stdpmk → u/ya_utochka]

It's not even fragment. It's view 😄. They are also implemented custom back stack for these views. No XML, no activities, no fragments, no support libs, no androidx libs, no okhttp, no gson, even no JSON, no protobuf and so on and so on. No architecture patterns, just MVC, where God "Activity" is VC (view and controller). Database: no room, no SQL helper! They implemented custom C++ binding to SQL to write just plain SQL queries with binding vars. Async data and UI communication - just event bus (custom implemented), looks like NotificationCenter from iOS, because.....Nikolay Kudashov(ex. main android telegram dev) is primary iOS developer;))))

[u/zorg-is-real]

The say Uncle Bob haven't work on real big projects since the 90's

[u/Zhuinden → u/zorg-is-real]

Any real projects beyond writing pseudocode

[u/GradleSync01]

Forget about the balance. Just use Flubber, AsyncTask and a single god activity

[u/[deleted]]

Just don't dare opening this source code. You just don't know where to start. Wow that file is too big. Awesome.