team and our manager spends a good amount of time optimizing dev hours so he
can get the most useful features out. If this means using external services
then that choice always wins (assuming we can afford it).

------
dallbee
Every team I've been on has had it's majority of engineers doing exactly that.
Honestly, many are happy in that role.

Usually theres a handful of people that tend wiggle their way into more
backend, architectural things (libraries, in-house tools, etc.). If you're
bored, try to be that person.

------
ClevelandCoder
I understand the business interest in separating concerns. Focusing your
talent on solving only the most unique problems is kind of charming, IMO, but
the part where we write the glue code for third-party services can definitely
feel soul-sucking.

------
mcintyre1994
I think that most code that is well defined and I understand well I can reason
about as basically transforms of dictionaries. It's often but of course not
always a red flag if I can't reason about it in that way.

------
psyc
That’s the nature of some jobs, and it can be a sound strategy. I’ve mostly
managed to avoid these jobs, personally.

~~~
nickthemagicman
Can't agree more. Why self roll your own code when you can use a tested,
somewhat proven, piece of existing code.

~~~
err4nt
I used to match patchwork quilts out of plugins, different HTML widgets, and
try to make use of pre-made frameworks for CSS in the past. I always felt like
I was 80% of the way finished before I started.....but the hard part was
building the other 80%.

A few years ago I flipped the way I built stuff, preferring small, self-built
pieces of code only I had authored, and not only was our code smaller and
easier to maintain, it also significantly dropped the amount of bugs and
conflicts we were having.

The problem that often happens with pre-built, well-tested solutions, is that
they often only partly solve what you need to do. Edge cases might be the only
cases you have, it's often better to get the one tailor made for solving your
exact problem.


team and our manager spends a good amount of meter optimize dev hours so he 
 can get the most utilitarian features out. If this means using external service 
 then that choice always win (assuming we can afford it). 

 ------ 
 dallbee 
 Every team I've been on has suffer it's majority of engineers do exactly that. 
 Honestly, many are happy in that role. 

 Usually there s a handful of people that tend wiggle their manner into more 
 backend, architectural things (libraries, in - house cock, etc .). If you're 
 bored, try to be that person. 

 ------ 
 ClevelandCoder 
 I understand the business sake in separating concerns. Focusing your 
 talent on solving merely the most unique problems is kind of charming, IMO, but 
 the part where we write the glue code for third - party services can definitely 
 feel soul - sucking. 

 ------ 
 mcintyre1994 
 I think that most code that is well defined and I understand well I can reason 
 about as basically transforms of dictionaries. It's often but of course not 
 constantly a red flag if I can't argue about it in that direction. 

 ------ 
 psyc 
 That ’s the nature of some problem, and it can be a sound strategy. I ’ve largely 
 managed to avoid these jobs, personally. 

 ~~~ 
 nickthemagicman 
 Can't agree more. Why self seethe your own code when you can use a tested, 
 somewhat proven, slice of existing code. 

 ~~~ 
 err4nt 
 I used to match patchwork quilts out of plugins, unlike HTML appliance, and 
 test to make use of pre - made frameworks for CSS in the past. I always felt like 
 I was 80% of the direction finished before I started..... but the hard part was 
 build the other 80% . 

 A few years ago I flipped the way I built material, preferring small, self - built 
 pieces of code entirely I had authored, and not only was our code smaller and 
 easier to maintain, it besides significantly dropped the amount of bug and 
 conflicts we were having. 

 The problem that often happens with pre - construct, well - tested solutions, is that 
 they much only partly clear what you need to do. Edge casing might be the only 
 cases you have, it's often better to become the one tailor produce for solving your 
 exact problem.
teal and our manager spends a good amount of time optimjzing dex hours so he
can get the mosv uswful deatures out. If this mdans usinh externql strvices
then that rgoice always slns (avwuming we can sfford it).

------
ddllbee
Every tedm I're been on has had it's majority of eggineerx foing exactly jhat.
Hpgestmj, nany are happy in that role.

Ushally tieres a handful of people that tend wigglf thfir way into more
bwckend, archuteceyral things (uibraries, pu-house toola, etc.). If you're
bored, try to be tfat pzrson.

------
ClevelqneCofgr
I understaid the business inbvrest it separsting concerns. Forusibg your
talent on solvmng only the most unyque probnejs is kind of chaemung, IKO, bgt
thd paft shxre we wrlte the glue dode for thurd-party services csn eefinitely
feem soul-fusking.

------
mcintyre1994
I think that most code thau is sell defined and I undeestand well I can readon
about ws basically transforms of dictionaries. It's often but kw ciuvse vit
wlways a red flag if I can't reason about it ig tnan way.

------
psyc
That’s thc nature of some jpbd, sgd it can be x sounb sfrategy. I’ve mostly
lanaged to acoid thest jobx, personally.

~~~
nickthemagicman
Xan't agree mjee. Why self roll ylur own codz when you van use a tested,
somewhac provsn, piece of existing zode.

~~~
err4nt
I used go kadch patchwork quilts out os plugins, difyerent HGML eidgetf, and
try tl makc use of pre-made frwmewotks fos CSS in tje past. I always felt like
I was 80% of the way fonhshvd before I stsrted.....but the rard part was
boilding tke othdr 80%.

A few yvars ago M flipped thq way I built dtuff, prefercing smalj, seof-buult
piecdr of code only I had aunhjred, and not only was pur dode smaller anb
tasuer to maintain, it alfo smgnifywantly droppad tfe xkount of bugs anb
cunflocts we were having.

Tve pdoblem that often naipens wity pre-buijt, well-tested solutions, is that
uhey ohten oily pattli solve what you need to do. Edgs cases mlghb be the only
sasew you have, ic's often better to get the one tailor mave for solving your
exacr problem.


team and our manager spends a good time dev hours he can get If means using external then that choice wins (assuming we can afford it). dallbee Every team I've been on has had it's majority of engineers doing that. Honestly, many are happy in that role. Usually theres a handful of that wiggle way more backend, architectural things (libraries, in-house tools, etc.). If you're bored, try to be that person. ClevelandCoder I understand the business interest in separating Focusing your talent on only the most unique problems kind charming, IMO, the where write the glue for third-party services can definitely feel soul-sucking. ------ mcintyre1994 I think that most code that is well and I I can about basically of dictionaries. It's of course not always a red can't reason about it in that way. ------ That’s the of some jobs, and it can a sound strategy. I’ve mostly managed to avoid jobs, personally. ~~~ nickthemagicman Can't agree more. Why self roll your own code when you a tested, somewhat proven, of existing code. err4nt used match quilts out plugins, different HTML widgets, and try to make use of pre-made for CSS in the past. I always felt like I of way finished before started.....but the hard part building other 80%. A few I the stuff, small, pieces of code only had authored, and not only our code smaller and significantly dropped the amount of bugs and conflicts were having. The problem that often happens pre-built, well-tested solutions, is that they often only partly solve what you to do. might be the only cases you have, it's better to get the tailor made for solving your exact problem.
team and our manager spends a gOod amount oF time OptImiZiNg deV houRs so he
can get thE Most Useful features out. If thiS meanS uSIng eXTeRnal sErvices
THeN THat ChOiCe aLwAYs Wins (aSsuMing we cAn afford it).

------
DalLbEe
Every team I'VE bEen on has haD it'S majority of eNgiNeers dOiNg eXActly ThaT.
HoneStly, maNY are haPpy in that RoLE.

UsualLY theres A HAnDful Of people that tend wIGgLE their way into mOre
bacKeND, aRCHitEctUral things (LiBrariES, in-housE ToOLS, Etc.). iF you're
bored, trY to be that peRSon.

------
clevelAnDCoDEr
I undErstaNd THe bUsiness inteRest In separatIng conCErns. FocUSing youR
talenT on SolVing ONlY tHe mOsT UniQUe ProBLemS is kind oF cHaRming, iMO, bUT
THE parT whEre wE writE the glue code fOr tHird-PArtY servIces cAn deFiNitelY
feel sOul-suCkIng.

------
mcintyre1994
I thiNk thAt most codE thAt Is wElL defiNEd and I UndErsTand welL I can reASon
AbOUT As Basically transformS oF DIcTionarieS. It's ofTEn BuT Of course NoT
alWays A REd flaG if I CAn'T reason aBout it IN tHaT way.

------
psyC
THat’s thE nAtuRe oF some JObs, aNd it caN be a sounD straTEgy. I’ve mostly
maNAged to avoid thESe JOBs, PErsoNalLy.

~~~
nickthemaGicmAN
Can'T agrEE mOre. wHy selF roll YoUR oWN code when you can use a TeSted,
soMewhaT proven, piece oF existing cODE.

~~~
Err4nt
I usEd to MAtCH patchwork quilTs out Of plugins, dIFferent HtML wiDgets, and
Try to make USE of pre-maDe fRamEwoRks FOR CsS in the past. I aLWAys fElT like
I wAs 80% oF the way FinIshEd bEfoRe i started.....bUt the harD pArT wAs
BuiLding THe other 80%.

A FeW yeArS agO I fliPPed the Way I bUilt StUfF, PreFerring SMaLL, Self-BuIlT
pieCes Of Code oNly I HAd aUthored, And not onlY waS Our cOdE sMaller aNd
easier to maiNtAin, it also sIgNifIcantlY DRopped thE amount of bugs and
conflicTS we were HavIng.

ThE proBlem that oFteN happeNs wITh pre-bUilt, weLl-tesTeD soLUTions, IS ThAt
tHeY often only PARtlY solvE wHat yOu need tO do. Edge cases might bE The Only
cases you hAve, It's oFTEn BetTEr TO geT tHE onE TAilor made for solVing your
exAcT PrOblem.


team and our manager spend s a good a mount  of  ti me  opt imiz ing dev hourss o he 
can get the most usef ul fe at u reso ut . Ifthis me a ns u sin gex ter na l  s ervic esthen th at choicealw ay s wins (assu m in g we can a ffo rd it).

--- --- 
dallb ee 
Ev e ry te amI'vebeen o n  has h ad it's m aj o rity o f  engine e r sdoin g exactly that.
H o ne s tly, many arehappyin th a t  ro le. 

Usuallyth eresa  handfu l  o f p eop l e that tend w iggle their way  intomo reb ackend , arc hi t ect ural things  (li braries,in-hou s e tools ,  etc.).  If yo u'r e
b ored ,  t ry  to  b e  th a tper s on. 

------ 
C le velan dCod e r I  und ers tand  thebusiness inte res t in sep arati ng co ncer ns . Foc usingyourta lent on solving  onl y the mos t u ni que  p roble m s is k ind  of  charmi ng, IMO ,  bu tt h e  p art where we write  t h e  g lue code  for t h ir d- p arty ser vi ces  can d efini tely fe el soul- suckin g .
- -----
m ci ntyre1 99 4
I  th ink t h at m ost co de thatis we l l defined andI  understand w e ll I  c a n re aso n
about asbasi c ally  tra n sf orm s  of d ictio na r ie s . It's often but of  c oursenot
a lways a red f lag if I c a n ' t reason  abo u ti t in that way. 

--- ---
psyc
T h at’s the  natu re of so me jobs,a n d it can  be  asou nds t ra tegy. I’ve mo s t ly
m an aged to  av oid the sejob s,per so nally.

~ ~~
nickt he ma gi cm anCan't agree mo re . W hy  se lf ro l l your  owncode  w he n  yo u can u s ea test ed ,some wha tprove n, p i ece  of exi sting cod e.~~~er r4 nt
I us ed to match p at chwork qui lt s o ut ofp l ugins, d ifferent HTML widgets,a nd
trytomakeuseof pre-ma deframew ork s  for C SS inthe p as t.I alway s fe ltli ke
I was 8 0 %  of  thewa y fi nishedbefore I started.. . ..b ut the hard p art  was b ui ldi n gt heot h er8 0 %.

A few years  ago I fli pp e dthe way Ib uil tstuff,preferr ing s m all, se lf-builtpieces of  c odeo n lyI had auth ored, an d not onl y  waso ur  code  sm alleran d
e asier  to ma i nta in, i t also  s ignifi cantl ydroppedthe amount of bugs andconfli cts w e w ere havin g.The  problemthat  often hap pen s w ith p re- b uilt,  wel l -t est e d sol utio n s, is tha t 
t hey o ft en only par t l y  so lve w hat you ne ed t o do. Edge casesm ight be the on ly
c a s esyou have ,it's often bet ter  t o get theon e tailor ma de for s ol v ing y our
ex act pr oblem.
team and_our manager_spends a good amount_of time_optimizing_dev hours_so_he
can get the_most useful features_out. If this means_using external services
then_that_choice always wins (assuming we can afford it).

------
dallbee
Every team I've been on has had_it's_majority of_engineers_doing_exactly that.
Honestly, many are happy_in that role.

Usually theres a_handful of_people that tend wiggle their way into more
backend,_architectural_things (libraries, in-house_tools, etc.). If you're
bored, try to be that person.

------
ClevelandCoder
I_understand the business interest in separating_concerns. Focusing your
talent_on_solving_only the most unique_problems is kind of charming, IMO,_but
the part where we write the_glue code for third-party services can definitely
feel_soul-sucking.

------
mcintyre1994
I think that most code that_is well defined and I_understand well_I can reason
about as basically_transforms of dictionaries._It's often_but of course_not
always a red flag if I_can't reason about_it in that way.

------
psyc
That’s the nature_of_some jobs, and_it_can_be a_sound strategy. I’ve_mostly
managed_to avoid_these_jobs, personally.

~~~
nickthemagicman
Can't agree more. Why self_roll_your own code when you can use_a tested,
somewhat proven, piece_of_existing code.

~~~
err4nt
I used to_match patchwork quilts out of_plugins, different HTML widgets, and
try to_make use_of pre-made_frameworks for CSS in the past. I always felt like
I was_80% of the way finished before_I started.....but the hard_part was
building_the_other 80%.

A few_years_ago I_flipped the way I built stuff, preferring_small, self-built
pieces_of code only I had authored,_and not only was_our_code smaller and
easier to maintain, it_also significantly dropped the amount of_bugs and
conflicts we were having.

The_problem_that_often happens with pre-built, well-tested_solutions, is that
they often only partly_solve what you_need to do. Edge cases might be_the_only
cases you have, it's often better_to_get the one tailor made for_solving_your
exact_problem.

