{"id":89062,"date":"2020-07-18T07:41:57","date_gmt":"2020-07-18T05:41:57","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/devops-ili-kak-my-teryaem-zarabotnuyu-platu-i-budushhee-it-otrasli"},"modified":"2020-07-18T07:41:57","modified_gmt":"2020-07-18T05:41:57","slug":"devops-ili-kak-my-teryaem-zarabotnuyu-platu-i-budushhee-it-otrasli","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/devops-ili-kak-my-teryaem-zarabotnuyu-platu-i-budushhee-it-otrasli","title":{"rendered":"DevOps ose si humbasim pagat dhe t\u00eb ardhmen e industris\u00eb IT","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

M\u00eb e trishtueshmja n\u00eb situat\u00ebn e sotme \u00ebsht\u00eb se IT po b\u00ebhet gradualisht nj\u00eb industri ku pothuajse nuk ka fjal\u00ebn \u201cstop\u201d n\u00eb sasin\u00eb e detyrave p\u00ebr nj\u00eb person. <\/p>\n

Duke lexuar shpalljet p\u00ebr pun\u00eb, ndonj\u00ebher\u00eb edhe shohim jo 2-3 njer\u00ebz, por nj\u00eb kompani t\u00eb t\u00ebr\u00eb n\u00eb nj\u00eb person, t\u00eb gjith\u00eb po nxitohen, borxhi teknik po rritet, legjenda e vjet\u00ebr p\u00ebrball\u00eb produkteve t\u00eb reja duket perfekte, sepse n\u00eb t\u00eb pakt\u00ebn ka dokumentacion dhe komente n\u00eb kod, produktet e reja shkruhen me shpejt\u00ebsi t\u00eb madhe, por p\u00ebrfundimisht nuk mund t\u00eb p\u00ebrdoren ende p\u00ebr nj\u00eb vit pas shkruan, dhe shpesh ky vit nuk sjell fitime. P\u00ebr m\u00eb tep\u00ebr, shpenzimet p\u00ebr \u201ccloud\u201d jan\u00eb m\u00eb t\u00eb larta se shitjet e sh\u00ebrbimit. Parat\u00eb e investitor\u00ebve shpenzohen p\u00ebr mb\u00ebshtetje t\u00eb nj\u00eb sh\u00ebrbimi q\u00eb ende nuk funksionon, por q\u00eb tashm\u00eb \u00ebsht\u00eb l\u00ebshuar n\u00eb rrjet si i till\u00eb.<\/a><\/noindex>
\nSi nj\u00eb shembull: nj\u00eb kompani e njohur, e cila remasterizoi nj\u00eb loj\u00eb t\u00eb vjet\u00ebr q\u00eb mori vler\u00ebsimet m\u00eb t\u00eb ulta n\u00eb historin\u00eb e industris\u00eb. Un\u00eb isha nj\u00eb nga ata q\u00eb bleva k\u00ebt\u00eb produkt, por ende tani ky produkt punohet tmerr\u00ebsisht, dhe n\u00eb parim nuk dukej se duhej t\u00eb dilte n\u00eb shitje n\u00eb k\u00ebt\u00eb form\u00eb. Kthimet e parave, r\u00ebnia e vler\u00ebsimit, nj\u00eb num\u00ebr i madh bllokimesh p\u00ebr p\u00ebrdoruesit n\u00eb forume p\u00ebr ankesat mbi performanc\u00ebn e sh\u00ebrbimeve. Numri i patcheve nuk ngaz\u00ebllehet, por t\u00eb qan, por p\u00ebrmbajtja mbetet jo e p\u00ebrdorshme. N\u00ebse ky qasje sjell rezultate t\u00eb tilla p\u00ebr nj\u00eb kompani, e cila merret me zhvillimin q\u00eb nga viti 91, at\u00ebher\u00eb situata p\u00ebr kompanit\u00eb q\u00eb sapo po fillojn\u00eb aktivitetin e tyre \u00ebsht\u00eb edhe m\u00eb e keqe.<\/p>\n

Por ne e pam\u00eb k\u00ebt\u00eb qasje nga perspektiva e p\u00ebrdoruesit t\u00eb sh\u00ebrbimit, tani le t\u00eb shohim problemet q\u00eb kan\u00eb dal\u00eb p\u00ebr punonj\u00ebsit. <\/p>\n

Shum\u00eb her\u00eb d\u00ebgjoj pretendimin se nuk duhet t\u00eb ekzistojn\u00eb grupe DevOps, q\u00eb kjo \u00ebsht\u00eb nj\u00eb metodologji etj., por ja q\u00eb kompanit\u00eb kan\u00eb pushuar s\u00eb k\u00ebrkuari noka, DBA, infrastrukturist\u00eb dhe inxhinier\u00eb nd\u00ebrtimi \u2013 tani gjith\u00e7ka \u00ebsht\u00eb nj\u00eb inxhinier DevOps n\u00eb vetmi. Natyrisht, n\u00eb disa kompani t\u00eb ve\u00e7anta ekzistojn\u00eb akoma k\u00ebto vende, por ato b\u00ebhen gjithnj\u00eb e m\u00eb pak. Shum\u00eb e quajn\u00eb k\u00ebt\u00eb zhvillim, un\u00eb personalisht e shoh si degradim, \u00ebsht\u00eb e pamundur t\u00eb mbash nj\u00eb nivel t\u00eb mir\u00eb njohurish n\u00eb t\u00eb gjitha drejtimet dhe n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb t\u00eb punosh jo m\u00eb shum\u00eb se 8 or\u00eb. Sigurisht \u2013 kjo jan\u00eb fantazi. N\u00eb realitet, shum\u00eb IT-ista jan\u00eb t\u00eb detyruar t\u00eb punojn\u00eb 12 ose 14 or\u00eb, nga t\u00eb cilat paguhen 8. Dhe shpesh edhe pa dit\u00eb pushimi, sepse \"m\u00eb \u00ebsht\u00eb caktuar nj\u00eb detyr\u00eb, dokumentet mungojn\u00eb ose jan\u00eb t\u00eb pasakta, dhe sh\u00ebrbimi ka kosto\", dhe p\u00ebr nj\u00eb gabim n\u00eb re nuk mund t\u00eb marr\u00ebsh pag\u00ebn p\u00ebr disa muaj, ve\u00e7an\u00ebrisht n\u00ebse punon me IP. N\u00eb fakt, ne po humbasim fjal\u00ebn n\u00eb biznes, s\u00eb bashku me ndarjen e p\u00ebrgjegj\u00ebsive, gjithnj\u00eb e m\u00eb shum\u00eb p\u00ebrballem me menaxher\u00eb q\u00eb nd\u00ebrhyjn\u00eb n\u00eb proceset e zhvillimit, duke mos kuptuar asgj\u00eb nga to, ata ngat\u00ebrrojn\u00eb t\u00eb dh\u00ebnat e biznesit dhe pun\u00ebn e aplikacionit, si rezultat fillon haosi. <\/p>\n

Kur fillon haosi, biznesi d\u00ebshiron t\u00eb gjej\u00eb fajtorin, dhe k\u00ebtu nevojitet nj\u00eb fajtor universale, t\u00eb hedh\u00ebsh fajin mbi m\u00eb shum\u00eb se 10 njer\u00ebz \u00ebsht\u00eb e v\u00ebshtir\u00eb, prandaj menaxher\u00ebt bashkojn\u00eb pozitat, sepse sa m\u00eb shum\u00eb detyra t\u00eb ket\u00eb nj\u00eb specialist, aq m\u00eb e leht\u00eb \u00ebsht\u00eb t\u00eb d\u00ebshmohet neglizhenca e tij. Dhe n\u00eb kushtet Agile, gjetja e \"fajtorit\" dhe nd\u00ebshkimi - \u00ebsht\u00eb baza e metodologjis\u00eb s\u00eb menaxhimit t\u00eb biznesit. Agile ka dal\u00eb prej koh\u00ebsh nga IT, dhe koncepti i tij kryesor \u00ebsht\u00eb \u2013 k\u00ebrkesa p\u00ebr rezultate t\u00eb p\u00ebrditshme. Problemi \u00ebsht\u00eb se nj\u00eb specialist i specializuar ngusht\u00eb nuk do t\u00eb ket\u00eb gjithmon\u00eb rezultate t\u00eb p\u00ebrditshme, q\u00eb do t\u00eb thot\u00eb se do t\u00eb jet\u00eb m\u00eb e v\u00ebshtir\u00eb p\u00ebr t\u00eb raportuar, dhe kjo \u00ebsht\u00eb nj\u00eb tjet\u00ebr arsye pse biznesi d\u00ebshiron \"specialist\u00eb p\u00ebr gjith\u00e7ka\". Por arsyeja kryesore natyrisht \u00ebsht\u00eb FOT \u2013 ai \u00ebsht\u00eb arsyeja kryesore e t\u00eb gjitha ndryshimeve, p\u00ebr rikompens\u00eb njer\u00ebzit pranuan t\u00eb punojn\u00eb p\u00ebr veten dhe at\u00eb djalin tjet\u00ebr. Por n\u00eb fund, ashtu si n\u00eb fusha t\u00eb tjera, kjo u b\u00eb thjesht nj\u00eb detyr\u00eb, p\u00ebr nj\u00eb pag\u00eb m\u00eb t\u00eb ul\u00ebt p\u00ebr nj\u00eb num\u00ebr m\u00eb t\u00eb madh sh\u00ebrbimesh t\u00eb ofruara. <\/p>\n

Sot tani, \u00ebsht\u00eb e zakonshme t\u00eb shihen artikuj q\u00eb thon\u00eb se zhvilluesit duhet t\u00eb din\u00eb t\u00eb b\u00ebjn\u00eb deployment dhe t\u00eb merren me infrastruktur\u00ebn p\u00ebrkrah inxhinier\u00ebve DevOps, por \u00e7far\u00eb rezultati sjell kjo? P\u00ebrgjigjja \u00ebsht\u00eb - nj\u00eb r\u00ebnie n\u00eb cil\u00ebsin\u00eb e sh\u00ebrbimeve dhe n\u00eb cil\u00ebsin\u00eb e zhvilluesve. T\u00eb dy dit\u00eb m\u00eb par\u00eb, i shpjegoja nj\u00eb zhvilluesi se mund t\u00eb shkruhet dhe lexohet nga hoste t\u00eb ndrysh\u00ebm, nd\u00ebrsa ai insistonte q\u00eb nuk e kishte par\u00eb kurr\u00eb nj\u00eb gj\u00eb t\u00eb till\u00eb, kishte vet\u00ebm n\u00eb settings orm host, port, db, user, password dhe mjaft... Por zhvilluesi di t\u00eb filloj\u00eb deployments, t\u00eb shkruaj\u00eb YAML... Nd\u00ebrsa ka harruar p\u00ebr testet unitare dhe komentet n\u00eb kod.<\/p>\n

Si pasoj\u00eb, shohim k\u00ebt\u00eb \u2013 puna e vazhdueshme, k\u00ebrkimi i zgjidhjeve p\u00ebr problemet jasht\u00eb orarit t\u00eb pun\u00ebs, m\u00ebsimi i vazhduesh\u00ebm gjat\u00eb fundjavave, nuk p\u00ebr rritjen e t\u00eb ardhurave, por p\u00ebr mbajtjen e vetes n\u00eb l\u00ebvizje. Zhvilluesit detyrohen t\u00eb ndihmojn\u00eb inxhinierin DevOps me CI\/CD, dhe n\u00ebse zhvilluesi nuk ka koh\u00eb, ai fillon t\u00eb ndjehet i mbingarkuar, dhe menaxher\u00ebt fillojn\u00eb t\u00eb krijojn\u00eb presion, dhe n\u00ebse kjo nuk rrit d\u00ebshir\u00ebn p\u00ebr t\u00eb punuar jasht\u00eb orarit, at\u00ebher\u00eb fillojn\u00eb t\u00eb aplikojn\u00eb sanksione dhe gjoba, duke e b\u00ebr\u00eb personin t\u00eb k\u00ebrkoj\u00eb nj\u00eb vend tjet\u00ebr pune, duke l\u00ebn\u00eb pas tij nj\u00eb borxh teknik sa Everest-i, si rezultat borxhi fillon t\u00eb rritet edhe te zhvilluesit, sepse ata detyrohen t\u00eb shkruajn\u00eb kod me m\u00eb pak refaktoring, p\u00ebr t'u siguruar q\u00eb ndihmojn\u00eb ose inxhinierin e vjet\u00ebr ose t\u00eb ri DevOps, nd\u00ebrsa menaxher\u00ebt jan\u00eb gjithmon\u00eb t\u00eb k\u00ebnaqur, sepse fajtori \u00ebsht\u00eb aty dhe duket menj\u00ebher\u00eb, q\u00eb do t\u00eb thot\u00eb se rregulli kryesor n\u00eb Agile p\u00ebr menaxhimin \u00ebsht\u00eb zbatuar, \u00ebsht\u00eb identifikuar fajtori dhe rezultatet e nd\u00ebshkimit t\u00eb tij jan\u00eb t\u00eb dukshme. <\/p>\n

Nj\u00ebher\u00eb kam mbajtur nj\u00eb prezantim n\u00eb ITGM me titull \"kur do t\u00eb m\u00ebsojm\u00eb t\u00eb themi 'jo'\" - rezultatet ishin shum\u00eb treguese. Nj\u00eb num\u00ebr i madh njer\u00ebzish besojn\u00eb se ky fjal\u00eb \u00ebsht\u00eb tabu, dhe derisa ne t\u00eb ndalojm\u00eb s\u00eb menduari k\u00ebshtu, problemet do t\u00eb vazhdojn\u00eb t\u00eb rriten.<\/p>\n

Pjes\u00ebrisht, ky artikull m\u00eb frym\u00ebzoi ky artikull<\/a><\/noindex>, por ndoshta m\u00eb von\u00eb do ta shkruaj at\u00eb m\u00eb pak me nj\u00eb gjuh\u00eb t\u00eb till\u00eb rrethore.<\/p>\n

Vet\u00ebm p\u00ebrdoruesit e regjistruar mund t\u00eb marrin pjes\u00eb n\u00eb anket\u00eb. Hyni<\/a><\/noindex>, ju lutem.<\/p>\n

Keni hasur ndonj\u00ebher\u00eb n\u00eb pun\u00eb, kur pun\u00ebdh\u00ebn\u00ebsi p\u00ebrpiqej t\u00eb z\u00ebvend\u00ebsonte disa persona me ty?<\/h2>\n