Coding skills or Language knowledge ?

[tjt]

Am avut la munca azi o mica disputa despre ce e mai important la un programator "coding skills" sau "language knowledge".

Eu la inceputurile mele credeam ca coding skills e sfant, intre timp mi-am schimbat parerea si o cunoastere in detaliu limbajului cu care lucrezi face mult, foarte mult si te poate scoate din multe cacaturi. Intr-un final nu ajungi sa lucrezi in cercetare ci in productie unde te lovesti de multe cacaturi.

 

Concluziile dezbateri au fost :

1. coding skills

- poti sa te adaptezi usor la orice limbaj;

- exista stackoverflow si google, orice algoritm/problema probabil deja are o rezolvare;

- gandesti prea abstract si nu poti sa te adaptezi la ceea ce cere clientul;

- pierzi prea mult timp incercand sa obtii solutia cea mai optima;

- debugging-ul de cele mai multe ori te omoara;

 

2. language knowledge:

- debuggingul e floare la ureche ---> pierzi putin timp pe buguri;

- esti axat prea mult pe un limbaj, tranzitia catre un alt limbaj e destul de grea;

- poti folosi toate beneficiile pe care ti le ofera acel limbaj ---> timp mai putin, nu reinventezi roata;

- esti mai flexibil in gandire;

- solutia care merge e deobicei solutia care o accepti ---> respecti deadline-urile;

 

Cum stau lucrurile din punctul vostru de vedere ?

[gigiRoman]

Flexibilitatea.

https://github.com/yuanhui-yang/Cracking-the-Coding-Interview/blob/master/Cracking the Coding Interview - 4th Edition.pdf

Pasaj din carte:

"Pop Divas Need Not Apply

Leonard  was  a  very  promising  C++  coder,  three  years  out  of  college,  with  a  solid  work  history and  an  impressive  skill  set    He  proved  on  the  phone  screen  that  he  was  above-average  technically,  and  so  he  was  invited  in  for  an  interview    We  needed  a  savvy  C++  person  to  work  on a  piece  of  middleware  that  interfaced  with  our  database,  and  Leonard  seemed  like  a  sure  fit However,  once  we  started  talking  to  him,  things  went  south  in  a  hurry    He  spent  most  of  the interview  criticizing  every  tool  and  platform  that  we  questioned  him  on    We  used  SQL  Server as  our  database?  Puhleease    We  were  planning  to  switch  to  Oracle  soon,  right?  What’s  that? Our  team  used  Tool  A  to  do  all  our  coding  in?  Unacceptable    He  used  Tool  B,  and  only  Tool B,  and  after  he  was  hired,  we'd  all  have  to  switch  to  Tool  B    And  we'd  have  to  switch  to  Java, because  he  really  wanted  to  work  with  Java,  despite  the  fact  that  75  percent  of  the  codebase would  have  to  be  rewritten    We'd  thank  him  later   And  oh,  by  the  way,  he  wouldn’t  be  making any meetings before ten o'clock Needless  to  say,  we  encouraged  Leonard  to  seek  opportunities  elsewhere    It  wasn’t  that  his ideas  were  bad  –  in  fact,  he  was “technically” right  about  many  things,  and  his  (strong)  opinions  were  all  backed  with  solid  fact  and  sound  reason  (except  for  the  ten  o'clock  thing  –  we think  he  may  have  just  been  making  a “power  play” )  But  it  was  obvious  that,  if  hired,  Leonard wasn’t  going  to  play  well  with  others  –  he  would  have  been  toxic  kryptonite  for  team  chemistry    He  actually  managed  to  offend  two  of  the  team  members  during  the  forty-five  minutes of  his  interview    Leonard  also  made  the  mistake  of  assuming  that  Code  Purity  and  Algorithm Beauty were always more important than a business deadline In  the  real  world,  there  are  always  compromises  to  be  made,  and  knowing  how  to  work  with the  business  analysts  is  just  as  important  as  knowing  how  to  refactor  a  blob  of  code    If  Leonard  would  not  have  gotten  along  with  other  IT  people,  he  definitely  wouldn’t  have  gotten along  with  the  business  folks    Maybe you can get  away with  hiring  a  Leonard  if  he’s  one  of  the best  ten  coders  in  the  world  (he  wasn’t)    But  he  was  the  classic  failure  example  for  the “Would you have a beer with this guy?” test "

[DoubleG]

cred ca ma incadrez la 2.

[tjt]

10 hours ago, gigiRoman said:

Flexibilitatea.

https://github.com/yuanhui-yang/Cracking-the-Coding-Interview/blob/master/Cracking the Coding Interview - 4th Edition.pdf

Pasaj din carte:

"Pop Divas Need Not Apply

Leonard  was  a  very  promising  C++  coder,  three  years  out  of  college,  with  a  solid  work  history and  an  impressive  skill  set    He  proved  on  the  phone  screen  that  he  was  above-average  technically,  and  so  he  was  invited  in  for  an  interview    We  needed  a  savvy  C++  person  to  work  on a  piece  of  middleware  that  interfaced  with  our  database,  and  Leonard  seemed  like  a  sure  fit However,  once  we  started  talking  to  him,  things  went  south  in  a  hurry    He  spent  most  of  the interview  criticizing  every  tool  and  platform  that  we  questioned  him  on    We  used  SQL  Server as  our  database?  Puhleease    We  were  planning  to  switch  to  Oracle  soon,  right?  What’s  that? Our  team  used  Tool  A  to  do  all  our  coding  in?  Unacceptable    He  used  Tool  B,  and  only  Tool B,  and  after  he  was  hired,  we'd  all  have  to  switch  to  Tool  B    And  we'd  have  to  switch  to  Java, because  he  really  wanted  to  work  with  Java,  despite  the  fact  that  75  percent  of  the  codebase would  have  to  be  rewritten    We'd  thank  him  later   And  oh,  by  the  way,  he  wouldn’t  be  making any meetings before ten o'clock Needless  to  say,  we  encouraged  Leonard  to  seek  opportunities  elsewhere    It  wasn’t  that  his ideas  were  bad  –  in  fact,  he  was “technically” right  about  many  things,  and  his  (strong)  opinions  were  all  backed  with  solid  fact  and  sound  reason  (except  for  the  ten  o'clock  thing  –  we think  he  may  have  just  been  making  a “power  play” )  But  it  was  obvious  that,  if  hired,  Leonard wasn’t  going  to  play  well  with  others  –  he  would  have  been  toxic  kryptonite  for  team  chemistry    He  actually  managed  to  offend  two  of  the  team  members  during  the  forty-five  minutes of  his  interview    Leonard  also  made  the  mistake  of  assuming  that  Code  Purity  and  Algorithm Beauty were always more important than a business deadline In  the  real  world,  there  are  always  compromises  to  be  made,  and  knowing  how  to  work  with the  business  analysts  is  just  as  important  as  knowing  how  to  refactor  a  blob  of  code    If  Leonard  would  not  have  gotten  along  with  other  IT  people,  he  definitely  wouldn’t  have  gotten along  with  the  business  folks    Maybe you can get  away with  hiring  a  Leonard  if  he’s  one  of  the best  ten  coders  in  the  world  (he  wasn’t)    But  he  was  the  classic  failure  example  for  the “Would you have a beer with this guy?” test "

 

 

Am citit si eu cracking the code interview, dar da... e adevarat.

Multi stiu tot felul de algoritmi, dar daca ii pui sa faca ceva simplu nu reusesc... nu au flexibilitate in gandire...

 

 

 

Edited April 4, 2017 by tjt

[gigiRoman]

Apropos de thread-ul tau mi-am mai amintit de cartea Pragmatic Programmer.

Si un link util:

http://rion.io/2017/01/07/my-developer-resolutions-for-2017/

Plus cartile mentionate in link:

https://ufile.io/0e16c1

Edited April 5, 2017 by gigiRoman

[emylian]

print "Hello World"

Daaa sunt programator..

 

[MrGrj]

16 hours ago, emylian said:

print "Hello World"

Daaa sunt programator..

 

Care-i scopu' postarii tale ?

 

ON: Va recomand si eu un curs de introducere in Computer Science de la Harvard care mi se pare absolut genial. Si nu pentru ca e foarte stufos, ci pentru ca tipul care il preda e foarte pasionat. 

 

Ca idee, tipu' incepe cu Scratch, continua cu C, si apoi trece si prin Python / Js / ceva SQL. Il recomand cu incredere mai ales celor care vor sa inceapa de undeva. Treceti prin toate lectiile si faceti toate temele. Incercati sa va puneti mintea la contributie si sa nu copiati raspunsurile de pe internet. 

 

Link: https://cs50.harvard.edu/weeks

 

Multumiri lu' @Usr6 in special (el mi-a zis de curs).

 

-->

@MrGrj Vezi ca la sf cursului te ascult :)))

<--Usr

[Guest]

Cel mai important lucru este sa fii disponibil sa inveti chestii noi oricand, sa nu ti se incrusteze in cap ideea ca "stii tot" sau lucruri de genul... Poate peste 20 de ani limbaje precum C# sau orice alt limbaj popular acum vor fi considerate "depasite".

 

 Discutia cu limbajul e relativa, conteaza sa stii sa gandesti, conteaza sa stii sa scrii cu pixul, ca pixul se strica nu e nimic, poti sa faci rost de altul.

 

 

Eu consider ca trebuie cate putin din toate dar disponibiliatea de a invata chestii noi si de a te mentine informat este numarul 1 pe lista.

[spiritmoney]

On 4/24/2017 at 3:55 PM, emylian said:

print "Hello World"

Daaa is a programmer ..

 

Am încredere că faci minunat. Puteți configura un server dedicat pentru mine și instala un e-mail în el.