Reply to thread

Message: <blockquote data-quote="HAneo" data-source="post: 26423533" data-attributes="member: 17432">OK there is a couple of approaches1. code base dekak maintain karana eka normaly karanne na. eka nisa api karane gap analysis ekak karanawa process deka athara. ehema karala monawada company deke salary management process eke wenaskam kiyala hoyagannawa. passe balanawa changes parameterize karanna puluwanda kiyala. ehema nam parameter walin separete karala ekama code base eke gahanawa2. branching use karanne ekama basic code base eke versioning walata. eka company dekaka ekama code base eka maintain karanna danne na eka ethics walin pita .  mama me kiyana eka experiance ekath ekka enne. eka thama api mulin analysis karala design karanakota adura gannawa changes wenna puluwan areas. ewaa api design pattern yodagena separate project wala gahanawa. mekata mama kiyane "CustomeLibrary" eka kkiyala. mekedi wenne core eka ehemmama thiyagena ara CustomLibrary project eka witharak customer wise change karanawa. api modification karanne Core ekata nisa addon fetures and future expanditions core eke set wenawa. so aluth client kenektath ekama base eka yanne 90% kma. me widihe design ekak karanna pattama amaruyi.  but with practise apita penawa meke me tika custome karanna one kiyala</blockquote>

Top Bottom