{"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 po humbasim pag\u00ebn dhe t\u00eb ardhmen e industris\u00eb IT","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

E keqja m\u00eb e madhe n\u00eb situat\u00ebn e sotme \u00ebsht\u00eb se IT po b\u00ebhet gradualisht nj\u00eb industri ku nuk ekziston fjal\u00eb \"ndal\" p\u00ebr numrin e p\u00ebrgjegj\u00ebsive p\u00ebr nj\u00eb person. <\/p>\n

Duke lexuar ofertat e pun\u00ebs, ndonj\u00ebher\u00eb tashm\u00eb shihni jo 2-3 persona, por nj\u00eb t\u00eb t\u00ebr\u00eb kompani n\u00eb nj\u00eb person; t\u00eb gjith\u00eb nxitojn\u00eb, borxhi teknik rritet, legjenda e vjet\u00ebr p\u00ebrball\u00eb produkteve t\u00eb reja duket si p\u00ebrkryerje, sepse t\u00eb pakt\u00ebn n\u00eb t\u00eb ka dokumentacion dhe komente n\u00eb kod, produktet e reja shkruhen me shpejt\u00ebsi drit\u00ebs, por n\u00eb fund nuk mund t\u00eb p\u00ebrdoren ende p\u00ebr nj\u00eb vit pas shkruarjes s\u00eb tyre, dhe shpesh ky vit nuk sjell fitime, p\u00ebr m\u00eb tep\u00ebr, shpenzimet p\u00ebr \"cloud\" jan\u00eb m\u00eb t\u00eb larta se shitjet e sh\u00ebrbimit. Para t\u00eb investitor\u00ebve shkojn\u00eb p\u00ebr mbajtjen e nj\u00eb sh\u00ebrbimi q\u00eb ende nuk funksionon, por q\u00eb tashm\u00eb \u00ebsht\u00eb l\u00ebshuar n\u00eb rrjet si i punuesh\u00ebm.<\/a><\/noindex>
\nSi shembull: nj\u00eb kompani e njohur, e cila remasterizoi nj\u00eb loj\u00eb t\u00eb vjet\u00ebr dhe mori vler\u00ebsimet m\u00eb t\u00eb ul\u00ebta n\u00eb histori t\u00eb industris\u00eb. Un\u00eb isha nj\u00eb nga ata q\u00eb bleva k\u00ebt\u00eb produkt, por edhe tani ky produkt funksionon keq, dhe n\u00eb teori nuk 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 banash t\u00eb p\u00ebrdoruesve n\u00eb forume p\u00ebr ankesat mbi funksionimin e sh\u00ebrbimeve. Numri i patch-eve nuk \u00ebsht\u00eb inkurajues, por trondit\u00ebs, por prap\u00eb \u2013 produkti nuk \u00ebsht\u00eb i p\u00ebrdorsh\u00ebm. N\u00ebse kjo qasje sjell k\u00ebto rezultate p\u00ebr nj\u00eb kompani q\u00eb merret me zhvillimin q\u00eb nga viti 1991, at\u00ebher\u00eb situata p\u00ebr kompanit\u00eb q\u00eb sapo kan\u00eb filluar aktivitetin e tyre \u00ebsht\u00eb edhe m\u00eb e keqe.<\/p>\n

Por k\u00ebtu kemi par\u00eb rezultatet e k\u00ebtij qasjeje nga ana e p\u00ebrdoruesit t\u00eb sh\u00ebrbimit, tani le t\u00eb shqyrtojm\u00eb problemet q\u00eb kan\u00eb dal\u00eb p\u00ebr punonj\u00ebsit. <\/p>\n

Shum\u00eb her\u00eb d\u00ebgjoj pretendimin se ekipet DevOps nuk duhet t\u00eb ekzistojn\u00eb, se \u00ebsht\u00eb nj\u00eb metodologji e till\u00eb dhe e tjera, por, e keqja \u00ebsht\u00eb, kompanit\u00eb p\u00ebr nj\u00eb arsye nuk po k\u00ebrkojn\u00eb m\u00eb nko, dba, inxhinier\u00eb infrastrukture dhe inxhinier\u00eb nd\u00ebrtimi \u2013 tani e gjith\u00eb kjo \u00ebsht\u00eb nj\u00eb inxhinier DevOps n\u00eb nj\u00eb person. Sigurisht, n\u00eb disa kompani t\u00eb ve\u00e7anta jan\u00eb akoma t\u00eb tilla vende t\u00eb pun\u00ebs, por ato po zvog\u00eblohen. Shum\u00eb e kan\u00eb quajtur k\u00ebt\u00eb zhvillim, un\u00eb personalisht n\u00eb k\u00ebt\u00eb shoh nj\u00eb degradim, \u00ebsht\u00eb e pamundur t\u00eb mbash nj\u00eb nivel t\u00eb mir\u00eb njohurie n\u00eb t\u00eb gjitha drejtimet dhe n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb t\u00eb arrish t\u00eb punosh jo m\u00eb shum\u00eb se 8 or\u00eb. Natyrisht - ato jan\u00eb fantazi. N\u00eb realitet, shum\u00eb IT-shinjt\u00eb jan\u00eb t\u00eb detyruar t\u00eb punojn\u00eb deri n\u00eb 12 dhe 14 or\u00eb, prej t\u00eb cilave paguhen vet\u00ebm 8. Dhe shpesh edhe pa fundjav\u00eb, sepse \"m\u00eb \u00ebsht\u00eb vendosur nj\u00eb detyr\u00eb, dokumentet s'jan\u00eb ekzistente ose jan\u00eb t\u00eb gabuara, m\u00eb shum\u00eb se sa kushton sh\u00ebrbimi\", dhe p\u00ebr nj\u00eb gabim n\u00eb cloud, mund t\u00eb mos marr\u00ebsh pag\u00ebn p\u00ebr disa muaj, sidomos n\u00ebse punon si IP. N\u00eb fakt, ne po humbasim fjal\u00ebn n\u00eb biznes, s\u00eb bashku me ndarjen e p\u00ebrgjegj\u00ebsive, po has m\u00eb shpesh n\u00eb at\u00eb q\u00eb menaxher\u00ebt nd\u00ebrhyjn\u00eb n\u00eb proceset e zhvillimit, pa kuptuar asgj\u00eb n\u00eb to, ata turfullin t\u00eb dh\u00ebnat e biznesit dhe pun\u00ebn e aplikacionit, dhe si rezultat fillon kaosi. <\/p>\n

Kur fillon kaosi, biznesi d\u00ebshiron t\u00eb gjej\u00eb fajtorin, dhe k\u00ebtu nevojitet nj\u00eb fajtor universall, sepse t\u00eb var\u00ebsh fajin mbi 10+ njer\u00ebz \u00ebsht\u00eb e komplikuar. Prandaj menaxher\u00ebt bashkojn\u00eb pozitat, sepse sa m\u00eb shum\u00eb p\u00ebrgjegj\u00ebsi t\u00eb ket\u00eb nj\u00eb specialist, aq m\u00eb e leht\u00eb \u00ebsht\u00eb t\u00eb provosh neglizhenc\u00ebn e tij. N\u00eb kushte Agile, gjetja e \"fajtorit\" dhe nd\u00ebshkimi jan\u00eb bazat e k\u00ebsaj metodologjie t\u00eb menaxhimit t\u00eb biznesit. Agile ka dal\u00eb prej koh\u00ebsh nga IT, dhe koncepti kryesor \u00ebsht\u00eb k\u00ebrkesa p\u00ebr rezultate t\u00eb p\u00ebrditshme. Problemi \u00ebsht\u00eb se nj\u00eb specialist i ngusht\u00ebsuar nuk do t\u00eb ket\u00eb gjithmon\u00eb rezultate t\u00eb p\u00ebrditshme, dhe kjo do t\u00eb thot\u00eb se do t\u00eb jet\u00eb m\u00eb e v\u00ebshtir\u00eb t\u00eb jap\u00ebsh llogari. Kjo \u00ebsht\u00eb nj\u00eb arsye tjet\u00ebr pse biznesi k\u00ebrkon \"specialist\u00eb n\u00eb gjith\u00e7ka\". Por arsyeja kryesore \u00ebsht\u00eb, sigurisht, FOT - ai \u00ebsht\u00eb arsyeja kryesore e t\u00eb gjitha ndryshimeve. P\u00ebr shkak t\u00eb shtesave, njer\u00ebzit kan\u00eb pranuar t\u00eb punojn\u00eb p\u00ebr veten e tyre dhe p\u00ebr t\u00eb tjer\u00ebt. Por p\u00ebrfundimisht, ashtu si n\u00eb fusha t\u00eb tjera, kjo thjesht u kthye n\u00eb nj\u00eb detyrim, p\u00ebr m\u00eb pak pages\u00eb p\u00ebr m\u00eb shum\u00eb sh\u00ebrbime t\u00eb ofruara. <\/p>\n

Sot me shpesh mund t\u00eb shohim madje artikuj q\u00eb sugjerojn\u00eb se tani zhvilluesit duhet t\u00eb din\u00eb t\u00eb realizojn\u00eb deploy, t\u00eb merren me infrastruktur\u00ebn ngjitur me inxhinier\u00ebt DevOps, por \u00e7far\u00eb rezultati sjell kjo? E sakta \u2013 r\u00ebnien e cil\u00ebsis\u00eb s\u00eb sh\u00ebrbimeve, r\u00ebnien e cil\u00ebsis\u00eb s\u00eb zhvilluesve. Para dy dit\u00ebsh, i shpjegoja nj\u00eb zhvilluesi se mund t\u00eb shkruajm\u00eb dhe lexojm\u00eb nga hoste t\u00eb ndryshme, kurse ai m\u00eb argumentonte se nuk kishte par\u00eb ndonj\u00ebher\u00eb di\u00e7ka t\u00eb till\u00eb, sepse aty ka n\u00eb settings orm host, port, db, user, password dhe asgj\u00eb m\u00eb shum\u00eb\u2026 Megjithat\u00eb, zhvilluesi dinte si t\u00eb b\u00ebnte deploy, si t\u00eb shkruante YAML\u2026 Por tashm\u00eb kishte harruar p\u00ebr testet e nj\u00ebsive dhe komentet n\u00eb kod.<\/p>\n

N\u00eb fund, ne shohim k\u00ebt\u00eb \u2013 riparime t\u00eb vazhdueshme, k\u00ebrkime zgjidhjesh p\u00ebr problemet jasht\u00eb orarit t\u00eb pun\u00ebs, m\u00ebsime t\u00eb vazhdueshme n\u00eb fundjav\u00eb, jo p\u00ebr rritjen e t\u00eb ardhurave, por p\u00ebr t\u00eb mbajtur veten n\u00eb vij\u00ebn e sip\u00ebrme. Zhvilluesit jan\u00eb t\u00eb detyruar t\u00eb ndihmojn\u00eb inxhinierin DevOps me CI\/CD, dhe n\u00ebse zhvilluesi nuk ka koh\u00eb, fillon t\u00eb mbingarkohet, dhe menaxher\u00ebt fillojn\u00eb t\u00eb krijojn\u00eb shqet\u00ebsime, e n\u00ebse kjo nuk ndihmon p\u00ebr t\u00eb rritur d\u00ebshir\u00ebn p\u00ebr t\u00eb punuar mbi orar, at\u00ebher\u00eb fillon t\u00eb aplikohen masa nd\u00ebshkuese dhe gjobat. Nj\u00eb person fillon t\u00eb k\u00ebrkoj\u00eb nj\u00eb vend t\u00eb ri pune, duke l\u00ebn\u00eb pas nj\u00eb borxhi teknik sa Everest-i, dhe si pasoj\u00eb, borxhi fillon t\u00eb rritet te zhvilluesit, pasi ata jan\u00eb t\u00eb detyruar t\u00eb shkruajn\u00eb kod me m\u00eb pak ristrukturim, p\u00ebr t\u2019u p\u00ebrballur me ndihm\u00ebn e inxhinierit t\u00eb vjet\u00ebr ose t\u00eb ri DevOps, nd\u00ebrsa menaxher\u00ebt jan\u00eb plot\u00ebsisht t\u00eb k\u00ebnaqur, sepse fajtorat jan\u00eb t\u00eb qart\u00eb dhe i shohin menj\u00ebher\u00eb; k\u00ebshtu q\u00eb rregulli kryesor n\u00eb menaxhimin Agile \u00ebsht\u00eb respektuar, fajtor\u00ebt jan\u00eb gjetur, dhe rezultatet e nd\u00ebshkimeve jan\u00eb t\u00eb dukshme. <\/p>\n

Nj\u00ebher\u00eb n\u00eb ITGM kam mbajtur nj\u00eb referat me titull \u00abkur do t\u00eb m\u00ebsojm\u00eb t\u00eb themi \u201cjo\u201d\u00bb \u2014 rezultatet ishin shum\u00eb treguese. Nj\u00eb num\u00ebr i madh njer\u00ebzish beson se kjo fjal\u00eb \u00ebsht\u00eb tabu, dhe derisa ne t\u00eb mos e ndalojm\u00eb k\u00ebt\u00eb mendim, problemet do t\u00eb vazhdojn\u00eb t\u00eb rriten.<\/p>\n

Pjes\u00ebrisht, ky artikull m\u00eb motivoi ky artikull<\/a><\/noindex>, por ndoshta m\u00eb von\u00eb do ta shkruaj at\u00eb me terma m\u00eb t\u00eb drejtp\u00ebrdrejt\u00eb.<\/p>\n

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

A keni hasur ndonj\u00ebher\u00eb n\u00eb pun\u00eb kur pun\u00ebdh\u00ebn\u00ebsi p\u00ebrpiqej t\u00eb z\u00ebvend\u00ebsonte disa njer\u00ebz me ju?<\/h2>\n