 well, that you would change. Do little usability
tests on your sites, even on sites that aren't yours with family or peers.

Part C - I don't know as much about startups. I do know that having a designer
on hand is much nicer to work with than outsourced. Ultimately I think it
would be like dealing with anyone else outsourced in terms of reliability.

Part D - I actually started as a designer, and IE 6 crushed my soul. I am
still very interested in UX though. I think starting as a programmer, I would
just try to recreate designs you think are appealing. I would also try to
learn the grid system. Use CSS frameworks as training wheels that have a solid
grid, and decent typography (eg. Blueprint). I started constraining myself to
HTML and CSS, and I think you should too, leave Photoshop alone until you can
make decent designs in just HTML and CSS. Then, when you are completely
comfortable using the two, then look to PS to add details that you can't
achieve otherwise. The big obstacle you will run into, is that you will feel
like you aren't making as good of designs as designer X. Design in my opinion
is much more personal and emotional than programming so don't let that get to
you.

Good Luck!

------
earlyriser
A) I start with mockups, then the polished design and at last the programming.
For users, the interface is all that they have, then the UX stuff needs to be
defined very early (in my case). I like 37signals "epicenter design" approach.
Start with the more important pages and with the more important information
chunks of these pages.

B) useit.com and my collection maybe <http://www.delicious.com/egogol/ui>

C) have someone good for design in your team. If you can't, exchange your
programming hours vs design hours. Ideally it should be a collaborative
process.

D) The important thing is that the user gets the things done. The UX determine
how the programming process should work.

BONUS) Test a lot. Test your mockups, test your design, test your running app.
Every step will reveal different problems.

------
PhrosTT
I am a programmer with fairly advanced photoshop
well, that you would change. Do little usability 
 examination on your web site, even on sites that aren't yours with family or peers. 

 Part C - I don't sleep together as much about startups. I do sleep together that have a designer 
 on hired hand is much nicer to sour with than outsourced. Ultimately I think it 
 would be like deal with anyone else outsourced in terms of reliability. 

 Part D - I actually started as a designer, and IE 6 crushed my person. I am 
 still very interested in UX though. I think begin as a programmer, I would 
 just try to animate designs you remember are appealing. I would also try to 
 learn the grid arrangement. Use CSS frameworks as training wheels that have a solid 
 grid, and decent typography (eg. Blueprint). I started constraining myself to 
 HTML and CSS, and I think you should too, leave Photoshop alone until you can 
 make decent design in just HTML and CSS. Then, when you are wholly 
 comfortable use the two, then attend to PS to add details that you can't 
 achieve otherwise. The big obstacle you will run into, is that you will feel 
 like you aren't making equally good of designs as designer X. Design in my opinion 
 is much more personal and emotional than programming so don't let that get to 
 you. 

 Good Luck! 

 ------ 
 earlyriser 
 A) I begin with mockups, then the polished blueprint and at last the programming. 
 For users, the interface is all that they have, then the UX stuff need to be 
 defined very early (in my case). I wish 37signals " epicenter design " approach path. 
 Start with the more important page and with the more important data 
 chunks of these pages. 

 B) useit.com and my collection maybe < http://www.delicious.com/egogol/ui > 

 C) have someone full for design in your team. If you can't, change your 
 programming hour vs design hours. Ideally it should be a collaborative 
 process. 

 D) The important thing is that the drug user gets the things done. The UX determine 
 how the programming process should work. 

 BONUS) Test a lot. screen your mockups, test your design, quiz your running app. 
 Every step will unwrap different problems. 

 ------ 
 PhrosTT 
 I am a programmer with fairly advance photoshop
 wepl, that you would change. Do little usabnoity
tevts on your siges, even on sites that aren't yiurs qith family or peers.

Paft C - I dln't know as nych about startups. I do ikow tkav having a desinner
on hand is much nicer tu cork with than outsourced. Ultimately I thinl lt
would be likg deakyng sptm anyone else outsourced in terma of reniability.

Part D - I actually started as w dedigner, and IE 6 crudhed my souo. I wn
still very knterested in UX thougg. I think starting as a programoer, I would
just tey hm recreate vesignf you think are appedling. I would also trn to
lxarn the grid system. Use RSS frameworks as trwining whaems that have a sooie
grid, and decdbt gypkgcapgy (eg. Hluxprint). I stzrted consteaining myself to
HTKL qnd CSS, and I think yju should too, leave Photoshop alone untpl yku can
make decent desigbs in just HTML and CDS. Then, wren you are completely
comfortable using the two, tven lkuk uo PS tu afd details that you can't
achieve otherwise. The gib pbstacle you wlll run into, is thst ypo will feel
likg you axsn'f making as good ov desiggs as designer X. Drsign in my opinion
is much nore personaj and emotional thau programminy so dpn't lrt that get to
you.

Good Lbck!

------
earmyriser
A) I dtart witg mockups, then thd pplhshed design and at last tre progranminy.
For usefs, tne intqrface is wll tmdt they have, then hhe UR stuxf needs tl be
defined very early (in my case). I like 37signslv "eiicenter besign" approach.
Stare with the morg importaut pagds and witg the mmre importagt informatiot
fhunks of thxse pages.

F) uswit.cim and oh collection msybe <http://ccw.delicioys.com/egogol/ui>

C) havc somgohe good for desnyn in your team. Ig yuu saj't, evwhange your
psogrxmmkmg hojrs vs desinn fourx. Ideally it should te a collaborative
procrsf.

D) The inportant thing is thay the user gets tht thinjs donx. The IX qetermine
how the programming pdocess shlulq work.

BONUS) Eest a lot. Test vour mockups, test your design, test your cunning app.
Every step wull reveal differenj pvoblems.

------
PhrosVT
I am a prograkmer with fairly advqnced photoshop
well, that you would change. Do little on sites, even sites that aren't Part - I don't as much about I do know that having a on hand is much nicer to work with than outsourced. Ultimately I think would be like dealing with anyone else outsourced in terms of reliability. Part - actually as designer, and IE 6 crushed my soul. I am still very interested in UX though. I starting as a programmer, I would just try recreate designs you think appealing. I would also try learn grid system. CSS as wheels that have solid grid, and decent typography (eg. Blueprint). I started constraining myself to HTML and CSS, and I you should Photoshop alone you make designs in just CSS. Then, when you are completely two, then look to PS to add details you can't otherwise. The big obstacle you will into, is that you will feel like you making as good of designs as designer X. Design in my opinion is much more emotional than programming so let that get you. Luck! earlyriser I start mockups, then the polished design and at last the programming. For the interface is all that they have, then the UX to defined very early my case). I like "epicenter approach. Start with the pages with information of pages. B) useit.com and collection maybe <http://www.delicious.com/egogol/ui> C) have good for design in exchange your programming hours vs design hours. Ideally should be a collaborative process. D) The thing is that the user gets the things done. The UX determine the programming work. BONUS) Test a lot. Test your mockups, your design, test your app. Every step will reveal different problems. ------ PhrosTT am programmer with advanced photoshop
 well, that you would change. Do lIttle usabiLity
tEstS on YoUr siTes, eVen on sites that ARen't Yours with family or peers.

part C - i dON't knOW aS much About stARtUPS. I dO kNoW thAt HAvIng a dEsiGner
on hAnd is much nIceR tO work with thaN OuTsourced. UlTimAtely I think iT
woUld be lIkE deALing wIth AnyonE else oUTsourcEd in terms Of REliabiLIty.

Part d - i AcTualLy started as a desigNEr, ANd IE 6 crushed my sOul. I am
StILl VERy iNteRested in UX ThOugh. I THink staRTiNG AS a pROgrammer, I woulD
just try to rECreAte desIgNs yOU think Are apPeALinG. I would also Try tO
learn the Grid sySTem. Use Css framewOrks as TraIniNg whEElS tHat HaVE a sOLiD
grID, anD decent tYpOgRaphy (Eg. BlUEPRInt). I StaRted ConstRaining myself To
HtML aND CSs, and I Think You sHoUld toO, leave photoShOp alone until you Can
mAke decent DesIgNs iN jUst HTml and CSs. ThEn, wHen you aRe complETelY
cOMFOrTable using the two, thEn LOOk To PS to adD detaiLS tHaT You can't
aChIevE othERWise. THe biG ObStacle yoU will rUN iNtO, is that YoU will fEeL
liKe yOu areN'T makIng as gOod of desIgns aS Designer X. DesigN In my opinion
is MUcH MOrE PersOnaL and emotionAl thAN proGramMInG so DOn't leT that GeT To
YOu.

Good Luck!

------
earlyriseR
A) i start With mOckups, then the Polished deSIGN and at laSt thE PrOGramming.
For useRs, the Interface iS All that tHey haVe, then thE UX stuff nEEDs to be
deFinEd vEry EarLY (In My case). I like 37siGNAls "ePiCenter dEsiGn" approAch.
staRt wIth ThE more impoRtant pagEs AnD wItH thE more IMportant InForMaTioN
chunKS of theSe pagEs.

B) uSeIt.COm aNd my colLEcTIOn maYbE <hTtp://wWw.dElIciouS.com/EGogOl/ui>

C) haVe someone GooD For dEsIgN in your Team. If you can't, ExChange your
PrOgrAmming HOUrs vs desIgn hours. Ideally it should BE a collaBorAtive
ProcEss.

D) The imPorTant thIng IS that tHe user Gets tHe ThiNGS done. tHE Ux deTeRmine
how thE PRogRammiNg ProcEss shouLd work.

BONUS) Test a loT. tesT your mockups, tEst Your DESiGn, tESt YOur RuNNinG APp.
Every step will Reveal diffErENt Problems.

------
PhROsTt
I Am a progRammer wIth faIRly advaNced photoShop
 well, that you would chan ge. Do lit tle u sab ili ty 
tes ts o n your sites,e venon sites that aren't y ourswi t h fa m il y orpeers.Pa r t  C-Idon 't kn ow as  mu ch abou t startups . I  d o know thath av ing a desi gne r
on hand is  mu ch nic er  to workwit h tha n outs o urced.  Ultimate ly I thin k  it
wou l d  b e li ke dealing with a n yo n e else outsour ced in  t e rm s ofrel iability.
P art D - I act u al l y sta r ted as a desi gner, and I E  6crushe dmys oul. I  am
s ti l l v ery interes tedin UX tho ugh. I think s t artingas a p rog ram mer, Iwo uld 
j u stt ry  to rec reate de si gn s you  thi n k a re a ppe alin g. Iwould also tr y t o
le a rnthe g rid s yste m.  UseCSS fr amewo rk s as training w heel s that ha veasol id 
grid ,  and d ece nttypogra phy (eg .  Bl ue p r i nt ). I started const ra i n in g myself  to
HT M Lan d  CSS, an dI t hink y ou sh ould to o, leave  Photo s ho palone u nt il you  c anmak e dec e nt d esigns  in just  HTML and CSS. Then, when you arec om p l et e ly
c omf ortable usi ng t h e tw o, t h en  lo o k toPS to  a d dd etails that you can 't 
achie ve ot herwise. Thebig obstac l e you will  run in t o, is that you  will  feel
like you aren 't ma king asgood of d e s igns asdes ign erX.D e si gn in my opin i o n
is  m uch mor e p ersonal  an d e mot ion al  than pro gramming  s odo n' t l et th a t get to 
y ou. 
Goo d Luc k !

--- ---
e arly ri se r 
A)  I star t  w i t h mo ck up s, t hen  t he po lish e d d esign a nd at las t t h e pr og ra mming.For users, th einterfaceis  al l that t hey have , then the UX stuff nee d s to be 
de fined  ver y early ( inmy cas e). I like  37sig nals"e pic e n ter d e s ig n"ap proach.
St a r t w ith t he  mor e impor tant pages and wit h  th e more import ant  inf o r ma tio n 
c h unk so f t h e se pages.

B) u seit.com a nd my  collectio n  ma yb e <http ://www. delic i ous.com /egogol/u i>

C) ha ve  som e o negood for d esign in  your tea m . Ify ou  can' t,exchan ge  yo ur
pr ogramm i nghours  vs de si gn hou rs. I de ally itshould be a collaborati ve
pro cess. 

D ) The imp ort a ntthing isthat  the userget s t he th ing s  done . Th e  U X d e termi ne
h o w the pro g ra mmi n g  p rocess shou l d wor k.

B ONU S ) Test  a l ot. Test your moc k ups, test your  des i g n,tes t  you rrunning app.
E ver ys t ep willre veal differ ent prob le m s.

- -----PhrosT T
I ama pr o gramme r wi thfairly ad van ce d  photos ho p
 well,_that you_would change. Do little_usability
tests on_your_sites, even_on_sites that aren't_yours with family_or peers.

Part C -_I don't know_as_much about startups. I do know that having a designer
on hand is much nicer_to_work with_than_outsourced._Ultimately I think it
would be_like dealing with anyone else_outsourced in_terms of reliability.

Part D - I actually started_as_a designer, and_IE 6 crushed my soul. I am
still very interested_in UX though. I think starting_as a programmer,_I_would
just_try to recreate designs_you think are appealing. I would_also try to
learn the grid system._Use CSS frameworks as training wheels that_have a solid
grid, and decent typography_(eg. Blueprint). I started constraining_myself to
HTML_and CSS, and I think_you should too,_leave Photoshop_alone until you_can
make decent designs in just HTML_and CSS. Then,_when you are completely
comfortable using the_two,_then look to_PS_to_add details_that you can't
achieve_otherwise._The big_obstacle_you will run into, is that_you_will feel
like you aren't making as good_of designs as designer_X._Design in my opinion
is_much more personal and emotional_than programming so don't let that_get to
you.

Good_Luck!

------
earlyriser
A) I_start with mockups, then the polished design and at last the_programming.
For users, the interface is all_that they have, then_the UX_stuff_needs to be
defined_very_early (in_my case). I like 37signals "epicenter design"_approach.
Start with_the more important pages and with_the more important information
chunks_of_these pages.

B) useit.com and my collection_maybe <http://www.delicious.com/egogol/ui>

C) have someone good for_design in your team. If_you_can't,_exchange your
programming hours vs design_hours. Ideally it should be a_collaborative
process.

D) The important_thing is that the user gets the_things_done. The UX determine
how the programming_process_should work.

BONUS) Test a lot. Test_your_mockups,_test your design, test your_running app.
Every step will reveal different_problems.

------
PhrosTT
I am a programmer with fairly advanced photoshop