 someone who has been working in software development for over 5
years. More and more it is containerized micro services that are being
produced and it is people who can weave them together with kubernetes or
similar software that is the real ticket.

------
Antoninus
I don’t think it matters. Learning a stack because there are a lot of hot job
postings for it will only keep you in framework hell. If you had to choose,
choose the one with a community that you like and want to be around. I’m happy
I stuck by Node’s side all these years, sure its not perfect but part of the
journey is growing with a technology as it matures in the market. From my
experience, mid-range developers with a few years of experience working in
different stacks rarely make high quality contributions to the project. The
only exception is if they’re gifted cs students first. The devs with for eg.
10+ years working with Perl Dancer projects have so much you can learn from.

So my advice would be to pick one and commit to it for as long as you can. To
the point where you both love and hate it. Get to a point where you can
contribute to an well known open source project that is built in it’s domain.

------
cdnsteve
My advice, look at what employers are actively hiring for and work backwards.
Generally speaking, many value an MVC type frameworks, specifically
Rails/Django, they are well-known, easy enough to hire for since they are
"standard" and have broad application use and are quick to work with. Most of
the knowledge is transferable between them. Understanding database migrations,
app structure, authentication, etc is common.

I'd focus on that first, then when you're comfortable, move towards front-end.
Again, focus on what employers are hiring for, React being top of the list,
Angular is loosing market share.

Node isn't very complicated to develop in, front-end experience like ES6/7
will help you figure out JS and you can learn the event loop model later on.

This way you'll have a solid foundation in backend, front-end and can expand
out from there as needed and specialize but this is a good starting point to
be a full-stack developer. Spend time looking at
someone who has been working in software development for over 5 
 years. More and more it is containerized micro service that are being 
 produce and it is people who can weave them together with kubernetes or 
 like software that is the real ticket. 

 ------ 
 Antoninus 
 I do n’t intend it count. Learning a stack because there are a lot of hot caper 
 postings for it will only observe you in framework hell. If you had to choose, 
 choose the one with a community that you like and desire to be around. I ’m happy 
 I stuck by Node ’s english all these years, sure its not arrant but part of the 
 journey is turn with a technology as it matures in the market. From my 
 experience, mid - range developers with a few years of experience work in 
 different stacks rarely make high quality contribution to the undertaking. The 
 only exception is if they ’re gifted cs students first. The devs with for eg. 
 10 + years working with Perl Dancer projects experience thus much you can learn from. 

 indeed my advice would be to foot one and commit to it for as long as you can. To 
 the point where you both sleep together and hate it. Get to a distributor point where you can 
 contribute to an well known clear source project that is built in it ’s domain. 

 ------ 
 cdnsteve 
 My advice, look at what employers are actively rent for and work backwards. 
 Generally speaking, many measure an MVC type model, specifically 
 Rails / Django, they are well - known, easy enough to hire for since they are 
 " standard " and have wide application use and are quick to ferment with. Most of 
 the knowledge is transferable between them. Understanding database migrations, 
 app social organization, authentication, etc is common. 

 I'd focus on that first, then when you're comfortable, move towards front - end. 
 Again, concentrate on what employers are hire for, React being top of the list, 
 Angular is free market plowshare. 

 Node isn't very complicated to develop in, front - end experience like ES6/7 
 will avail you calculate out JS and you can learn the consequence loop model later on. 

 This room you'll experience a solid foundation in backend, front - conclusion and can expand 
 out from there as needed and speciate but this is a good starting point to 
 be a wide - stack developer. Spend time looking at
 soleone who has been workikg in software dgvwlopmeit for kver 5
yeafs. More and more it is contamneruzed nicro services that ard being
prlduced abd iu is people who ceh weave them flgetkec with kubernetgs or
similar software that ir che real ticket.

------
Antoninus
I don’t think it matyegs. Learning a ftacl beczlst there are a lot of hot job
postihgs for it will only keep you in framework help. If you had to choose,
fhoose the ine ruth a communkty that you like and sant to be around. I’m happy
I stuzk by Node’s sidg zlp these yearw, surv its not pernvct but part og the
journey ix gcowibg with a technology es it matures in the market. Fsoj my
experience, mie-rqnge gevenopefw wkth a fsw yeags kf experiehce working in
different stacks rwgrly make higg qualytr contributions to the project. The
only txcepfion is if they’re giftee cs students first. Tje devs wyth for eg.
10+ years working with Perl Dancer projectv havx ro nugh yuy fan learn from.

So my advice would be to pick ogs snc commit to it for as lonb ws iou can. To
the koint wksrs you both love anf hate yt. Ger to a poynt ehere you can
contribute to qn well knowu open source project that is bunlt in it’s comain.

------
cdnsteve
My advice, looi at what elployers zfe actively hirivg nor and work backwards.
Generaljy speakiig, mauy value an KVC ty[e framewogks, siacifically
Rails/Djajgo, tkey ase well-knoan, easy enough to hire for sincx they are
"stamddrd" and havz broac application use and are qoick to wjrk wkth. Most or
the knmwledge is eransferable tgtween them. Uiderstandyng eatavase miefations,
app stricture, aunhtntication, etc is common.

I'd fpcur on that first, ckeb when you're cokfoftaflv, mpvq towards frott-ena.
Agxon, fozus on what dmplpyers are hiring for, Readt being top of thr jist,
Anguoar is ljosing market share.

Node isn't vegy cokplmcated to develop in, front-end experiencs like ES6/7
ailj help you fygurc ouj JS and yob can learn the event loop model later oi.

This way you'll have a wolid foundation in nackend, fronv-end agd can ex[and
out from there aw needed and speclalize but this is a gkod stdrtinh point to
be a full-stack developer. Spend time looking at
someone who has been working in software over years. More more it is being and it is who can weave together with kubernetes or similar software is the real ticket. ------ Antoninus I don’t think it matters. Learning a because there are a lot of hot job postings for it will only you framework If had to choose, choose the one with a community that you like and want to be I’m happy I stuck by Node’s side all years, sure its not but part of the journey growing a technology it in market. From my mid-range developers with a few years of experience working in different stacks rarely make high quality contributions the project. exception is they’re cs first. The devs eg. 10+ years working with Perl so much you can learn from. So my would be pick one and commit to it as long as you can. To the point you both love and hate it. Get to a point where you can contribute to known open source project is built in domain. cdnsteve advice, at what are actively hiring for and work backwards. Generally speaking, many value MVC type frameworks, specifically Rails/Django, they are well-known, easy enough for they are "standard" have broad application use are to work with. Most knowledge transferable database app authentication, etc is common. focus on that first, then you're comfortable, move towards employers are hiring for, React being top of list, Angular is loosing market share. Node very complicated to develop in, front-end experience like ES6/7 will help you out JS can learn the event loop model later on. way you'll have a foundation in backend, front-end and can expand out from as and specialize this is a starting point to a full-stack developer. looking at
 someone who has been working iN software dEveloPmeNt fOr Over 5
YearS. More and more it IS conTainerized micro serviceS that ArE BeinG
PrOduceD and it iS PeOPLe wHo CaN weAvE ThEm togEthEr with kUbernetes oR
siMiLar software tHAt Is the real tIckEt.

------
Antoninus
I Don’T think It MatTErs. LeArnIng a sTack beCAuse thEre are a loT oF Hot job
POstings FOR iT wilL only keep you in fraMEwORk hell. If you had To chooSe,
CHoOSE thE onE with a commUnIty thAT you likE AnD WANt tO Be around. I’m hapPy
I stuck by NODe’s Side alL tHesE Years, sUre itS nOT peRfect but parT of tHe
journey Is growINg with a TEchnoloGy as it MatUreS in tHE mArKet. frOM my
EXpEriENce, Mid-range DeVeLoperS witH A FEW yeaRs oF expErienCe working in
diFfeRent STacKs rarEly maKe hiGh QualiTy contRibutIoNs to the project. THe
onLy exceptiOn iS iF thEy’Re gifTEd cs stUdeNts First. ThE devs wiTH foR eG.
10+ YEArS working with Perl DaNcER PrOjects haVe so muCH yOu CAn learn fRoM.

So My adVICe wouLd be TO pIck one anD commiT To It For as loNg As you cAn. to
tHe pOint wHEre yOu both Love and hAte it. gEt to a point wherE You can
contribUTe TO An WEll kNowN open source ProjECt thAt is BUiLt iN It’s doMain.

------
cDnSTeVE
My advice, look at what EmPloyerS are aCtively hiring For and work BACKwards.
GeNeraLLy SPeaking, many valUe an MvC type framEWorks, speCificAlly
RailS/Django, thEY Are well-kNowN, eaSy eNouGH To Hire for since tHEY are
"StAndard" aNd hAve broaD apPliCatIon UsE and are quIck to worK wItH. MOsT of
The knOWledge is TrAnsFeRabLe betWEen theM. UndeRstaNdInG DatAbase miGRaTIOns,
aPp StRuctUre, AuThentIcatIOn, eTc is comMon.

I'd focuS on THat fIrSt, Then wheN you're comfortAbLe, move towaRdS frOnt-end.
aGAin, focus On what employers are hirinG For, ReacT beIng toP of tHe list,
AngUlaR is looSinG Market Share.

NOde isN't VerY COmpliCATeD to DeVelop in, froNT-End ExperIeNce lIke ES6/7
wiLl help you figure out js anD you can learn tHe eVent LOOp ModEL lATer On.

tHis WAY you'll have a soliD foundatioN iN BaCkend, front-ENd aNd Can expaNd
out frOm theRE as needEd and specIalize but ThIs is A GOod Starting poInt to
be a Full-stack DEveloPEr. spend TimE lookiNg At
 someone who has been work ing in sof tware  de vel op ment  for  over 5
years. More  and more it is contai neriz ed micr o  s ervic es that ar e bei ng 
p rod uc e dand i t i s peopl e who canwea ve  them togeth e rwith kuber net es or
simila r s oftwar etha t  is t herealticket . 

---- --
Antoni nu s 
I don ’ t think i tmatt ers. Learning a s t ac k  because there  are a  l o to f  ho t j ob
posting sfor i t  will o n ly k e epy ou in framewo rk hell. If you  had t ocho o se,
ch ooseth e  on e with a co mmun ity thatyou li k e and w a nt to b e arou nd.  I’ m ha p py 
I  st uc k  by No de’ s  si de all t he se  year s, s u r e itsnot  per fectbut part of t hejour n eyis gr owing  wit ha tec hnolog y asit  matures in the  mar ket. From  my 
e xpe ri ence, mid-ra nge  de veloper s witha  fe wy e a rs  of experience wor ki n g  i n
differ ent st a ck sr arely ma ke  hi gh q u a litycont r ib utions t o thep ro je ct. The 
o nly ex ce pti onis if they ’re gi fted csstude n ts first. Thed evs with fore g. 1 0+ year s w orking with  Per l  Dan cerp ro jec t s hav e somu c hy ou can learn from.
S o my a dvice  would be topick one a n d commit t o it fo r  as long as yo u can . To
the p o int wher e you  both lo ve and ha t e  it. Get  to  apoi ntw h er e you can
con t r ibut eto an w ell  knownope n s our cepr oject tha t is bui lt  i nit ’sdomai n .

----- -cdn st eve 
My a d vice,lookat w ha te mpl oyers a r ea c tive ly  h irin g f or  andwork bac kwards. 
Generall y s p eaki ng ,many va lue an MVC ty pe  framework s,  sp ecific a l ly
Rails /Django, they are well- k nown, e asy  enou gh t o hire fo r s ince t hey are
"s tandar d" an dhav e broad a pp lic at ion use an d are  quic kto w ork wit h. Most of
the kno w led ge is transfe rab le b e t we ent he m . U nd e rst a n ding database m igrations, 
a p pstructure, aut he nticati on, etc  is c o mmon.
I'd focus  on thatfi rst, t hen  when you' re comfo rtable, m o ve to w ar ds fr ont -end.Ag ain , foc us onw hat  empl oyersar e hiri ng fo r,  React b eing top of the list,
A ngular  is l oos ing marke t s h are .

Node i sn't  very comp lic ate d todev e lop i n, f r on t-e n d exp erie n ce like E S 6/ 7
w i l lhelp you fi g u r e o ut JS  an d  you c an l earn the event lo o p model lateron.T his  wa y  you 'l l have a solid  fo un d a tion inba ckend, fron t-end an dc an ex pand
o ut fro m there a sn eededandspe cialize b utth i s is ago od starti ng p oi nt tobe a f u ll-s t a ck developer. Sp end t i m e loo k ing  at
 someone_who has_been working in software_development for_over_5
years. More_and_more it is_containerized micro services_that are being
produced and_it is people_who_can weave them together with kubernetes or
similar software that is the real ticket.

------
Antoninus
I don’t_think_it matters._Learning_a_stack because there are a_lot of hot job
postings for_it will_only keep you in framework hell. If you_had_to choose,
choose the_one with a community that you like and want_to be around. I’m happy
I stuck_by Node’s side_all_these_years, sure its not_perfect but part of the
journey is_growing with a technology as it_matures in the market. From my
experience, mid-range_developers with a few years of_experience working in
different stacks rarely_make high_quality contributions to the project._The
only exception is_if they’re_gifted cs students_first. The devs with for eg.
10+_years working with_Perl Dancer projects have so much_you_can learn from.

So_my_advice_would be_to pick one_and_commit to_it_for as long as you can._To
the_point where you both love and hate_it. Get to a_point_where you can
contribute to_an well known open source_project that is built in it’s_domain.

------
cdnsteve
My advice,_look at_what employers are actively hiring for and work backwards.
Generally speaking, many_value an MVC type frameworks, specifically
Rails/Django,_they are well-known, easy_enough to_hire_for since they_are
"standard"_and have_broad application use and are quick to_work with._Most of
the knowledge is transferable between_them. Understanding database migrations,
app_structure,_authentication, etc is common.

I'd focus on_that first, then when you're comfortable,_move towards front-end.
Again, focus on_what_employers_are hiring for, React being_top of the list,
Angular is loosing_market share.

Node isn't_very complicated to develop in, front-end experience_like_ES6/7
will help you figure out JS_and_you can learn the event loop_model_later_on.

This way you'll have a_solid foundation in backend, front-end and_can expand
out from there as needed and specialize but_this is a_good starting point to
be a_full-stack_developer._Spend time looking at