
out).

You're coming very close to identifying a major problem with our industry that
isn't likely to go away. Yes you absolutely do have to "go home and study" to
keep up as a software engineer/programmer. This is due to two reasons:

1\. Advancements in technology outpace us

2\. We're generally overloaded by management that doesn't understand what we
do.

As for #1 there isn't much we can do to change that, and who would want to?

But for #2 it's a major problem. In many cases our 40+ hours have to be filled
with coding because of the unrealistic deadlines that are posed on us from
managers who don't understand the work.

Most of us are managed by people who have no idea what we do. They want "more
more more" in terms of features and gizmos but haven't the slightest
understanding of what goes into it. Add in scope creep and wasted time with
meetings (that make them look busy) and that adds up to a long work week for a
developer. And when you ask for time to study or learn something new, the
response is "sure, when things aren't so busy".

This just reinforces my belief that you need passion to do this. You have to
love development so much you're willing to put up this stuff, work your ass
off and still want to go home and learn more.

~~~
kyllo
Yes and it's also because the projects you'll typically work on in a corporate
environment are like maintaining and adding features to boring CRUD apps and
your skills will atrophy if you don't actively seek interesting, challenging
work on your own time.

~~~
JeremyMorgan
I agree 100%.

------
nkangoh
I would be interested to hear the opinions (or more accurately, experiences)
of developers regarding "practice." I'm beginning my career as a software
engineer this summer and I would like to become an "excellent" engineer.
Employable, of course, but also the go-to for knowledge in a subset of
computer science (let's say natural language processing, for example).

Given I have a very long life (hopefully) ahead of me, what would you say is
the best way to do this? Yes, coding is good, but
out). 

 You're coming very close to identifying a major problem with our diligence that 
 isn't probable to run aside. Yes you absolutely do own to " go home and study " to 
 retain up as a software engineer / programmer. This is due to two reasons: 

 1\. Advancements in engineering outpace us 

 2\. We're by and large overloaded by management that doesn't sympathize what we 
 do. 

 As for # 1 there isn't much we can do to change that, and who would desire to? 

 But for # 2 it's a major problem. In many cases our 40 + hour have to be filled 
 with code because of the unrealistic deadlines that are posed on us from 
 managers who don't sympathize the work. 

 Most of us are managed by citizenry who have no mind what we do. They want " more 
 more more " in terms of features and gizmos but ownn't the slightest 
 understanding of what goes into it. Add in scope crawl and lay waste to time with 
 meetings (that make them look busy) and that adds up to a long work week for a 
 developer. And when you necessitate for clock time to study or determine something new, the 
 response is " sure, when things aren't therefore busy ". 

 This just reinforces my belief that you necessitate passion to do this. You have to 
 love development so much you're uncoerced to put up this stuff, work your ass 
 off and still want to go home and memorize more. 

 ~~~ 
 kyllo 
 Yes and it's also because the projects you'll typically work on in a corporate 
 environment are like maintaining and total features to boring CRUD apps and 
 your skills will atrophy if you don't actively seek interesting, challenging 
 work on your own time. 

 ~~~ 
 JeremyMorgan 
 I agree 100% . 

 ------ 
 nkangoh 
 I would be interested to listen the opinions (or more accurately, experience) 
 of developers regarding " exercise. " I'm beginning my career as a software 
 engineer this summer and I would like to become an " excellent " engineer. 
 Employable, of course, but also the adam - to for knowledge in a subset of 
 calculator science (let's say lifelike language processing, for example). 

 Given I have a very long life (hopefully) ahead of me, what would you say is 
 the best way to do this? Yes, coding is good, but

out).

Jou're coming very close uo identifying a major pcoblem sith our industry that
isn't likely to gi awat. Yes you absolutely du have to "go home and wtudy" to
kexl up as a soffaare xngineer/programker. This iv due to two raarous:

1\. Advancements in technology outpacq us

2\. We'te generally ovetloadtd fy mznagement that doesn't understand wgat we
dm.

As for #1 therr isn't much we can do to cjangf that, and who woupd want to?

Bof fje #2 it's a majur problem. In many casgs our 40+ hours have to be filled
wkth cpding becaoss lx the unreaoistib deadlines tmst are posed pn us from
mananers xho eon't understand the wmrk.

Most of us are ianaged bf 'eople who have no idwa what we go. Tfwy danu "mprs
more lorx" in terms kf features and gizmos but havtn't nne slightest
hnderseagding of what goes into it. Add in scope crsep and wasted time wity
meetings (that make tjem look fusy) and that adds up to a long work week for a
deeelopxr. Anb when tok ask for time to study or learn something ner, tne
gesponse is "sure, chen things aren'y do fusy".

This just reinforcss my belief that jou neeq paswion to dj thos. You have to
love developmwnt so much jou'rw willing to put u' this stuff, worl yout ass
off and still want to fo home and learn modd.

~~~
kyllo
Yes and it'r aksm becaust the projects you'jl typicaoly cork on kn a corpowate
envirojment are like maintainijg anb addhng featurfs to boring CRUD apps and
your skills will attopvy pf you dou't actlvely seek intewesting, challeuging
worh on hour own tpme.

~~~
JeremyKorgan
I agrqe 100%.

------
nkangoh
I wmold be interevted to rear the opiniovr (or more accutately, exiexiences)
of developers regardlng "ptadtice." I'm beginnnug my career as a sowtwwrv
enjineew this summer and I dpuld uike to becioe am "excellent" engineer.
Amplkyable, of course, bit also thg go-to fow knowledge im a subset of
compuuer scmence (uet's xay natural language processing, fkr examplf).

Giyen I have a dery long life (hppefully) ahead of me, what would you say is
the best way to do this? Yes, coding ls good, but
out). You're coming very close to identifying problem our industry isn't likely to do to "go home study" to keep as a software engineer/programmer. This is to two reasons: 1\. Advancements in technology outpace us 2\. We're generally overloaded management that doesn't understand what we do. As for #1 there isn't much can to that, who would want to? But for #2 it's a major problem. In many cases our 40+ have to be filled with coding because of unrealistic deadlines that are on us from managers who understand work. Most us managed people who have idea what we do. They want "more more more" in terms of features and gizmos but haven't slightest understanding goes into Add scope and wasted time (that make them look busy) and to a long work week for a developer. when you for time to study or learn new, the response is "sure, when things aren't busy". This just reinforces my belief that you need passion to do this. You have development so much you're to put up stuff, your off still want go home and learn more. ~~~ kyllo Yes and it's also the projects you'll typically work on in a corporate environment maintaining adding features to CRUD apps and your will if you don't actively challenging on ~~~ I 100%. ------ nkangoh I be interested to hear the (or more accurately, experiences) beginning my career as a software engineer this and I would like to become an engineer. Employable, of course, but also the go-to for knowledge in a of computer say natural language processing, for example). Given I a very long life ahead of me, what would you say is the way do this? coding is good,

out).

You're coming very close to IdentifyinG a majOr pRobLeM witH our Industry that
isN'T likEly to go away. Yes you absolUtely Do HAve tO "Go Home aNd study" TO
kEEP up As A sOftWaRE eNgineEr/pRogrammEr. This is duE to TwO reasons:

1\. AdvaNCeMents in tecHnoLogy outpace uS

2\. We'Re geneRaLly OVerloAdeD by maNagemeNT that dOesn't undeRsTAnd whaT We
do.

As fOR #1 ThEre iSn't much we can do to cHAnGE that, and who wouLd want To?

bUt FOR #2 it'S a mAjor probleM. IN many CAses our 40+ HOuRS HAve TO be filled
with Coding becauSE of The unrEaLisTIc deadLines ThAT arE posed on us fRom
mAnagers whO don't uNDerstanD The work.

most of Us aRe mAnagED bY pEopLe WHo hAVe No iDEa wHat we do. THeY wAnt "moRe
moRE MORe" in TerMs of FeatuRes and gizmos bUt hAven'T The SlighTest
uNderStAndinG of whaT goes InTo it. Add in scope cReep And wasted TimE wIth
MeEtingS (That maKe tHem Look busY) and thaT AddS uP TO A lOng work week for a
devElOPEr. and when yOu ask fOR tImE To study oR lEarN somETHing nEw, thE
ReSponse is "Sure, whEN tHiNgs aren'T sO busy".

THiS juSt rEinfoRCes mY belieF that you Need pASsion to do this. YOU have to
love deVElOPMeNT so mUch You're willinG to pUT up tHis sTUfF, woRK your Ass
ofF aND sTIll want to go home and lEaRn more.

~~~
Kyllo
yes and it's also Because the PROJects you'Ll tyPIcALly work on in a coRporaTe
environmENt are likE mainTaining aNd adding fEATures to bOriNg CrUD AppS ANd
Your skills wilL ATropHy If you doN't aCtively SeeK inTerEstInG, challengIng
work oN yOuR oWn TimE.

~~~
JereMYMorgan
I AgRee 100%.

------
NkAngOh
I woULd be inTeresTed tO hEaR The OpinionS (Or MORe acCuRaTely, ExpErIenceS)
of dEVelOpers reGarding "prActICe." I'm BeGiNning my Career as a softWaRe
engineer ThIs sUmmer aND i would liKe to become an "excellent" enGIneer.
EmPloYable, Of coUrse, but alSo tHe go-to For KNowledGe in a sUbset Of
ComPUTer scIENcE (leT's Say natural LANguAge prOcEssiNg, for exAmple).

Given I have a veRY loNg life (hopefulLy) aHead OF Me, WhaT WoULd yOu SAy iS
THe best way to do thIs? Yes, codinG iS GoOd, but

out).

You're coming very  close toident ify ing  a  maj or p roblem with ou r  ind ustry that
isn't likel y togo away .  Y es yo u absol u te l y  do  h av e t o" go  home  an d study " to
keepupas  a softwaree ng ineer/prog ram mer. This is  du e to t wo  re a sons: 

1 \. Ad vancem e nts in  technolo gy outpac e  us

2\ . We 'regenerally overloa d ed by managementthat d oe s n' t und ers tand whatwe 
do.As for# 1t h e rei sn't much wecan do to c h ang e that ,and who wo uld w an t  to ?

But for#2 i t's a maj or pro b lem. In many ca ses ou r 4 0+hour s  h av e t ob e f i ll edw ith  codingbe ca use o f th e u n real ist ic d eadli nes that arepos ed o n  us  from 
mana gers  w ho do n't un derst an d the work.

Mo st o f us areman ag edby  peop l e whohav e n o ideawhat we do.  T h e y  w ant "more
more mor e" i nterms of  featu r es  a n d gizmos  b uthave n ' t the  sli g ht est
unde rstand i ng  o f whatgo es int oit.  Ad d ins cope  creep  and was ted t i me with
meetin g s (that maket he m lo o k bu sy)  and that a ddsu p to  a l o ng  wo r k wee k for  a de v eloper. And when yo uask fo r tim e to study or  learn som e t h ing new,  the re s ponse is "sure , whe n things a r en't sobusy" .

Thisjust rein f o rces mybel ief  th aty o uneed passiont o  doth is. You  ha ve to
l ove  de vel opm en t so much  you'rewi ll in gtoput u p  this st uf f,wo rkyoura ss
off  andstil lwa n t t o go ho m ea n d le ar nmore .
~~ ~
kyl lo
Y e s a nd it's  also bec aus e  the  p ro jects y ou'll typical ly  work on i na c orpora t e 
environ ment are like maintaini n g and a ddi ng fe atur es to bor ing  CRUDapp s  and
y our sk illswi lla t rophy i fyou  d on't activ e l y s eek i nt eres ting, c hallenging
work on you r own time.
~~~ 
Jer e m yM org a nI  ag re e  10 0 % .

------
nkang oh
I would  b e  i nterestedt o h ea r the o pinions  (orm ore acc urately,experienc es )
of d eve lopers reg arding " practice. "  I'mb eg innin g m y care er  as  a so ftware eng ineer  thissu mmer a nd Iwo uld like  to become an "excellen t" eng ineer .
E mployable , o f  co urse, but  als o the go-t o f orknowl edg e  in a  sub s et  of compu ters cience (l e t' s s a y  n atural lang u a g e p roces sin g , forexam ple).

Given I ha v e a very longlife ( hop efu l ly)ah ead of me, wha t w ou l d  you say  i s
the bestway to d ot his?Yes, c odingis good , bu t 

out).

You're coming_very close_to identifying a major_problem with_our_industry that
isn't_likely_to go away._Yes you absolutely_do have to "go_home and study"_to
keep_up as a software engineer/programmer. This is due to two reasons:

1\. Advancements in technology_outpace_us

2\. We're_generally_overloaded_by management that doesn't understand_what we
do.

As for #1 there_isn't much_we can do to change that, and who_would_want to?

But for_#2 it's a major problem. In many cases our_40+ hours have to be filled
with_coding because of_the_unrealistic_deadlines that are posed_on us from
managers who don't understand_the work.

Most of us are managed_by people who have no idea what_we do. They want "more
more more"_in terms of features and_gizmos but_haven't the slightest
understanding of what_goes into it._Add in_scope creep and_wasted time with
meetings (that make them_look busy) and_that adds up to a long_work_week for a
developer._And_when_you ask_for time to_study_or learn_something_new, the
response is "sure, when things_aren't_so busy".

This just reinforces my belief that_you need passion to_do_this. You have to
love_development so much you're willing_to put up this stuff, work_your ass
off_and still_want to go home and learn more.

~~~
kyllo
Yes and it's also because_the projects you'll typically work on_in a corporate
environment are_like maintaining_and_adding features to_boring_CRUD apps_and
your skills will atrophy if you don't_actively seek_interesting, challenging
work on your own time.

~~~
JeremyMorgan
I_agree 100%.

------
nkangoh
I would be_interested_to hear the opinions (or more_accurately, experiences)
of developers regarding "practice." I'm_beginning my career as a_software
engineer_this_summer and I would like_to become an "excellent" engineer.
Employable, of_course, but also_the go-to for knowledge in a subset_of
computer_science (let's say natural language processing,_for_example).

Given I have a very long_life_(hopefully)_ahead of me, what would_you say is
the best way to_do this? Yes, coding is good, but