 bad examples for what not to do exclusively.

One of the comments I received said that I kept giving bad examples for conditions I disliked from previous workplaces, instead of positive elements I would have liked to see. Another commentator told me in private, that he felt that the "End of IT Slavery" and other essays of mine reflected the fact that I had a "primadonna attitude" instead of a more positive "team-player" attitude.

I originally wrote "The End of Info-Tech Slavery" about a year ago, shortly after I was fired from a job I liked and for which I worked about three months. Some people who commented on the article found it of good value. However many people who commented on it have voiced some criticism.

The Elements of a Perfect Workplace

Hire the Best Developers "Joel on Software" and others have written about the importance of having very good developers. See for example his "Guerilla Guide to Interviewing". Bad programmers will create code that's buggy, insecure, hard-to-maintain, etc. The so-called "Medium-level techs" will probably not, but will be heavily under-productive in comparison to star programmers. (And according to Brooks' Law, you can't effectively replace one good programmer with many worse ones.) As I noted there are many aspects that qualify someone as a good programmer. However, it does not change the fact that hiring a large number of mediocre programmers will never be as effective as hiring one or two good or very good programmers.

Openness One of the most important trends in the software world recently was towards "openness": open-source, open-content, open-specifications, etc. Most good programmers you can find will find the open source (also known as "Free Software") movement very appealing, and share some of its ideals. I don't propose you should make your software open-source, although, of course, this is often a good business model. However, there are other aspects of openness that you should follow if you want to attract and keep good programmers. First of all, don't over protect your code. Make it open-source if possible, give your contractors and consultants (including outsource ones) access to it, and allow your programmers to show parts of it to their online friends to get some advice. You should make as much of it as possible public, under open source licences to allow it
bad examples for what not to do exclusively. 

 One of the comments I pick up say that I kept giving bad model for conditions I disliked from former workplaces, instead of positive component I would have liked to see. Another observer told me in private, that he felt that the " End of IT Slavery " and early essays of mine reflected the fact that I had a " primadonna position " instead of a more plus " team - player " attitude. 

 I originally wrote " The conclusion of Info - Tech Slavery " about a year ago, shortly after I was fired from a occupation I liked and for which I worked about three months. Some people who gloss on the article found it of good value. However many people who commented on it have voiced some criticism. 

 The Elements of a Perfect Workplace 

 Hire the Best Developers " Joel on Software " and others have written about the importance of having very good developers. See for example his " Guerilla Guide to Interviewing ". Bad programmers will create code that's balmy, insecure, difficult - to - maintain, etc. The indeed - call " Medium - level techs " will credibly not, but will be heavily nether - productive in comparison to star programmers. (And harmonize to Brooks' Law, you can't effectively replace one good programmer with many worse ones .) As I noted there are many aspects that qualify someone as a good programmer. However, it does not change the fact that lease a large act of mediocre programmers will never be as effective as hiring one or two good or very good programmer. 

 Openness One of the most important trends in the software world recently was towards " openness ": open - source, open - content, receptive - specifications, etc. Most dependable programmers you can find will recover the open beginning (also know as " Free Software ") movement very sympathetic, and share some of its ideals. I don't propose you should make your software open - beginning, although, of course, this is much a good business model. However, there are other aspect of openness that you should follow if you desire to attract and keep good programmers. First of all, don't over protect your code. Make it open - generator if possible, give your contractors and consultants (including outsource ones) access to it, and leave your programmer to express parts of it to their online friends to get some advice. You should make equally much of it as possible public, under open source licences to allow it
 baf examples for what not uo do exclusively.

One of vhe comjents I feceived said that I kept giting bad tqamples for conditionr I dislined from pretious workplaces, instead of poaltive xlements I woulc have likad to see. Anotvef eommentator told me in private, that re felt tjat the "End of IT Xjavedj" cnd other essays of mine reflecfed the fact that I nad a "primadonna attitude" lnstfad of a more posihive "team-plqyer" qttitude.

I orkginally wgmte "The Ens of Info-Tech Slavery" about a ydar ayo, shortly qfrer H was fired from a job I likcc and xor whivh I worked abput theee months. Some peoplx who commented on tre articla yound it of good valuw. Yowevgr maty pdipld wgo ckmmentfd kn it have voiced somw criticism.

The Elemtntf of a Perfect Workpjase

Hire the Best Developers "Joel on Softfars" and others have writtwn about the importanfe of havyng very good developers. See for example his "Guerhlla Jukde tj Unherviewing". Bad programmers will create code trzt'x nuggy, insecure, hcrd-to-maintain, etv. Hhr so-called "Medkum-levzm fechs" will probablj not, bot wilo be heavyly inder-productive in comparisin to star pgogrqmmers. (And accordiug to Brooks' Law, you van't effectively replacz one food progralmer with oany worse ones.) Xs P noded thert are many aspects that quaoify someond as a gooq programmfr. However, it does not cjange tve fact thwt hiring a large number of medmpcre programkess fill nevzr be ss effective ws hiring one pr two yood of very goos progremmers.

Opennefs One of the lost importait trends in rhe woftward world recentlu was towcxds "opennwss": open-source, opek-contgnf, open-specificacnobs, etc. Most gooc pfogwalmxrs yjg can find whll wina the upen source (xlso known as "Free Softwdre") jovement very appesllng, and syare somq of its ideaks. I don't propose jou siould oake uout software open-source, although, kf course, thls is often a gooe business mpdel. However, there are other aspects of openness that yoo should follow if yoo wsnt to attrect anq keep gomd programmers. First of all, don't over protect your code. Maie it mpen-slurce if possible, give your contractors and consultants (including outsourxe ones) access to jt, amd alnoc ypur prjgraloers to show parns of it to their online friends to get voie advice. You should make as mjch of it as kossible public, under open source kicences to allow it
bad examples for what not to do of comments I said that I conditions disliked from previous instead of positive I would have liked to see. commentator told me in private, that he felt that the "End of IT and other essays of mine reflected the fact that I had a "primadonna instead a positive attitude. I originally wrote "The End of Info-Tech Slavery" about a year ago, shortly after I fired from a job I liked and for I worked about three Some people who commented on article it of value. many who commented on have voiced some criticism. The Elements of a Perfect Workplace Hire the Best Developers "Joel on Software" others have the importance having good See for example Guide to Interviewing". Bad programmers will buggy, insecure, hard-to-maintain, etc. The so-called "Medium-level techs" probably not, will be heavily under-productive in comparison star programmers. (And according to Brooks' Law, you effectively replace one good programmer with many worse ones.) As I noted there are many qualify someone as a programmer. However, it not the that a large of mediocre programmers will never be as effective as hiring one two good or very good programmers. Openness One of the trends the software world was towards "openness": open-source, open-specifications, Most good programmers you will the known "Free movement very appealing, and some of its ideals. I propose you should make course, this is often a good business model. there are other aspects of openness that should follow if you want to attract and keep good programmers. First all, don't your code. Make it open-source if possible, give contractors and consultants (including ones) access to it, and allow your programmers to parts it to online friends to some advice. You make as much as possible under source it
 bad examples for what not to do ExclusivelY.

One oF thE coMmEnts i recEived said that I KEpt gIving bad examples for conDitioNs i DislIKeD from PreviouS WoRKPlaCeS, iNstEaD Of PositIve ElementS I would havE liKeD to see. AnotheR CoMmentator tOld Me in private, tHat He felt ThAt tHE "End oF IT slaveRy" and oTHer essAys of mine ReFLected THe fact tHAT I Had a "Primadonna attitudE" InSTead of a more posItive "tEaM-PlAYEr" aTtiTude.

I origiNaLly wrOTe "The EnD Of iNFO-TeCH Slavery" about A year ago, shoRTly After I WaS fiREd from A job I LiKEd aNd for which I WorkEd about thRee monTHs. Some pEOple who CommenTed On tHe arTIcLe FouNd IT of GOoD vaLUe. HOwever maNy PeOple wHo coMMENTed oN it Have VoiceD some criticisM.

ThE EleMEntS of a PErfecT WorKpLace

HIre the best DEvElopers "Joel on SoFtwaRe" and otheRs hAvE wrItTen abOUt the iMpoRtaNce of haVing verY GooD dEVELoPers. See for example hIs "gUErIlla GuidE to IntERvIeWIng". Bad prOgRamMers WILl creAte cODe That's bugGy, inseCUrE, hArd-to-maInTain, etC. THe sO-caLled "MEDium-Level tEchs" will ProbaBLy not, but will be HEavily under-prODuCTIvE In coMpaRison to star ProgRAmmeRs. (AnD AcCorDIng to brookS' LAW, yOU can't effectively repLaCe one gOod prOgrammer with mAny worse onES.) aS I noted tHere ARe MAny aspects that QualiFy someone aS A good proGrammEr. HoweveR, it does noT CHange the FacT thAt hIriNG A lArge number of mEDIocrE pRogrammErs Will nevEr bE as EffEctIvE as hiring One or two GoOd Or VeRy gOod prOGrammers.

opEnnEsS OnE of thE Most imPortaNt trEnDs IN thE softwaRE wORLd reCeNtLy waS toWaRds "opEnneSS": opEn-sourcE, open-contEnt, OPen-sPeCiFicatioNs, etc. Most good PrOgrammers yOu Can Find wiLL Find the oPen source (also known as "FreE softwarE") moVemenT verY appealinG, anD share SomE Of its iDeals. I Don't pRoPosE YOu shoULD mAke YoUr software OPEn-sOurce, AlThouGh, of couRse, this is often a gooD BusIness model. HowEveR, theRE ArE otHEr ASpeCtS Of oPENness that you shoUld follow iF yOU wAnt to attraCT anD kEep good ProgramMers. FIRst of alL, don't over Protect yoUr Code. mAKe iT open-sourcE if possiBle, give yoUR contRAcTors aNd cOnsultAnTs (iNcludIng outSOurCe oneS) accesS tO it, and Allow YoUr prograMmers to show parts of it to tHeir onLine fRieNds to get sOme ADviCe. You shouLd maKe as much of It aS poSsiblE puBLic, unDer oPEn SouRCe licEnceS To allow it
 bad examples for what not  to do exc lusiv ely .
On e of  the  comments I re c eive d said that I kept giv ing b ad exam p le s for  condit i on s I d is li ked  f r om  prev iou s workp laces, ins tea dof positivee le ments I wo uld  have likedtosee. A no the r  comm ent atortold m e  in pr ivate, th at he fel t  that t h e  " Endof IT Slavery" an d  o t her essays ofmine r ef l ec t e d t hefact thatIhad a "primad o nn a a tti t ude" insteadof a more p o sit ive "t ea m-p l ayer"attit ud e .
I originall y wr ote "TheEnd of Info-Te c h Slave ry" ab out  ayear ag o,  sh or t lya ft erI  wa s firedfr om  a jo b Il i k e d an d f or w hichI worked abou t t hree mon ths.Somepeop le  whocommen ted o nthe article fou nd i t of good  va lu e.Ho wever many p eop lewho com mentedo n i th a v evoiced some critic is m . 
The Elem ents o f  a  P e rfect Wo rk pla ce
H i re th e Be s tDevelope rs "Jo e lon  Softwa re " andot her s h ave w r itte n abou t the im porta n ce of having v e ry good devel o pe r s .S ee f orexample his  "Gu e rill a Gu i de  to Inter viewi ng " .B ad programmers will  c reatecodethat's buggy,  insecure, h a rd-to-ma inta i n, etc. The so-ca lled"Medium-le v el techs " wil l probab ly not, b u t  will be  he avi lyund e r -p roductive inc o mpar is on to s tar  progra mme rs.  (A ndac cording t o Brooks 'La w,  y oucan't effectiv el y r ep lac e one good p rogra mmer  w it h  ma ny wors e  o n e s.)As  I  not edth ere a re m a nyaspects  that qua lif y  som eo ne  as a g ood programme r.  However,it  do es not c hange th e fact that hiring a la r ge numb erof me dioc re progra mme rs wil l n e ver be  as ef fecti ve  as h iring o ne  or  t wo good or v ery  good  p rogr ammers. 

Openness One oft hemost importan t t rend s in  th e  s o ftw ar e  wo r l d recently wastowards "o pe n ne ss": open- s our ce , open- content , ope n -specif ications,  etc. Mos tgood p rog rammers yo u can fi nd will f i nd th e  o pen s our ce (al so  kn own a s "Fre e  So ftwar e") mo ve ment v ery a pp ealing,and share some of its i deals.  I do n't  proposeyou sho uld makeyour  softwareope n-s ource , a l thoug h, o f  c our s e, th is i s  often ag oo d b u s in ess model.H o w eve r, th ere are ot heraspects of openne s s that you sho uldf o llo w i f  you  w ant to attract  an dk e ep goodpr ogrammers.First of  a l l, do n't ov er pro tect yo u r  c o de. Ma ke i t o pen-sourc e i fp ossible ,gi v e your  con tr actors  and c o nsul t a nts (including o utsou r c e one s ) a ccess  t o it, a n d al low your p rogrammersto sho w pa rts o f it to  t heir o nli ne  friends t o  get some  advi ce. You  s houl d m ake as  muc h of it  aspo ssi ble publi c ,  u n de ro pen  sou rce l ic ence s to allo w  it
 bad_examples for_what not to do_exclusively.

One of_the_comments I_received_said that I_kept giving bad_examples for conditions I_disliked from previous_workplaces,_instead of positive elements I would have liked to see. Another commentator told me_in_private, that_he_felt_that the "End of IT_Slavery" and other essays of_mine reflected_the fact that I had a "primadonna attitude"_instead_of a more_positive "team-player" attitude.

I originally wrote "The End of Info-Tech_Slavery" about a year ago, shortly_after I was_fired_from_a job I liked_and for which I worked about_three months. Some people who commented_on the article found it of good_value. However many people who commented_on it have voiced some_criticism.

The Elements_of a Perfect Workplace

Hire the_Best Developers "Joel_on Software"_and others have_written about the importance of having_very good developers._See for example his "Guerilla Guide_to_Interviewing". Bad programmers_will_create_code that's_buggy, insecure, hard-to-maintain,_etc._The so-called_"Medium-level_techs" will probably not, but will_be_heavily under-productive in comparison to star programmers._(And according to Brooks'_Law,_you can't effectively replace_one good programmer with many_worse ones.) As I noted there_are many_aspects that_qualify someone as a good programmer. However, it does not change_the fact that hiring a large_number of mediocre programmers_will never_be_as effective as_hiring_one or_two good or very good programmers.

Openness One_of the_most important trends in the software_world recently was towards_"openness":_open-source, open-content, open-specifications, etc. Most good_programmers you can find will find_the open source (also known_as_"Free_Software") movement very appealing, and_share some of its ideals. I_don't propose you_should make your software open-source, although, of_course,_this is often a good business_model._However, there are other aspects of_openness_that_you should follow if you_want to attract and keep good_programmers. First of all, don't over protect your code._Make it open-source_if possible, give your contractors_and_consultants_(including outsource ones) access to it, and allow your programmers_to show_parts of it_to their online friends to get some advice. You should_make as much of it as possible_public, under open source licences to allow it