{"id":36115,"date":"2019-10-31T22:09:42","date_gmt":"2019-10-31T19:09:42","guid":{"rendered":"https:\/\/prohoster.info\/blog\/ne-soglashajtes-razrabatyvat-to-chego-ne-ponimaete\/"},"modified":"2019-10-31T22:09:42","modified_gmt":"2019-10-31T19:09:42","slug":"ne-soglashajtes-razrabatyvat-to-chego-ne-ponimaete","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/novosti-interneta\/ne-soglashajtes-razrabatyvat-to-chego-ne-ponimaete","title":{"rendered":"Mos pranoni t\u00eb zhvilloni at\u00eb q\u00eb nuk e kuptoni","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Mos
\n
\nQ\u00eb nga fillimi i vitit 2018, un\u00eb mbaj pozitat e liderit\/kryetarit\/zhvilluesit t\u00eb avancuar n\u00eb ekip \u2014 quajeni si t\u00eb doni, por thelbi \u00ebsht\u00eb se un\u00eb kam p\u00ebrgjegj\u00ebsin\u00eb totale p\u00ebr nj\u00eb nga modulet dhe p\u00ebr t\u00eb gjith\u00eb zhvilluesit q\u00eb punojn\u00eb mbi t\u00eb. Ky pozicion m\u00eb ofron nj\u00eb perspektiv\u00eb t\u00eb re mbi procesin e zhvillimit, pasi jam i angazhuar n\u00eb nj\u00eb num\u00ebr m\u00eb t\u00eb madh projektesh dhe marr pjes\u00eb m\u00eb aktivisht n\u00eb marrjen e vendimeve. S\u00eb fundmi, fal\u00eb k\u00ebtyre dy rrethanave, papritur kuptova se sa shum\u00eb niveli i kuptimit ndikon n\u00eb kod dhe n\u00eb aplikacion.<\/p>\n

Mendimi q\u00eb dua t\u00eb shpreh \u00ebsht\u00eb se cil\u00ebsia e kodit (dhe e produktit p\u00ebrfundimtar) \u00ebsht\u00eb ngusht\u00eb e lidhur me aq sa njer\u00ebzit q\u00eb merren me projektimin dhe shkruajn\u00eb kodin e kuptojn\u00eb at\u00eb q\u00eb po b\u00ebjn\u00eb.<\/p>\n

Ndoshta tani po mendoni: \"Faleminderit, kap. Sigurisht, do ishin t\u00eb dobishme t\u00eb kuptoje se \u00e7far\u00eb po shkruan. N\u00eb t\u00eb kund\u00ebrt, mund t\u00eb pun\u00ebsojm\u00eb nj\u00eb grup majmun\u00ebsh q\u00eb t\u00eb godasin \u00e7el\u00ebsat rast\u00ebsisht dhe t\u00eb qet\u00ebsohemi me k\u00ebt\u00eb.\" Dhe keni t\u00eb drejt\u00eb. Prandaj, e pranoj si nj\u00eb fakt t\u00eb gatsh\u00ebm: ju e kuptoni se \u00ebsht\u00eb e domosdoshme t\u00eb keni nj\u00eb p\u00ebrmbledhje t\u00eb p\u00ebrbashk\u00ebt t\u00eb asaj q\u00eb b\u00ebni. K\u00ebt\u00eb mund ta quajm\u00eb nivelin zero t\u00eb kuptimit, dhe nuk do ta shqyrtojm\u00eb at\u00eb n\u00eb detaje. N\u00eb vend t\u00eb k\u00ebsaj, do t\u00eb analizojm\u00eb se \u00e7far\u00eb sakt\u00ebsisht duhet t\u00eb kuptoni dhe si ndikon k\u00ebto n\u00eb vendimet q\u00eb merrni \u00e7do dit\u00eb. N\u00ebse do isha njohur me k\u00ebto gj\u00ebra m\u00eb her\u00ebt, do t\u00eb m\u00eb kishte kursyer nj\u00eb sasi t\u00eb madhe koh\u00eb t\u00eb humbur dhe kod t\u00eb dyshimt\u00eb.
\n<\/a><\/noindex>
\nMegjith\u00ebse keni parasysh se nuk do t\u00eb shihni asnj\u00eb rresht kodi k\u00ebtu, akoma mendoj se gjith\u00e7ka q\u00eb \u00ebsht\u00eb th\u00ebn\u00eb k\u00ebtu ka nj\u00eb r\u00ebnd\u00ebsi t\u00eb madhe p\u00ebr shkruan kod t\u00eb cil\u00ebsis\u00eb s\u00eb lart\u00eb dhe t\u00eb shprehsh\u00ebm. <\/p>\n

Niveli i par\u00eb i kuptimit: Pse nuk funksionon?<\/h4>\n

\nKy nivel zakonisht arrin zhvilluesit n\u00eb fazat m\u00eb t\u00eb hershme t\u00eb karrier\u00ebs s\u00eb tyre, ndonj\u00ebher\u00eb madje pa ndihm\u00ebn e askujt \u2014 t\u00eb pakt\u00ebn sipas v\u00ebzhgimeve t\u00eb mia. Imagjinoni se keni marr\u00eb nj\u00eb raport p\u00ebr gabime: nj\u00eb funksion n\u00eb aplikacion nuk funksionon, duhet ta riparoni. Si do t\u00eb veproni?<\/p>\n

Skema standarde duket k\u00ebshtu:<\/p>\n

    \n
  1. T\u00eb identifikoni fragmentin e kodit q\u00eb shkakton problemin (si ta b\u00ebni k\u00ebt\u00eb \u00ebsht\u00eb nj\u00eb tem\u00eb e ve\u00e7ant\u00eb, e cila e zbuloj n\u00eb librin tim p\u00ebr kodin obsolett)<\/li>\n
  2. T\u00eb b\u00ebni ndryshime n\u00eb at\u00eb fragment<\/li>\n
  3. T\u00eb siguroheni q\u00eb gabimi \u00ebsht\u00eb rregulluar dhe nuk ka ndodhur ndonj\u00eb gabim regresiv<\/li>\n<\/ol>\n

    \nTani le t\u00eb p\u00ebrqendrohemi n\u00eb pik\u00ebn e dyt\u00eb \u2014 b\u00ebrjen e ndryshimeve n\u00eb kod. Ekzistojn\u00eb dy qasje ndaj k\u00ebtij procesi. E para: t\u00eb kuptoni se \u00e7far\u00eb sakt\u00ebsisht po ndodh n\u00eb kodin aktual, t\u00eb identifikoni gabimin dhe ta rregulloni at\u00eb. E dyta: t\u00eb avanconi n\u00eb m\u00ebnyr\u00eb t\u00eb rast\u00ebsishme \u2014 t\u00eb shtoni, p\u00ebr shembull, +1 n\u00eb nj\u00eb operator kushtor ose cik\u00ebl, t\u00eb shihni n\u00ebse funksioni ka filluar t\u00eb punoj\u00eb n\u00eb skenarin e k\u00ebrkuar, pastaj t\u00eb provoni di\u00e7ka tjet\u00ebr dhe k\u00ebshtu deri n\u00eb pafund\u00ebsi.<\/p>\n

    Qasja e sakt\u00eb \u00ebsht\u00eb e para. Si\u00e7 shpjegon Steve McConnell n\u00eb librin e tij Code Complete (n\u00eb fakt, e rekomandoj shum\u00eb), \u00e7do her\u00eb q\u00eb ne b\u00ebjm\u00eb ndonj\u00eb ndryshim n\u00eb kod, duhet t\u00eb jemi n\u00eb gjendje t\u00eb parashikojm\u00eb me siguri se si do t\u00eb ndikoj\u00eb kjo n\u00eb aplikacion. Citoj nga kujtesa, por n\u00ebse riparimi i gabimit nuk funksionon ashtu si\u00e7 e prisnit, kjo duhet t'ju shqet\u00ebsoj\u00eb; duhet ta v\u00ebn\u00eb n\u00eb pik\u00ebpyetje gjith\u00eb planin tuaj t\u00eb veprimit.<\/p>\n

    K\u00ebshtu, p\u00ebr t\u00eb kryer nj\u00eb riparim t\u00eb mir\u00eb t\u00eb gabimeve q\u00eb nuk do ta p\u00ebrkeq\u00ebsoj\u00eb cil\u00ebsin\u00eb e kodit, duhet t\u00eb kuptoni si struktur\u00ebn e kodit ashtu edhe burimin e problemit t\u00eb ve\u00e7ant\u00eb.<\/p>\n

    Niveli i dyt\u00eb i kuptimit: Pse funksionon?<\/h4>\n

    \nKy nivel arrihet shum\u00eb m\u00eb pak intuitivisht se sa ai i m\u00ebparshmi. Nd\u00ebrsa isha ende nj\u00eb zhvillues i ri, e kuptova at\u00eb nga shefi im, dhe m\u00eb von\u00eb disa her\u00eb e shpjegova thelbin e tij fillestar\u00ebve.<\/p>\n

    K\u00ebt\u00eb her\u00eb le t\u00eb imagjinojm\u00eb se ju keni pranuar menj\u00ebher\u00eb dy raportet p\u00ebr gabime: n\u00eb t\u00eb parin flitet p\u00ebr skenarin A, n\u00eb t\u00eb dytin p\u00ebr skenarin B. N\u00eb t\u00eb dy skenar\u00ebt ndodh di\u00e7ka e gabuar. Prandaj, filloni s\u00eb pari me gabimin e par\u00eb. Duke u udh\u00ebhequr nga parimet q\u00eb kemi nxjerr\u00eb p\u00ebr nivelin e par\u00eb t\u00eb kuptimit, ju thelloheni n\u00eb kodin q\u00eb lidhet me problemin, zbuloni pse ai e detyron aplikacionin t\u00eb sillet k\u00ebshtu n\u00eb skenarin A dhe b\u00ebni ndryshime t\u00eb arsyeshme q\u00eb japin sakt\u00ebsisht at\u00eb rezultat q\u00eb prisnit. Gjith\u00e7ka shkon shk\u00eblqyesh\u00ebm.<\/p>\n

    Pastaj kaloni n\u00eb skenarin B. Ju p\u00ebrs\u00ebrisni skenarin n\u00eb nj\u00eb p\u00ebrpjekje p\u00ebr t\u00eb provokuar gabimin, por \u2014 surpriz\u00eb! \u2014 tani gjith\u00e7ka funksionon si duhet. N\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb konfirmuar hipotez\u00ebn tuaj, ju anulloni ndryshimet e b\u00ebra gjat\u00eb pun\u00ebs mbi gabimin A dhe gabimi B kthehet p\u00ebrs\u00ebri. Riparimi juaj i gabimit zgjidhi t\u00eb dy problemet. Fat i mir\u00eb!<\/p>\n

    Nuk e kishit pritur k\u00ebt\u00eb. Keni gjetur nj\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb riparuar gabimin n\u00eb skenarin A dhe nuk keni asnj\u00eb ide se pse ka funksionuar p\u00ebr skenarin B. N\u00eb k\u00ebt\u00eb faz\u00eb, temptimi p\u00ebr t\u00eb vendosur se t\u00eb dy detyrat jan\u00eb plot\u00ebsuar me sukses \u00ebsht\u00eb shum\u00eb i madh. Kjo \u00ebsht\u00eb krejt\u00ebsisht logjike: q\u00ebllimi ishte t\u00eb hiqnim gabimet, apo jo? Por puna nuk ka mbaruar akoma: ju ende duhet t\u00eb kuptoni pse veprimet tuaja riparuan gabimin n\u00eb skenarin B. Pse? Sepse, ndoshta, ai po funksionon n\u00eb parime t\u00eb gabuara, dhe at\u00ebher\u00eb do t\u00eb duhet t\u00eb k\u00ebrkoni nj\u00eb zgjidhje tjet\u00ebr. Ja disa shembuj t\u00eb till\u00eb:<\/p>\n