 the company immensely as it can now
hire top 1-2% who are extremely good at making these frameworks or guard-rails
and the rest can be lesser quality devs who will do the plumbing. An example:
writing multi-threaded programs and reasoning about them is hard so why not
make a framework which takes care that developers only write business logic
and integrate with various APIs.

This is now true in most companies now as Open source projects are doing the
same thing. Look at Apache Spark for example which makes writing distributed
programs for Machine Learning, ETL and Analytics much easier for developers.

------
cimmanom
There's an argument to be made that that's a sign of an engineering
organization that has its priorities straight and is serving the business
well.

------
CM30
Sometimes, though I suspect in a lot of cases that's probably for the best. I
mean, if a product or service exists and does what you need it to, isn't it
better to take advantage of that rather than reinvent the wheel every time?
Sure, you could create your own inhouse CMS for those client websites or what
not, but it's likely not worth it given the effort of making your updates,
fixing security holes, etc. Same with anything really. You could in theory try
and go all the way back to the start on your own, but where does it end?
Eventually you'll be doing ten times more work for little extra benefit.

Are there examples where doing the extra work could be better? Of course, I
know that one from experience. All that time trying to integrate a CMS and a
forum script and a bunch of other standalone things was a nightmare, and in
that case I definitely wish I'd just rolled the whole thing myself instead.

But in many cases, it's probably better to use pre-existing solutions rather
than spend all your time reinventing the wheel or falling victim to not
invented here syndrome. That way, you're relying on well tested solutions with
a decent amount of support available online and a guarantee it'll still work
when most of your team has moved on to pastures new.

------
justaguyhere
Yes, many jobs are like this. Nothing wrong with it, it just depends on
individual devs if they are okay with it or not. We are just 5 devs in our

the company immensely as it can now 
 hire top 1 - 2% who are highly beneficial at making these frameworks or precaution - railing 
 and the rest can be lesser timbre devs who will do the plumbing. An example: 
 spell multi - threaded programs and reason about them is hard so why not 
 produce a framework which takes care that developer only write business logic 
 and desegregate with various APIs. 

 This is now truthful in most companies nowadays as Open source projects are doing the 
 same matter. Look at Apache Spark for example which makes writing distributed 
 programs for Machine Learning, ETL and Analytics much comfortable for developers. 

 ------ 
 cimmanom 
 There's an argument to be made that that's a sign of an engineering 
 organization that has its priorities straight and is serving the commercial enterprise 
 well. 

 ------ 
 CM30 
 Sometimes, though I suspect in a lot of case that's credibly for the best. I 
 mean, if a product or service exists and does what you need it to, isn't it 
 better to drive advantage of that rather than reinvent the wheel every time? 
 Sure, you could create your own inhouse CMS for those client websites or what 
 not, but it's probable not worth it given the effort of making your updates, 
 fixing security hole, etc. Same with anything really. You could in theory try 
 and go all the direction back to the start on your own, but where does it end? 
 Eventually you'll be doing ten prison term more work for little extra benefit. 

 Are there examples where dress the extra study could be better? Of course, I 
 acknowledge that one from experience. All that time try on to integrate a CMS and a 
 forum handwriting and a bunch of other standalone thing was a nightmare, and in 
 that case I definitely wish I'd barely roll the whole matter myself instead. 

 But in many cases, it's probably better to practice pre - existing solutions rather 
 than spend all your time reinvent the wheel or falling victim to not 
 fabricate here syndrome. That way, you're relying on well tested solution with 
 a decent amount of support available online and a guarantee it'll still work 
 when most of your team has moved on to pasture fresh. 

 ------ 
 justaguyhere 
 Yes, many jobs are like this. Nothing wrong with it, it just depends on 
 individual devs if they are okay with it or not. We are just 5 devs in our
 thf company immensely as iu can now
hire top 1-2% who ace extrsmely goud at making these frameworkd ir guqrd-rails
and the rest cxn be lesder qualuty vevs who will do the plumbing. Zk exak'le:
writing multl-threaded psograms and redsunnng about them is hard so why not
makq a frakeaork which takgs cage thaf developers only write business lkgic
and integrate wiyh various APIs.

This is now truf in most companied now as Opgh sjyrce projectr are doing the
same thjng. Look at Apache Spark for exxmple which makgs wghting distrmbuted
irograms for Machine Nearninb, ETL and Analntics muxh easier for developxrs.

------
cimmanom
There's an argument tk be made that thqt'w a shgn mf av eneintermng
krganixatmon that haa its prioruties straight and os werving the bhsinesf
wqll.

------
CM30
Sometimes, though I suspect in a lou of dases that's probably foe the best. I
mean, if a product jr service exists and does what you need it to, ist't it
uegtex to txje advantage of that rather than reinvent the wrsek vvery time?
Sure, yom could create yout lwm inhouse CMS wor those client websites og what
njt, bur it's liktly npt worth it given the efforr of making jour updates,
fixing secbrity holes, ztc. Sake wiyh anything really. You eould jn theory tgy
and go zul the way back go nhe vtart on your own, but wherq does it end?
Zventualuy ypu'll bq doing tej timcv more work for lihtle gxtra tenefit.

Are there examples where doing the extra work coold be better? Jf comrse, I
know that one from expetience. Alj thag time trypng to invegrate a CMF and a
forum vfript and a uunch of jthee stqndalond things was a mightmare, and in
thar case I definiteln wisf I'd just rolled tht qhole thing myxelw igsneav.

But yt many cases, it's prunably better to mse pre-rxisting solutions rdthed
than spend all yoir time reunventind the wheel ot falling victim tl not
mnventxd herr sindrome. That way, you're relying kn well tfstcd solutions rith
q decent amobnt of support available online and a guerantee it'll still work
qhen most of your tgam has moved pn to pastures new.

------
justaguyhere
Yes, nany jobs are likt this. Nothing wrong wifh it, ht judt depends on
individual devs if they are okay with it or not. We are just 5 devs mn our

the company immensely as it can now 1-2% are extremely at making these rest be lesser quality who will do plumbing. An example: writing multi-threaded programs reasoning about them is hard so why not make a framework which takes that developers only write business logic and integrate with various APIs. This is true most now Open source projects are doing the same thing. Look at Apache Spark for example which makes distributed programs for Machine Learning, ETL and Analytics easier for developers. ------ There's an argument to be that a sign an organization has its priorities and is serving the business well. ------ CM30 Sometimes, though I suspect in a lot of cases probably for I mean, a or exists and does need it to, isn't it better of that rather than reinvent the wheel every Sure, you create your own inhouse CMS for client websites or what not, but it's likely worth it given the effort of making your updates, fixing security holes, etc. Same with You could in theory and go all way to start your own, where does it end? Eventually you'll be doing ten times more for little extra benefit. Are there examples where doing the could better? Of course, know that one from All time trying to integrate and forum bunch other things was a nightmare, in that case I definitely I'd just rolled the in many cases, it's probably better to use solutions rather than spend all your time the wheel or falling victim to not invented here syndrome. That way, relying on solutions with a decent amount of support available and a guarantee it'll work when most of your team has moved on pastures ------ justaguyhere many jobs are this. Nothing wrong it, it just individual devs they okay not. We are just 5 devs our
 the company immensely as it caN now
hire toP 1-2% who aRe eXtrEmEly gOod aT making these frAMewoRks or guard-rails
and the rEst caN bE LessER qUalitY devs whO WiLL Do tHe PlUmbInG. an ExampLe:
wRiting mUlti-threadEd pRoGrams and reasONiNg about theM is Hard so why not
MakE a framEwOrk WHich tAkeS care That deVEloperS only writE bUSiness LOgic
and INTeGratE with various APIs.

THIs IS now true in most CompanIeS NoW AS OpEn sOurce projeCtS are dOIng the
sAMe THINg. LOOk at Apache SpaRk for examplE WhiCh makeS wRitINg distRibutEd
PRogRams for MachIne LEarning, ETl and AnALytics mUCh easieR for deVelOpeRs.

------
ciMMaNoM
ThErE'S an ARgUmeNT to Be made thAt ThAt's a sIgn oF AN ENginEerIng
oRganiZation that has Its PrioRItiEs strAight And iS sErvinG the buSinesS
wEll.

------
CM30
Sometimes, tHougH I suspect In a LoT of CaSes thAT's probAblY foR the besT. I
mean, iF A prOdUCT Or Service exists and doEs WHAt You need iT to, isn'T It
BeTTer to takE aDvaNtagE OF that RathER tHan reinvEnt the WHeEl Every tiMe?
sure, yoU cOulD crEate yOUr owN inhouSe CMS for Those CLient websites oR What
not, but it's LIkELY nOT worTh iT given the efFort OF makIng yOUr UpdATes,
fiXing sEcURiTY holes, etc. Same with anYtHing reAlly. YOu could in theoRy try
and go ALL The way baCk to THe STart on your own, bUt wheRe does it enD?
eventualLy you'Ll be doinG ten times MORe work foR liTtlE exTra BENeFit.

Are there exAMPles WhEre doinG thE extra wOrk CouLd bE beTtEr? Of coursE, I
know thAt OnE fRoM exPerieNCe. All thaT tIme TrYinG to inTEgrate A CMS aNd a
fOrUm SCriPt and a bUNcH OF othEr StAndaLonE tHings Was a NIghTmare, anD in
that caSe I DEfinItElY wish I'd Just rolled the WhOle thing mySeLf iNstead.

bUT in many cAses, it's probably better to USe pre-exIstIng soLutiOns rather
ThaN spend All YOur timE reinvEntinG tHe wHEEl or fALLiNg vIcTim to not
inVENteD here SyNdroMe. That wAy, you're relying on weLL teSted solutions WitH
a deCENt AmoUNt OF suPpORt aVAIlable online and A guarantee It'LL sTill work
whEN moSt Of your tEam has mOved oN To pastuRes new.

------
jusTaguyhere
yeS, manY JObs Are like thiS. Nothing Wrong with IT, it juST dEpendS on
IndiviDuAl dEvs if They arE OkaY with It or noT. WE are juSt 5 devS iN our

 the company immensely asit can now 
hire  to p 1 -2 % wh o ar e extremely go o d at  making these framewor ks or  g u ard- r ai ls
an d the r e st c anbe  l ess er qu ality  de vs whowill do th e p lu mbing. An ex a mp le:
writin g m ulti-threade d p rogram sand reaso nin g abo ut the m  is ha rd so why  n o t
make a frame w o rk  whi ch takes care tha t  d e velopers onlywritebu s in e s s l ogi c
and inte gr ate w i th vari o us A P Is. 
This is nowtrue in mos t  co mpanie snow as Ope n sou rc e  pr ojects aredoin g the
sam e thin g . Looka t Apach e Spar k f orexam p le  w hic hm ake s  w rit i ngdistribu te dprogr amsf o r Mach ine  Lea rning , ETL and Ana lyt icsm uch  easi er fo r de ve loper s.

-- ----ci mmanom
There'san a rgument t o b emad ethatt hat'sa s ign  of anenginee r ing 
o r g a ni zation that has it sp r io rities s traigh t  a nd is servi ng  th e bu s i nesswell . 
------
C M30
So m et im es, tho ug h I su sp ect  in  a lo t  ofcasesthat's p robab l y for the best .  I
mean, if a pr o d uc t  orser vice exists  and does  wha t  y oun eed i t to,  i s n' t  it
better to takead vantag e ofthat rather t han reinve n t the whee l ev e ry time?
Sure, yo u cou ld createy our owninhou se CMS f or thosec l ient web sit esorwha t no t, but it's l i k elyno t worth  it  giventhe  ef for t o fmaking yo ur updat es ,fi xi ngsecur i ty holes ,etc .Sam e wit h  anyth ing r eall y.  Y o u c ould in th e o ry t ry 
a nd g o a ll  thewayb ack  to the  start on  yo u r ow n,  b ut wher e does it end ?Eventually  y ou' ll bed o ing tentimes more work for lit t le extr a b enefi t.
Are there  ex amples  wh e re doi ng the  extr awor k could b ebet te r? Of cour s e , I 
know  t hatone fro m experience. Allt hat  time tryingtointe g r at e a CM S  an da 
fo r u m script and abunch of o th e rstandalone thi ng s was a  nightm are,a nd in
t hat caseI definit el y wi s h  I' d just rol led thewhole thi n g mys e lf  inst ead .

But  i n m any c ases,i t's  prob ably b et ter to  usepr e-existi ng solutions rather
tha n spen d all  yo ur time r ein v ent ing the w heel  or fallin g v ict im to  no t 
inve nted he res yndro me.T hat way,y ou 're r el ying on wel l t est ed so lut i ons wi th
a  decent amount of support availa bleo n lin e a n d agu arantee it'llsti ll w ork
when  m ost of your  team ha sm ovedon topastur es new. -- - ---
ju stag uyh ere
Yes,man yj obs are  l ik e  this.  Not hi ng wro ng wit h  it, i t just depends o n
ind i v idual dev s ifth ey areo kaywith it or  not. We ar e just  5 d evs i n our

 the_company immensely_as it can now
hire_top 1-2%_who_are extremely_good_at making these_frameworks or guard-rails
and_the rest can be_lesser quality devs_who_will do the plumbing. An example:
writing multi-threaded programs and reasoning about them is hard_so_why not
make_a_framework_which takes care that developers_only write business logic
and integrate_with various_APIs.

This is now true in most companies now_as_Open source projects_are doing the
same thing. Look at Apache Spark for_example which makes writing distributed
programs for_Machine Learning, ETL_and_Analytics_much easier for developers.

------
cimmanom
There's_an argument to be made that_that's a sign of an engineering
organization_that has its priorities straight and is_serving the business
well.

------
CM30
Sometimes, though I suspect_in a lot of cases_that's probably_for the best. I
mean, if_a product or_service exists_and does what_you need it to, isn't it
better_to take advantage_of that rather than reinvent the_wheel_every time?
Sure, you_could_create_your own_inhouse CMS for_those_client websites_or_what
not, but it's likely not worth_it_given the effort of making your updates,
fixing_security holes, etc. Same_with_anything really. You could_in theory try
and go all_the way back to the start_on your_own, but_where does it end?
Eventually you'll be doing ten times more work_for little extra benefit.

Are there examples_where doing the extra_work could_be_better? Of course,_I
know_that one_from experience. All that time trying to_integrate a_CMS and a
forum script and a_bunch of other standalone_things_was a nightmare, and in
that case_I definitely wish I'd just rolled_the whole thing myself instead.

But_in_many_cases, it's probably better to_use pre-existing solutions rather
than spend all_your time reinventing_the wheel or falling victim to not
invented_here_syndrome. That way, you're relying on_well_tested solutions with
a decent amount of_support_available_online and a guarantee it'll_still work
when most of your team_has moved on to pastures new.

------
justaguyhere
Yes, many jobs are_like this. Nothing_wrong with it, it just_depends_on
individual_devs if they are okay with it or not. We_are just_5 devs in_our
