{"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\/news\/ne-soglashajtes-razrabatyvat-to-chego-ne-ponimaete","title":{"rendered":"Mos prano zhvillimin e asaj q\u00eb nuk e kupton","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Mos
\n
\nQ\u00eb nga fillimi i vitit 2018, un\u00eb kam marr\u00eb postin e liderit\/drejtorit\/t\u00eb zhvilluesit t\u00eb avancuar n\u00eb ekip \u2014 quajeni si t\u00eb doni, por e r\u00ebnd\u00ebsishme \u00ebsht\u00eb se un\u00eb plot\u00ebsisht jam p\u00ebrgjegj\u00ebs p\u00ebr nj\u00eb nga moduli dhe p\u00ebr t\u00eb gjith\u00eb zhvilluesit q\u00eb punojn\u00eb mbi t\u00eb. Ky pozicion m\u00eb hap nj\u00eb perspektiv\u00eb t\u00eb re mbi procesin e zhvillimit, pasi jam i angazhuar n\u00eb m\u00eb shum\u00eb projekte dhe marr pjes\u00eb m\u00eb aktivisht n\u00eb vendimmarrje. S\u00eb fundmi, fal\u00eb k\u00ebtyre dy rrethanave, papritur e kuptova sa shum\u00eb niveli i kuptimit ndikon n\u00eb kod dhe n\u00eb aplikacion.<\/p>\n

Mendimi q\u00eb dua t\u00eb shpreh lidhet me faktin se cil\u00ebsia e kodit (dhe e produktit p\u00ebrfundimtar) \u00ebsht\u00eb ngusht\u00eb e lidhur me at\u00eb se sa njer\u00ebzit q\u00eb merren me dizajnimin dhe shkruajn\u00eb kodin jan\u00eb t\u00eb vet\u00ebdijsh\u00ebm p\u00ebr at\u00eb q\u00eb po b\u00ebjn\u00eb.<\/p>\n

Ndoshta tani po mendoni: \"Faleminderit, kapiten. Sigurisht, do t\u00eb ishte mir\u00eb t\u00eb kuptoje \u00e7far\u00eb po shkruan. Ndryshe, me t\u00eb nj\u00ebjtin sukses mund t\u00eb angazhojm\u00eb nj\u00eb grup majmun\u00ebsh q\u00eb t\u00eb godas\u00eb rast\u00ebsisht n\u00eb tastier\u00eb dhe t\u00eb qet\u00ebsohemi me k\u00ebt\u00eb.\" Dhe keni plot\u00ebsisht t\u00eb drejt\u00eb. Ndaj, e pranoj si nj\u00eb t\u00eb dh\u00ebn\u00eb: ju e kuptoni se t\u00eb kesh nj\u00eb kuptim t\u00eb p\u00ebrgjithsh\u00ebm p\u00ebr at\u00eb q\u00eb b\u00ebn \u00ebsht\u00eb e nevojshme. Kjo mund t\u00eb quhet niveli zero i kuptimit, dhe ne nuk do ta shqyrtojm\u00eb at\u00eb n\u00eb detaje. Do t\u00eb shqyrtojm\u00eb n\u00eb detaje se \u00e7far\u00eb sakt\u00ebsisht duhet t\u00eb kuptosh dhe si ndikon kjo n\u00eb vendimet q\u00eb merr \u00e7do dit\u00eb. N\u00ebse do ta dija k\u00ebto gj\u00ebra paraprakisht, 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>
\nPavar\u00ebsisht se nuk do t\u00eb shihni asnj\u00eb rresht kodin m\u00eb posht\u00eb, un\u00eb akoma mendoj se gjith\u00e7ka q\u00eb thuhen k\u00ebtu ka r\u00ebnd\u00ebsi t\u00eb madhe p\u00ebr shkruarjen e nj\u00eb kodi cil\u00ebsor dhe ekspresiv. <\/p>\n

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

\nZhvilluesit zakonisht arrijn\u00eb n\u00eb k\u00ebt\u00eb nivel n\u00eb fazat m\u00eb t\u00eb hershme t\u00eb karrier\u00ebs s\u00eb tyre, ndonj\u00ebher\u00eb madje edhe pa ndihm\u00ebn e t\u00eb tjer\u00ebve \u2014 t\u00eb pakt\u00ebn sipas v\u00ebzhgimeve t\u00eb mia. Imagjinoni se keni marr\u00eb nj\u00eb raport t\u00eb defektit: nj\u00eb funksion n\u00eb aplikacion nuk funksionon, dhe duhet ta rregulloni. Si do t\u00eb veproni?<\/p>\n

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

    \n
  1. T\u00eb gjeni fragmentin e kodit q\u00eb shkakton problemin (si t\u00eb b\u00ebhet kjo \u2014 \u00ebsht\u00eb nj\u00eb tem\u00eb e ve\u00e7ant\u00eb, e cila e trajtoj n\u00eb librin tim p\u00ebr kodin e vjet\u00ebr)<\/li>\n
  2. T\u00eb b\u00ebni ndryshime n\u00eb k\u00ebt\u00eb fragment<\/li>\n
  3. T\u00eb siguroheni se defekti \u00ebsht\u00eb korrigjuar dhe se nuk ka ndodhur ndonj\u00eb gabim regresiv<\/li>\n<\/ol>\n

    \nTani do t\u00eb p\u00ebrqendrohemi n\u00eb pik\u00ebn e dyt\u00eb \u2014 ndryshimin e kodit. Ka dy qasje p\u00ebr k\u00ebt\u00eb proces. E para: t\u00eb kuptosh sakt\u00ebsisht se \u00e7far\u00eb po ndodh n\u00eb kodin aktual, t\u00eb identifikosh gabimin dhe ta korrigjosh at\u00eb. E dyta: t\u00eb ec\u00ebsh n\u00eb err\u00ebsir\u00eb \u2014 t\u00eb shtosh, p\u00ebr shembull, +1 n\u00eb operatorin kusht ose n\u00eb cik\u00ebl, t\u00eb shoh\u00ebsh n\u00ebse kjo funksionon n\u00eb skenar\u00ebt q\u00eb nevojiten, pastaj t\u00eb provosh ndonj\u00eb gj\u00eb tjet\u00ebr dhe k\u00ebshtu deri n\u00eb pafund\u00ebsi.<\/p>\n

    Qasja e sakt\u00eb \u00ebsht\u00eb ajo e par\u00eb. Si\u00e7 shpjegon Steve McConnell n\u00eb librin e tij Code Complete (p\u00ebr leht\u00ebsim, e rekomandoj shum\u00eb), sa her\u00eb q\u00eb ne ndryshojm\u00eb di\u00e7ka n\u00eb kod, duhet t\u00eb jemi n\u00eb gjendje t\u00eb parashikojm\u00eb me besim se si do t\u00eb ndikoj\u00eb kjo n\u00eb aplikacion. Po citoj nga memoria, por n\u00ebse rregullimi i gabimit nuk rezulton ashtu si\u00e7 e kishe pritur, kjo duhet t\u00eb t\u00eb shqet\u00ebsoj\u00eb shum\u00eb, duhet t\u00eb v\u00ebsh n\u00eb dyshim t\u00eb gjith\u00eb planin t\u00ebnd t\u00eb veprimit.<\/p>\n

    Duke p\u00ebrmbledhur, p\u00ebr t\u00eb kryer nj\u00eb rregullim t\u00eb mir\u00eb t\u00eb gabimeve, i cili nuk do t\u00eb d\u00ebmtoj\u00eb cil\u00ebsin\u00eb e kodit, duhet t\u00eb kuptosh 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 kjo?<\/h4>\n

    \nKy nivel arrin t\u00eb kuptohet shum\u00eb m\u00eb pak intuitivisht se niveli i m\u00ebparsh\u00ebm. Un\u00eb, duke qen\u00eb ende nj\u00eb zhvillues i ri, e kuptova k\u00ebt\u00eb fal\u00eb shefit tim, dhe m\u00eb pas shpesh e kam shpjeguar thelbin e k\u00ebsaj \u00e7\u00ebshtjeje fillestar\u00ebve.<\/p>\n

    Tani le t\u00eb imagjinojm\u00eb se keni marr\u00eb nj\u00ebkoh\u00ebsisht dy raportime p\u00ebr gabime: n\u00eb t\u00eb parin flitet p\u00ebr skenarin A, dhe n\u00eb t\u00eb dytin \u2014 p\u00ebr skenarin B. N\u00eb t\u00eb dy rastet ndodh di\u00e7ka e gabuar. Prandaj, s\u00eb pari merresh me gabimin e par\u00eb. Duke u udh\u00ebhequr nga parimet q\u00eb nxorr\u00ebm p\u00ebr nivelin e par\u00eb t\u00eb kuptimit, ju futeni thell\u00eb n\u00eb kodin q\u00eb ka lidhje me problemin, e kuptoni pse ai e b\u00ebn aplikacionin t\u00eb sillet ashtu si\u00e7 sillet n\u00eb skenarin A, dhe b\u00ebni ndryshime t\u00eb arsyeshme q\u00eb japin pik\u00ebrisht rezultatin q\u00eb prisnit. Gjith\u00e7ka shkon mrekulluesh\u00ebm.<\/p>\n

    Pastaj kaloni te skenari B. E p\u00ebrs\u00ebrisni skenarin n\u00eb p\u00ebrpjekje p\u00ebr t\u00eb provokuar gabimin, por \u2014 surpriz\u00eb! \u2014 tani gjith\u00e7ka funksionon si\u00e7 duhet. P\u00ebr t\u00eb konfirmuar dyshimin tuaj, anuloni ndryshimet e b\u00ebra gjat\u00eb pun\u00ebs mbi gabimin A, dhe gabimi B riaktualizohet. Rregullimi juaj zgjidhi t\u00eb dy problemet. Fat i mir\u00eb!<\/p>\n

    Nuk e kishit pritur kurr\u00eb 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 pse ka funksionuar edhe p\u00ebr skenarin B. N\u00eb k\u00ebt\u00eb pik\u00eb, tundimi \u00ebsht\u00eb i madh p\u00ebr t\u00eb vendosur se t\u00eb dyja detyrat jan\u00eb finalizuar me sukses. Kjo \u00ebsht\u00eb logjike: q\u00ebllimi ishte t\u00eb eliminohen gabimet, apo jo? Por puna ende nuk ka p\u00ebrfunduar: ju duhet t\u00eb kuptoni pse veprimet tuaja e korrigjuan gabimin n\u00eb skenarin B. Pse? Sepse, ndoshta, ai punon mbi parime t\u00eb gabuara, dhe at\u00ebher\u00eb do t'ju duhet t\u00eb k\u00ebrkoni nj\u00eb zgjidhje tjet\u00ebr. Ja disa shembuj t\u00eb till\u00eb.<\/p>\n