16

We had 1 Android app to be developed for charity org for data collection for ground water level increase competition among villages.

Initial scope was very small & feasible. Around 10 forms with 3-4 fields in each to be developed in 2 months (1 for dev, 1 for testing). There was a prod version which had similar forms with no validations etc.

We had received prod source, which was total junk. No KT was given.

In existing source, spelling mistakes were there in the era of spell/grammar checking tools.

There were rural names of classes, variables in regional language in English letters & that regional language is somewhat known to some developers but even they don't know those rural names' meanings. This costed us at great length in visualizing data flow between entities. Even Google translate wasn't reliable for this language due to low Internet penetration in that language region.

OOP wasn't followed, so at 10 places exact same code exists. If error or bug needed to be fixed it had to be fixed at all those 10 places.

No foreign key relationships was there in database while actually there were logical relations among different entites.

No created, updated timestamps in records at app side to have audit trail.

Small part of that existing source was quite good with Fragments, MVP etc. while other part was ancient Activities with business logic.

We have to support Android 4.0 to 9.0 of many screen sizes & resolutions without any target devices issued to us by the client.

Then Corona lockdown happened & during that suddenly client side professionals became over efficient.

Client started adding requirements like very complex validation which has inter-entity dependencies. Then they started filing bugs from prod version on us.

Let's come to the developers' expertise,
2 developers with 8+ years of experience & they're not knowing how to resolve conflicts in git merge which were created by them only due to not following git best practice for coding like only appending new implementation in existing classes for easy auto merge etc.

They are thinking like handling click events is called development.

They don't want to think about OOP, well structured code. They don't want to re-use code mostly & when they copy paste, they think it's called re-use.

They wanted to follow old school Java development in memory scarce Android app life cycle in end user phone. They don't understand memory leaks, even though it's pin pointed by memory leak detection tools (Leak canary etc.).

Now 3.5 months are over, that competition was called off for this year due to Corona & development is still ongoing.

We are nowhere close to completion even for initial internal QA round.

On top of this, nothing is billable so it's like financial suicide.

Remember whatever said here is only 10% of what is faced.

- An Engineering lead in a half billion dollar company.

Comments
  • 9
    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.
  • 1
    Are these developers Indian, by any chance?
  • 2
    @vatsalengg wow, there is so much wrong in that company...
  • 2
    @dontknowshit correct. Basically company started paying below average salaries so good talents had evaporated & what we have now are good for nothing 'coders'.
  • 1
    @vatsalengg sounds similar to a situation that I walked into two years ago, we got rid of them but we are still suffering the consequences of their actions today and I don’t see it getting better anytime soon because of an unwillingness to ‘redo’ instead of ‘work around’ some of those bad decisions.
  • 2
    @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.
  • 3
    @vatsalengg I am facing the same problem, I have one tester that has to manually test everything, due to a policy of ‘writing no tests’. It takes weeks for a simple change to be tested, due to testing not even being this guys primary job, but because no client is paying for us to write tests, the company refuses to let us.
Add Comment