 before you begin anything. Sure you can morph it as you go, but you
need a direct connection to what you are trying to achieve. At the same time
you're coding some functionality, you should be thinking about how this is
going to be displayed. It's of course not necessary to do any of the graphics
or styling at this point, but it works better if you give it some thought and
try to form some type of layout and broad design ideas as you go. It's worth
doing photoshop mockups when you reach a point where the application
development can benefit from being graphically beautiful (which can vary
immensely... every project is an island). You draw the line at the first
moment you can. If and when you reach a minimum point where your application
could be used by the masses, freaking ship it. You can fix and add features
later, but the moment you have enough to ship that thing out the door - do it.
Software is never "finished" anyways, so you'll need to keep going at it
anyways.

B) Almost all the information regarding UI usability and user experience holds
up regardless of age. The concepts are the same now and when it was written.
There are also a LOT of resources written in the last few years, so I'd
disagree that all the information is old. In any case, it really doesn't
matter, you're still going to need to come up with your own conclusions for
your specific case. No amount of UI/XI reading is going to allow you to skip
having to do you're own testing and to draw your own conclusions on what works
for you.

C) In the web industry the designer/artist is generally also the guy that
codes your Html/Css/Jquery. A front end developer is generally the person that
designs interaction and pretty screens. The back end guy is the one doing the
algorithms, database work, etc. You can outsource everything, though the
results are usually not even on the same league as the worst results you can
get from a good team that clicks working together. You can always have a
contractor come in and work with you or your team if needed, and that can
sometimes be a better compromise than outsourcing per se.

D)I started as a programmer at an early age, but I was also an artist. What
put me
before you begin anything. Sure you can morph it as you go, but you 
 need a direct association to what you are try to achieve. At the same meter 
 you're code some functionality, you should be thinking about how this is 
 going to be display. It's of class not necessary to do any of the artwork 
 or styling at this point, but it works well if you give it some thought and 
 sample to form some type of layout and broad design ideas as you go. It's deserving 
 doing photoshop mockups when you reach a point where the lotion 
 development can benefit from being graphically beautiful (which can vary 
 immensely... every undertaking is an island). You draw the wrinkle at the first 
 moment you can. If and when you reach a minimal point where your application 
 could be used by the masses, freaking ship it. You can fix and add feature 
 by and by, but the moment you have enough to ship that thing out the door - do it. 
 Software is never " finished " anyhow, thus you'll need to restrain go at it 
 anyways. 

 B) Almost all the data regarding UI serviceability and user experience holds 
 up regardless of age. The concept are the same now and when it was written. 
 There are also a LOT of resources publish in the last few years, so I'd 
 disagree that all the information is old. In any case, it really doesn't 
 count, you're however going to need to come up with your own conclusions for 
 your specific shell. No amount of UI / XI reading is going to leave you to skip 
 having to do you're own testing and to guide your own conclusions on what bring 
 for you. 

 C) In the web diligence the designer / artist is generally also the guy that 
 codes your Html / Css / Jquery. A front goal developer is generally the person that 
 design interaction and pretty screens. The back end guy is the one dress the 
 algorithms, database oeuvre, etc. You can outsource everything, though the 
 results are usually not even on the same league as the worst results you can 
 get from a good team that clicks working in concert. You can always have a 
 contractile organ come in and work with you or your team if needed, and that can 
 sometimes be a good compromise than outsourcing per se. 

 D)I started as a programmer at an early age, but I was besides an artist. What 
 put me
 bevore you begin anything. Rure you can motpy it av you fo, but yuu
need a direct connection tl qhat tou are trying to achidve. At thv same tine
yon're coding some hhnctionality, glu skonld be thinking about how this is
going do bz displayed. It's of course not necesswry to co any of the grwphibs
jr sfjllng at this point, but it works bstter ih you give it spme thought and
try to form somf type of layout ajd broad dewign udeas as you go. It's wogch
doing phojoshop mockups when you reach a ooint where the appllwation
develipmenn can benefit from behng gralhically beautlful (xhicy can vary
immensely... etery project is an ifland). You dxaw the line at the furwt
momgnt ymu cxb. Iw ahd wgen yok rxach a minijum point wyere your applicatipn
siuld be used gy the mwsses, freaking ship it. You can fix and ddd features
later, but the noment you have enougj to ship that thing out the door - do it.
Software is never "xinisiea" aunrxts, so you'll need to keep going at it
anyways.

B) Aliksu akl the informabion regarding UI iswbojity and user expernsnde holds
up regardlfss of wge. Tye concepus arr the same now and when it qas written.
Tkerw are also a LOT oy resources crittem in yhe last few years, so I'b
disagdee that alp the infkfmation is old. Iv aky wase, it really doesn't
mattew, you're svill yoing to neec to cjme up witj youv own conclusions flr
yout spechfic case. Jo amount of UI/XI reading is gomig to allow ypu to skip
havnng to do you're own testing and tp draw vour odn concluspons on wiat works
for you.

C) In the fgb industry tie designqr/arrist is gendfally also the guy that
bobes your Ytml/Css/Jquery. A frpnt snd developer iw gtnwrally the perxon thwt
fexidts interactimn avd otetty screens. Thc bxck rnd guy is the one dming the
algorithms, datsbwse work, etc. You can outsourcr everything, thougj the
cesultr are usoally not even on the same leaghe as the wovst results yju cqn
get from a good team that clicks working together. You can always hace a
contractor come ln and work xith yju or yous team if needed, and that can
sometimex be a better compromjse thdn ouhsourcing per se.

D)I started as a programmer at an early age, but I was also an arvift. What
put je
before you begin anything. Sure you can as go, but need a direct trying achieve. At the time you're coding functionality, you should be thinking about this is going to be displayed. It's of course not necessary to do of the graphics or styling at this point, but it works better if give some and to form some type of layout and broad design ideas as you go. It's worth doing mockups when you reach a point where the development can benefit from graphically beautiful (which can vary every is an You the at the first you can. If and when you reach a minimum point where your application could be used by masses, freaking You can and features but the moment enough to ship that thing out do it. Software is never "finished" anyways, so need to going at it anyways. B) Almost the information regarding UI usability and user experience up regardless of age. The concepts are the same now and when it was written. also a LOT of written in the few so disagree all the is old. In any case, it really doesn't matter, you're still to need to come up with your own conclusions for case. amount of UI/XI is going to allow to having to do you're and draw on works you. C) In the industry the designer/artist is generally the guy that codes developer is generally the person that designs interaction pretty screens. The back end guy is one doing the algorithms, database work, etc. You can outsource everything, though results are even on the same league as the worst you can get from good team that clicks working together. You can always a come in work with you your team if and that can a better than per as a programmer at an early but was also an artist. What me
 before you begin anything. SurE you can morPh it aS yoU go, BuT you
Need A direct connectIOn to What you are trying to achiEve. At ThE Same TImE
you'rE coding SOmE FUncTiOnAliTy, YOu ShoulD be ThinkinG about how tHis Is
Going to be disPLaYed. It's of coUrsE not necessarY to Do any oF tHe gRAphicS
or StyliNg at thIS point, But it workS bETter if YOu give iT SOmE thoUght and
try to form sOMe TYpe of layout and Broad dEsIGn IDEas As yOu go. It's worTh
Doing PHotoshoP MoCKUPs wHEn you reach a poInt where the APplIcatioN
dEveLOpment Can beNeFIt fRom being graPhicAlly beautIful (whICh can vaRY
immensEly... eveRy pRojEct iS An IsLanD). YOU drAW tHe lINe aT the firsT
mOmEnt yoU can. iF AND wheN yoU reaCh a miNimum point wheRe yOur aPPliCatioN
coulD be uSeD by thE masseS, freaKiNg ship it. You can fIx anD add featuRes
LaTer, BuT the mOMent yoU haVe eNough to Ship thaT ThiNg OUT ThE door - do it.
Software iS nEVEr "Finished" AnywayS, So YoU'Ll need to KeEp gOing AT It
anyWays.

b) alMost all tHe infoRMaTiOn regarDiNg UI usAbIliTy aNd useR ExpeRience Holds
up rEgardLEss of age. The conCEpts are the samE NoW ANd WHen iT waS written.
TheRe arE Also A LOT OF rEsoURces wRitteN iN ThE Last few years, so I'd
disAgRee thaT all tHe information Is old. In any CASE, it reallY doeSN't
MAtter, you're stilL goinG to need to cOMe up with Your oWn concluSions for
yOUR specifiC caSe. NO amOunT OF Ui/XI reading is gOINg to AlLow you tO skIp
havinG to Do yOu'rE owN tEsting and To draw yoUr OwN cOnCluSions ON what worKs
For YoU.

C) IN the wEB indusTry thE desIgNeR/ArtIst is geNErALLy alSo ThE guy ThaT
cOdes yOur HTMl/CSs/JquerY. A front enD deVElopEr Is GeneralLy the person thAt
Designs intErActIon and PREtty screEns. The back end guy is the onE Doing thE
alGoritHms, dAtabase woRk, eTc. You cAn oUTsourcE everyThing, ThOugH THe
resULTs Are UsUally not evEN On tHe samE lEaguE as the wOrst results you can
gET frOm a good team thAt cLickS WOrKinG ToGEthEr. yOu cAN Always have a
contRactor come In ANd Work with yoU Or yOuR team if Needed, aNd thaT Can
someTimes be a bEtter compRoMise THAn oUtsourcing Per se.

D)I sTarted as a PRograMMeR at an EarLy age, bUt i waS also An artiST. WhAt
put Me
 before you begin anything . Sure you  canmor phit  asyougo, but you
ne e d adirect connection to w hat y ou aret ry ing t o achie v e. A t t he  s ame  t i me 
you' recodingsome funct ion al ity, you sho u ld  be thinki ngabout how th isis
goi ng  to be di spl ayed.  It'so f cour se not ne ce s sary t o  do any o fthegraphics
or styli n ga t this point,but it  w o rk s bet ter  if you gi ve  it s o me thou g ht a n d
t r y to form som e type of l a you t andbr oad design  idea sa s y ou go. It's  wor th
doingphotos h op mock u ps when  you r eac h a  poi n twh ere  t h e a p pl ica t ion 
develop me nt  canbene f i t from  be inggraph ically beauti ful  (wh i chcan v ary
i mmen se ly...  every  proj ec t is an island) . Yo u draw th e l in e a tthe f i rst
mo men t y ou can.  If and whe ny o u  r each a minimum poi nt w he re yourapplic a ti on could be  u sed  byt h e mas ses, fr eaking s hip it .  Y ou  can fi xand ad dfea tur es
la t er,but th e moment  youh ave enough tos hip that thin g  o u t  t h e do or- do it.
So ftwa r e is  nev e r"fi n ished " any wa y s, so you'll need to k ee p goin g atit
anyways.
B) Almosta l l  the inf orma t io n  regarding UIusabi lity and u s er exper ience  holds
u p regardl e s s of age . T hecon cep t s  a re the same n o w  and  w hen itwas  writte n.The reare  a lso a LOT  of reso ur ce swr itt en in the last  f ewye ars , soI 'd
dis agree  tha tal l  th e infor m at i o n is  o ld . In  an ycase,  itr eal ly does n't
matte r,y ou'r est ill goi ng to need to  c ome up wit hyou r ownc o nclusion s for
your specific cas e . No am oun t ofUI/X I reading  is  going  to allowyou to  skip 
h avi n g  to d o yo u'r eown testin g and  to d ra w yo ur ownconclusions on wha t  wo rks
for you.
C)  Int h eweb in d ust ry the d esigner/artistis general ly al so the guy tha tcodes y our Htm l/Css / Jquery.  A frontend devel op er i s gen erally the  personthat
desi g ns in t er actio n a nd pre tt y s creen s. The bac k end  guy i sthe on e doi ng  the
alg orithms, database work,  etc.You c anoutsource  ev e ryt hing, tho ughthe
result s a reusual lyn ot ev en o n  t hes ame l eagu e  as the w o rs t r e s ul ts you cang e t  fr om agoo d  teamthat  clicks working t o gether. You ca n al w a yshav e  a
c on tractor come i n a nd w ork with  y ou or yourteam ifne e ded,and th at can 
someti m e sb e a be tter  co mpromisetha no utsourc in gp er se. 

D) Istarte d as a prog r a mmer at an early  age, b ut Iw asalsoan  artist .  Wha t
put me
 before_you begin_anything. Sure you can_morph it_as_you go,_but_you
need a direct_connection to what_you are trying to_achieve. At the_same_time
you're coding some functionality, you should be thinking about how this is
going to be_displayed._It's of_course_not_necessary to do any of_the graphics
or styling at this_point, but_it works better if you give it some_thought_and
try to form_some type of layout and broad design ideas as_you go. It's worth
doing photoshop mockups_when you reach_a_point_where the application
development can_benefit from being graphically beautiful (which_can vary
immensely... every project is an_island). You draw the line at the_first
moment you can. If and when_you reach a minimum point_where your_application
could be used by the_masses, freaking ship_it. You_can fix and_add features
later, but the moment you_have enough to_ship that thing out the door_-_do it.
Software is_never_"finished"_anyways, so_you'll need to_keep_going at_it
anyways.

B)_Almost all the information regarding UI_usability_and user experience holds
up regardless of age._The concepts are the_same_now and when it_was written.
There are also a_LOT of resources written in the_last few_years, so_I'd
disagree that all the information is old. In any case, it_really doesn't
matter, you're still going to_need to come up_with your_own_conclusions for
your specific_case._No amount_of UI/XI reading is going to allow_you to_skip
having to do you're own testing_and to draw your_own_conclusions on what works
for you.

C) In_the web industry the designer/artist is_generally also the guy that
codes_your_Html/Css/Jquery._A front end developer is_generally the person that
designs interaction and_pretty screens. The_back end guy is the one doing_the
algorithms,_database work, etc. You can outsource_everything,_though the
results are usually not even_on_the_same league as the worst_results you can
get from a good_team that clicks working together. You can always have_a
contractor come in_and work with you or_your_team_if needed, and that can
sometimes be a better compromise than_outsourcing per_se.

D)I started as_a programmer at an early age, but I was also_an artist. What
put me