 work - always seems a minefield

------
supremeanger
I buy and sell HN Karma as an investment. So far im looking at about 40% ROI

~~~
Rainymood
Could you elaborate on this? I'm really curious...

 

Your hard drive is too big - stefankendall
http://www.stefankendall.com/2011/12/17/your-hard-drive-is-too-big/

======
bunderbunder
Unnecessarily trollish.

A 1TB, 7200RPM drive costs like 100 bucks nowadays. At that price being able
to store large amounts of crap is hardly a giant waste. Half the folks I know
have burned that much money on collecting cases for their iPhones. For that
matter, it might not even be necessary. Me, I've got a couple big disks,
because my test data sets alone consume nearly a terabyte.

Second, I agree that having an SSD can be really beneficial. Which is why I
got one. But that doesn't imply that the presence of a 1TB drive is harmful.
It's absolutely OK to have both. Even a good idea, since they have different
strengths. SSDs certainly have great bandwidth and latency, but price per gig
is another metric that's worth considering.

For that matter, if most the work you're doing is CPU-bound and the software
you work on already compiles in a second or two, there's a chance that an SSD
doesn't really provide much value anyway. Booting might take longer, but any
reduction in boot time below how long it takes to get my morning coffee is
meaningless.

~~~
stefankendall
Price per GB is a crap metric; price per _used_ GB would be more relevant. If
your test data is terabytes, you externalize to servers or lock yourself into
only being able to work off a desktop. I also question whether or not a subset
of that data could be run locally, and the CI system could run a full stack.

This just sounds like a justification of a bad test environment.

I also can't think of any project that compiles "in a second or two".
Compilation and tests usually run build time into the minutes quickly, and
time grows linearly, or possibly superlinearly with a project
work - always seems a minefield 

 ------ 
 supremeanger 
 I buy and deal HN Karma as an investing. So far i m looking at approximately 40% ROI 

 ~~~ 
 Rainymood 
 Could you complicate on this? I'm really curious... 

 

 Your hard driveway is besides big - stefankendall 
 http://www.stefankendall.com/2011/12/17/your-hard-drive-is-too-big/ 

 = = = = = = 
 bunderbunder 
 Unnecessarily trollish. 

 A 1 TB, 7200RPM campaign costs like 100 bucks nowadays. At that monetary value being able 
 to store large amounts of crap is hardly a elephantine waste. Half the folks I know 
 have burn that much money on collecting cases for their iPhones. For that 
 topic, it might not even be necessary. Me, I've got a couple big disks, 
 because my examination data sets entirely consume closely a terabyte. 

 Second, I agree that own an SSD can be really beneficial. Which is why I 
 got one. But that doesn't imply that the bearing of a 1 TB drive is harmful. 
 It's absolutely OK to have both. Even a good idea, since they have unlike 
 lastingness. SSDs certainly have great bandwidth and latency, but price per gig 
 is another metric that's worth considering. 

 For that topic, if most the employment you're doing is CPU - tie down and the software 
 you make on already compiles in a second or two, there's a chance that an SSD 
 doesn't really provide much value anyhow. Booting might take longer, but any 
 reduction in boot time below how long it accept to get my morning coffee is 
 meaningless. 

 ~~~ 
 stefankendall 
 Price per GB is a crap metric; price per _ used _ GB would be more relevant. If 
 your test data is terabytes, you externalize to server or lock yourself into 
 merely being able to work off a desktop. I also question whether or not a subset 
 of that data could be tend locally, and the CI system could run a full smokestack. 

 This just sounds like a justification of a bad test environment. 

 I besides can't think of any project that compiles " in a second or two ". 
 Compilation and tests usually carry build clock time into the minutes promptly, and 
 time grow linearly, or possibly superlinearly with a project
 wogk - always seems a minefleld

------
supremeanger
N buy aid sell HN Karmx as an investment. So far im liokint at about 40% ROI

~~~
Rainymoud
Could ylu elaboeate in this? I'm really gbrioua...

 

Youx iard drive is tpo big - stafankendall
htt[://wdw.dtefankendall.com/2011/12/17/your-hard-drive-is-too-byg/

======
bundetbknder
Unnecessatily urojlisg.

A 1TB, 7200RPM drive costs like 100 bucks howadayv. At that prive being able
to store largf amlunts of crap is hwrdly a giabt wwwte. Half the folks I know
have burngd that much money on collecting casex for theit jPjmnes. For thet
mattvr, it might not even te necexsary. Me, I've gpt e coyple big disks,
because my test data sets alone cotsbme nearly a terabyte.

Wexond, H agsee gyat habiig zn SSD cai be really beneficial. Which is why I
got pnq. But that doean't im[lr that the presence of a 1TB drive is hagmfum.
It's absolutely OK to hqve both. Even a good ldea, sincq they have different
strengths. SSDs certainly hava greet bauewidtf ajd latency, but price per gig
is another metric fhst'x worth considcring.

For that mattrr, ig most the wory you'rz dking is CPU-bound ajd the foftwqre
you wowk om already compiles in a secind or two, tkerw's a chance that au SSD
doesn't xeally provode much value anyway. Buotihg might tane longer, cut any
reduction in bmot time below how long it takes to get my morving coffeq is
meaninhless.

~~~
stefankendall
Price oer GY is d crap metgic; price per _used_ GB would be more relevant. Of
foug test daca is berabytes, you evternalize to xervers or luck yoursemf into
mnly being wble to work mvf a desktop. I also zuesrion whethef or not a subsrt
of that data coule be run locally, akd thg DI system could rub a full stack.

Tnis juft spuggs like a juvtifkcagoon ow a bad tesb evvirpnment.

I also can't thhnk kf any project thay gompiles "un a secjnd or two".
Comlilation and tests usuanly run nuijd time into the minutes quickmy, and
timf gvows linearly, or iossybly superkinearly with a project
work - always seems a minefield ------ buy sell HN as an investment. about ROI ~~~ Rainymood you elaborate on I'm really curious... Your hard drive too big - stefankendall http://www.stefankendall.com/2011/12/17/your-hard-drive-is-too-big/ ====== bunderbunder Unnecessarily trollish. A 1TB, 7200RPM drive like 100 bucks nowadays. At that price being able to store large amounts crap hardly giant Half the folks I know have burned that much money on collecting cases for their iPhones. that matter, it might not even be necessary. I've got a couple disks, because my test data alone nearly a Second, agree having an SSD be really beneficial. Which is why I got one. But that doesn't imply that the presence of 1TB drive It's absolutely to both. a good idea, have different strengths. SSDs certainly have latency, but price per gig is another metric worth considering. that matter, if most the work doing is CPU-bound and the software you work already compiles in a second or two, there's a chance that an SSD doesn't really value anyway. Booting might longer, but any in time how it takes get my morning coffee is meaningless. ~~~ stefankendall Price per GB a crap metric; price per _used_ GB would be more your data is terabytes, externalize to servers or yourself only being able to a I or a of that data could run locally, and the CI could run a full a justification of a bad test environment. I can't think of any project that compiles a second or two". Compilation and tests usually run build time into minutes quickly, grows linearly, or possibly superlinearly with a project
 work - always seems a minefield

------
SupremeangEr
I buY anD seLl hN KaRma aS an investment. SO Far iM looking at about 40% ROI

~~~
RainYmood
coULd yoU ElAboraTe on thiS? i'm REAllY cUrIouS...

 

YOUr Hard dRivE is too bIg - stefankeNdaLl
Http://www.stefaNKeNdall.com/2011/12/17/yoUr-hArd-drive-is-toO-biG/

======
bundeRbUndER
UnneCesSarilY trollISh.

A 1TB, 7200RpM drive coStS Like 100 buCKs nowadAYS. AT thaT price being able
to SToRE large amounts oF crap iS hARdLY A giAnt Waste. Half tHe Folks i Know
havE BuRNED thAT much money on cOllecting caSEs fOr theiR iphoNEs. For tHat
maTtER, it Might not eveN be nEcessary. ME, I've goT A couple BIg disks,
BecausE my TesT datA SeTs AloNe COnsUMe NeaRLy a Terabyte.

seCoNd, I agRee tHAT HAvinG an sSD cAn be rEally beneficiAl. WHich IS whY I
got One. BuT thaT dOesn't Imply tHat thE pResence of a 1TB driVe is Harmful.
It'S abSoLutElY OK to HAve botH. EvEn a Good ideA, since tHEy hAvE DIFfErent
strengths. SSDs CeRTAiNly have gReat baNDwIdTH and lateNcY, buT priCE Per giG
is aNOtHer metriC that's WOrTh ConsideRiNg.

For tHaT maTteR, if moST the Work yoU're doing Is CPU-BOund and the softWAre
you work on aLReADY cOMpilEs iN a second or tWo, thERe's a ChanCE tHat AN SSD
dOesn't ReALlY Provide much value anyWaY. BootiNg migHt take longer, bUt any
reducTION in boot tIme bELoW How long it takes To get My morning cOFfee is
meAningLess.

~~~
stefAnkendall
pRIce per GB Is a CraP meTriC; PRiCe per _used_ GB woULD be mOrE relevaNt. IF
your teSt dAta Is tEraByTes, you extErnalize To SeRvErS or Lock yOUrself inTo
OnlY bEinG able TO work oFf a deSktoP. I AlSO quEstion wHEtHER or nOt A sUbseT
of ThAt datA couLD be Run locaLly, and the cI sYStem CoUlD run a fuLl stack.

This juSt Sounds like A jUstIficatION of a bad tEst environment.

I also can't THink of aNy pRojecT thaT compiles "In a Second Or tWO".
CompiLation And teStS usUALly ruN BUiLd tImE into the miNUTes QuickLy, And
tIme growS linearly, or possiblY SupErlinearly witH a pRojeCT
 work - always seems a min efield

-- ----sup rem ea nger 
I b uy and sell HN Karm a as an investment. So  farim look i ng  at a bout 40 %  R O I 

~ ~~ 
R ain ym o od 
Coul d y ou elab orate on t his ?I'm really c u ri ous...

 
Yo ur hard driv e i s toobi g - stefa nke ndall 
http: / /www.s tefankend al l .com/2 0 11/12/1 7 / yo ur-h ard-drive-is-too- b ig / 

======
bunde rbunde rU nn e c ess ari ly trollis h. 

A 1 T B, 7200 R PM d r ive costs like 10 0 bucks now a day s. Atth atp rice b eingab l e
t o store lar ge a mounts of  crapi s hardl y  a gian t wast e.Hal f th e  f ol ksIk now ha veb urn ed thatmu ch  mone y on c o l lect ing  cas es fo r their iPhon es.  For tha t
mat ter,it m ig ht no t even  be n ec essary. Me, I'v e go t a coupl e b ig  di sk s,
be c ause m y t est  data s ets alo n e c on s u m enearly a terabyte. 
S e co nd, I ag ree th a tha v ing an S SD  ca n be r eally  ben e fi cial. Wh ich is wh yI
got o ne . Butth atdoe sn'ti mply  thatthe pres enceo f a 1TB drivei s harmful.
It ' sa b so l utel y O K to have b oth. Even  a g o od  id e a, si nce t he y  h a ve different
streng th s. SSD s cer tainly have g reat bandw i d t h and la tenc y ,b ut price per g ig
is  another m e tric tha t's w orth con sidering. For that  ma tte r,ifm o st  the work you ' r e do in g is CP U-b ound an d t hesof twa re 
you work  on alre ad yco mp ile s ina  secondor  tw o,  th ere's a chan ce th at a nSS D 
do esn't r e al l y  pro vi de  muc h v al ue an yway .  Bo oting m ight take  lo n ger,  b ut  any
re duction in bo ot  time belo whow  longi t  takes t o get my morning coffee is
mean ing less. 

~~ ~
stefank end all
Pr ice per GB  is acrapme tri c ;  pric e pe r _ us ed_ GB wou l d  be  more  r elev ant. If 
your test data is ter abytes, you e xte rnal i z etos er v ers  o r  lo c k  yourself intoonly being  a b le  to work o f f a  d esktop.  I also  ques t ion whe ther or n ot a subs et 
oft h atdata could  be runlocally,a nd th e  C I sys tem  could  r una ful l stac k .
Thisjust s ou nds li ke aju stificat ion of a bad test envir onment .

Ials o can't t hin k  of  any proj ectthat compi les  "i n a s eco n d ortwo" . 
C omp i latio n an d  tests us u al lyr u nbuild timei n t o t he mi nut e s quic kly,  and
time grows l i nearly, or pos sibl y sup erl i near ly  with a projec t
 work_- always_seems a minefield

------
supremeanger
I buy_and sell_HN_Karma as_an_investment. So far_im looking at_about 40% ROI

~~~
Rainymood
Could you_elaborate on this?_I'm_really curious...

 

Your hard drive is too big - stefankendall
http://www.stefankendall.com/2011/12/17/your-hard-drive-is-too-big/

======
bunderbunder
Unnecessarily trollish.

A 1TB, 7200RPM drive_costs_like 100_bucks_nowadays._At that price being able
to_store large amounts of crap_is hardly_a giant waste. Half the folks I know
have_burned_that much money_on collecting cases for their iPhones. For that
matter, it_might not even be necessary. Me,_I've got a_couple_big_disks,
because my test data_sets alone consume nearly a terabyte.

Second,_I agree that having an SSD_can be really beneficial. Which is why_I
got one. But that doesn't imply_that the presence of a_1TB drive_is harmful.
It's absolutely OK to_have both. Even_a good_idea, since they_have different
strengths. SSDs certainly have great_bandwidth and latency,_but price per gig
is another metric_that's_worth considering.

For that_matter,_if_most the_work you're doing_is_CPU-bound and_the_software
you work on already compiles in_a_second or two, there's a chance that_an SSD
doesn't really provide_much_value anyway. Booting might_take longer, but any
reduction in_boot time below how long it_takes to_get my_morning coffee is
meaningless.

~~~
stefankendall
Price per GB is a crap metric; price per__used_ GB would be more relevant._If
your test data is_terabytes, you_externalize_to servers or_lock_yourself into
only_being able to work off a desktop._I also_question whether or not a subset
of_that data could be_run_locally, and the CI system could_run a full stack.

This just sounds_like a justification of a_bad_test_environment.

I also can't think of_any project that compiles "in a_second or two".
Compilation_and tests usually run build time into_the_minutes quickly, and
time grows linearly, or_possibly_superlinearly with a project