Going through exactly this situation. Instead of making new one now management told me to just add new UI & features in 11 years old Android app.

@fighter no it was bigger than that, it was to gradually transform children into genius by evolving their imagination to increase their intelligence. AI, machine learning, behavior tracking etc. was implemented.

Unfortunately it couldn't materialize due to reason like DevOps etc. & project died prematurely.

That's exactly our DevOps engineer.
Apart from that he always lies that somebody else changed some config so particular tool was broken. 😏
We all know it's a lie because only he had credentials & at the timestamp of log of that change in config only he was online & all were at home.🤷🏻‍♂️

He was QA earlier & changed his field & having total 15+ years of experience. 🤦🏻‍♂️

Our architect who had selected him was repenting & saying he (architect) was cursed then only he got such a pain in the a** DevOps. 😑

@SortOfTested I am also not in favor of working in service company, but till now in my life I have worked on our client product companies' projects to build a product from scratch, including in this company. This is the 1st incident of this kind in my experience.

I don't overuse OOP, I use it only where it's logical to do so, helps to reduce efforts, redundancy, gives re-usability benefits etc.

Clean code name is given to attract people who generally don't apply common sense in coding due to some reasons.

About libraries, I think we shouldn't re-invent the wheel when it's open-source, free to use in commercial product by proper license, have long history of improvements, fixes, dedicated team to fix library specific bugs etc.

It's basic principle as 'less is more', less custom code will give you more time to focus on your business logic than common trivial tasks which libraries already do efficiently.

@heyheni I have tried 2-3 times by sending mails to project lead with highlighting these issues but he ignores.
Project lead is having very good relations with manager & I am just a month old in this 2-3 years old team. This way also I can't do anything.

Now I see only one way as making long term improvements list & keep it in backlog somewhere so that by chance in future somebody from client side higher management find out it.

@Fast-Nop earlier this maintenance project was with some other company & this product was initially an in-house development of our that client, an IT enterprise company.

About techdebt that enterprise company itself should understand as source repo is still under their control.

I am quite surprised as code is never really reviewed with any seriousness in whole 8 years. No excuse can justify this.

To avoid rework in new features or change requests, I had suggested best practices to my team when I had recently joined this project, but project lead don't want to follow it. He is just interested in visible things like UI only to impress client.

They don't want to do even memory profiling to find high memory usage or leak which I can already see due to Android anti-patterns used in new implementations also.

Sorry about devrant tag, didn't know it's for devrant.com only.

@heyheni actually there are client side security auditors with big experience but may be knowing Java only & not knowing Android basics or may be don't want to increase their headache as too large & too many changes are needed.

Highlighted same issues orally in my team but nobody wants to work on tasks which are not given by client.

I play music keyboard when I have some spare time. Don't know notations, chords but mostly I can play 2-3 lines of any song I like. It thrills me to set tune of songs I like by doing experiments & unwinds me for next work day.

- Indian devs mostly careless & just do frugal tricks to finish tasks without caring about memory leak, speed etc.

- Indian developers mostly work for money & they don't want to 'waste' time in 1 project's good quality code when more projects' bad quality code can give enough money.

- There is almost no learning culture for domain speciality. Even top Indian IT companies prompt developers to take stupid crash course of a week or 2 in any language & expect them to start working in that.
Now after that those half knowledge having developers will do experiments for even basic things in live projects of any client.

- Lastly due to hardware revolution now a days good quality code may make only around 10-15% difference in performance.

Like in even in Android like lower H/W requirement platform, apps' speed improvement like 1-2 seconds or saving 20-30 MB memory in 4GB RAM phones won't be noticeable. Compare this with server side dev with around 32/64 GB RAM, cloud computing etc.

2/2

According to my experience below are the reasons

- Almost all companies of the world need some IT solution & world don't have those many good developers, so to cop up with the quantity they have to compromise on developers' quality & so...

- Gradually almost all non-Indian client companies who ran by managers became too much cost saving (due to recession or too many alternative Indian companies) so they don't care or don't understand importance about code quality.

- Bad code quality is good for Indian IT company as they can get more money from client in the name of "improvement". As mostly projects are TnM (Time & Material) based client has to pay also if they want "improvement".

- Good devs won't be appreciated for good code quality as it's not important for manager if your code finish particular task 2 second faster or saves 20MB memory. It's fine as far as application is not crashing.
1/2

@SortOfTested it's my inner frustration after observing code quality in around 7-8 prestigious projects in my 500 million dollar employer. I can't understand how people can take such heavy projects so lightly 😢.

@dontknowshit even for testing part management wants QA team to 100 times repeat same simple test cases like login but don't want to automate it.

@dontknowshit correct. Basically company started paying below average salaries so good talents had evaporated & what we have now are good for nothing 'coders'.

Adding to above post :
No security best practices were followed, Salesforce backend credentials stored in plain text in Android Manifest. Username password are passed in GET request params in plain text to call Salesforce Query API. Client have charity edition of salesforce so no risk of overbilling by credentials hijacking, but data about end user's contact info can be leaked surely.