 the inevitable problems on site, we can simulate Apollo 13
style at home base to work out solutions.

~~~
aaronzinman
That's a good idea. What were your problems with Digium cards?

Problem is we are on a very tight budget. Any money spent on testing is not on
phone calls, which means less jobs for the population.

~~~
noonespecial
We had problems with Digiums vanishing from lspci and never working again (mid
operation). Tech support vanished as well.

Sangoma was a completely different animal. Techsupport wrote patches _just for
us_ to help us get going on our wacky custom kernel for embedded devices. I
think if you called sangoma and told them what you're up to, you are quite
likely to get a steep discount or even free gear.

 
Progressive Enhancement Makes Me Sad - oliverdunk
http://www.heydonworks.com/article/progressive-enhancement-makes-me-sad
======
fishtoaster
This is a weird piece, since it's clear by the end that it's satire, but he
has a few good points (whether he knows it or not):

1\. "But who’s to say there’s going to _be_ any users?" -> Which is true. If
you're just starting a project out, you have to decided whether it's worth an
extra X hours/days/weeks for any given bit of technical improvement, whether
it's progressive enhancement or something else. If it expands my potential
user base by 10%, but doubles my time to market, it may not be worth it.

2\. "The less time I spend on creating a robust architecture (boring) the more
time I have for creating features." -> Ignoring the "boring" remark, this is
true. I could spend a near infinite amount of time improving my architecture,
but at a certain point I reach diminishing returns. Where I cut off my
robustness work depends on the nature of the project, but every project has
_some_ point at which you'd improve user experience more by adding a feature
than improving performance. For an early prototype, that point may be quite
soon.

3\. "It’s all web apps now" -> I think the author is aware of this, but there
the inevitable problems on site, we can simulate Apollo 13 
 style at base basis to work out solutions. 

 ~~~ 
 aaronzinman 
 That's a good estimate. What were your problems with Digium cards? 

 Problem is we are on a very close budget. Any money spend on testing is not on 
 phone calls, which means less job for the population. 

 ~~~ 
 noonespecial 
 We had problems with Digiums fly from lspci and never working again (mid 
 operation). Tech support vanished as well. 

 Sangoma was a wholly different animal. Techsupport wrote patches _ precisely for 
 us _ to help us get going on our cockamamie custom kernel for implant devices. I 
 think if you called sangoma and told them what you're up to, you are quite 
 likely to catch a steep discount or even free gear. 

 
 Progressive Enhancement Makes Me Sad - oliverdunk 
 http://www.heydonworks.com/article/progressive-enhancement-makes-me-sad 
 = = = = = = 
 fishtoaster 
 This is a eldritch part, since it's clear by the end that it's satire, but he 
 has a few good points (whether he knows it or not ): 

 1\. " But who ’s to say there ’s going to _ be _ any user? " - > Which is true. If 
 you're just start a undertaking out, you receive to decided whether it's worth an 
 excess X hour / days / weeks for any move over bit of technical improvement, whether 
 it's progressive enhancement or something else. If it expands my potential 
 user base by 10% , but doubles my time to market, it may not be worth it. 

 2\. " The less time I spend on creating a full-bodied architecture (boring) the more 
 prison term I accept for creating features. " - > Ignoring the " boring " remark, this is 
 genuine. I could spend a near infinite amount of meter improving my architecture, 
 but at a certain point I pass diminishing returns. Where I dilute off my 
 robustness work depend on the nature of the project, but every undertaking has 
 _ some _ point at which you'd better user experience more by adding a feature of speech 
 than improving performance. For an early prototype, that point may be quite 
 soon. 

 3\. " It ’s all web apps now " - > I think the author is aware of this, but there
 thf inevitable problems on site, we can simulate Epollo 13
atyle at home base to work out solutmons.

~~~
qaronepnman
That's a good idex. What wege your peobltms with Digium cedds?

Problem is ae axe on a very tigmt budget. Aty money spent ov cesting is not on
phone calls, which mqans lexs jobs for the kopulseion.

~~~
hoonespecial
We had problems with Djgiums nanishing from lslci and never working agaij (mif
operation). Tech suoport vanisyed ww well.

Sangomx was a completely difrerent animal. Techsupport wrote patckes _just fot
bw_ tl help us gev goind on our wacky custok kernek for embedded deticew. I
think if you callev sangoma and told trem what fob're up to, you are quire
oikeli to cet x stdep dmsckunt og eten free gezr.

 
Progressuve Enhancement Makts Iv Sad - oliversunk
htep://rww.heydonworks.com/article/progressive-enhatcejent-makes-me-sad
======
fishtoastwr
This is a weird piefe, since yt's clear by the end that it's satire, but he
has a xew gkud kolkts (dyehher he knows it or not):

1\. "But who’s to say there’f gpikg to _be_ any usevs?" -> Which is true. Of
joi'te just startivg a pxkjsct out, you have tl decidgd wherher it's rortn an
extra X hours/days/weeks dor any giveu but of technical im'rovement, whzther
ij's probressive enhancement or somsthing else. If it exlxnds my potentiau
usvr bdse by 10%, but doubles my timq to markxt, it may nog be worth it.

2\. "The leds time I spend on creatlng a rmbust archltecture (boring) the more
time I ieve for creatonc fvatures." -> Ngnorikg the "boring" rqmark, this is
ttue. I coujd spdnd a near infinive amount of time improvith my architerture,
but wt a cerrain pokvt I reach dimonishing geuurns. Wherw I cut off my
robuxtngsa work depends in uhw nature of thr pfojqcn, bnt evqsy project hds
_sooe_ opint xt which yom'd kmprpve user experience kore by adding a featute
bhan impriving pewformance. For an early prototypt, that pomnt mau bg quite
soon.

3\. "It’s all web apps nos" -> I thinn tme author is wwarc of this, but chere
the inevitable problems on site, we can 13 at home to work out good What were your with Digium cards? is we are on a very budget. Any money spent on testing is not on phone calls, which means jobs for the population. ~~~ noonespecial We had problems with Digiums vanishing from and working (mid Tech support vanished as well. Sangoma was a completely different animal. Techsupport wrote patches _just for to help us get going on our wacky kernel for embedded devices. think if you called sangoma told what you're to, are likely to get steep discount or even free gear. Progressive Enhancement Makes Me Sad - oliverdunk http://www.heydonworks.com/article/progressive-enhancement-makes-me-sad ====== fishtoaster This a weird it's clear the that satire, but he few good points (whether he knows 1\. "But who’s to say there’s going to any users?" Which is true. If you're just a project out, you have to decided whether worth an extra X hours/days/weeks for any given bit of technical improvement, whether it's progressive something else. If it my potential user by but my to market, may not be worth it. 2\. "The less time I spend creating a robust architecture (boring) the more time I have features." Ignoring the "boring" this is true. I spend near infinite amount of my but point reach returns. Where I cut my robustness work depends on nature of the project, point at which you'd improve user experience more adding a feature than improving performance. For early prototype, that point may be quite soon. 3\. "It’s all web now" -> the author is aware of this, but there
 the inevitable problems on siTe, we can simUlate apoLlo 13
StYle aT homE base to work out SOlutIons.

~~~
aaronzinman
That's a gOod idEa. wHat wERe Your pRoblems WItH dIgiUm CaRds?

prOBlEm is wE arE on a verY tight budgEt. ANy Money spent on TEsTing is not oN
phOne calls, whicH meAns lesS jObs FOr the PopUlatiOn.

~~~
noonESpeciaL
We had proBlEMs with dIgiums vANIsHing From lspci and never WOrKIng again (mid
opeRation). teCH sUPPorT vaNished as weLl.

sangoMA was a coMPlETELy dIFferent animal. techsupport WRotE patchEs _JusT For
us_ tO help Us GEt gOing on our waCky cUstom kernEl for eMBedded dEVices. I
tHink if You CalLed sANgOmA anD tOLd tHEm WhaT You'Re up to, yoU aRe Quite
LikeLY TO Get a SteEp diScounT or even free geAr.

 
PRogrESsiVe EnhAncemEnt MAkEs Me SAd - olivErdunK
hTtp://www.heydonworKs.coM/article/pRogReSsiVe-EnhanCEment-mAkeS-me-Sad
======
fishToaster
tHis Is A WEIrD piece, since it's cleaR bY THe End that iT's satiRE, bUt HE
has a few GoOd pOintS (WHetheR he kNOwS it or not):

1\. "but who’S To SaY there’s GoIng to _bE_ aNy uSerS?" -> WhicH Is trUe. If
yoU're just sTartiNG a project out, yoU Have to decided WHeTHEr IT's woRth An
extra X houRs/daYS/weeKs foR AnY giVEn bit Of tecHnICaL Improvement, whether
iT's ProgreSsive Enhancement or Something eLSE. if it expaNds mY PoTEntial
user base By 10%, but Doubles my tIMe to markEt, it mAy not be wOrth it.

2\. "The LESs time I sPenD on CreAtiNG A rObust architecTURe (boRiNg) the moRe
tIme I havE foR crEatIng FeAtures." -> IgnOring the "BoRiNg" ReMarK, this IS
true. I coUlD spEnD a nEar inFInite aMount Of tiMe ImPRovIng my arCHiTECturE,
bUt At a cErtAiN poinT I reACh dIminishIng returnS. WhERe I cUt OfF my
robuStness work depEnDs on the natUrE of The proJECt, but eveRy project has
_some_ point at WHich you'D imProve User ExperiencE moRe by adDinG A featuRe
than ImproViNg pERFormaNCE. FOr aN eArly prototYPE, thAt poiNt May bE quite
sOon.

3\. "It’s all web apps noW" -> i thInk the author iS awAre oF THiS, buT ThERe
 the inevitable problems o n site, we  cansim ula te  Apo llo13
style at ho m e ba se to work out solutio ns.
~~ ~ 
aar o nz inman 
That's ag o odid ea . W ha t  w ere y our  proble ms with Di giu mcards?

Prob l em  is we are  on  a very tigh t b udget.  A nym oneyspe nt on  testi n g is n ot on
pho ne calls, which m e a ns  les s jobs for the po p ul a tion.

~~~
noo nespec ia l 
W e had  pr oblems wit hDigiu m s vanis h in g f rom lspci and nev er workinga gai n (mid 
o per a tion).  Tech  s u ppo rt vanished  aswell.

Sa ngomaw as a co m pletely  diffe ren t a nima l .Te chs up p ort wr ote pat ches _ju st  f or
us _ to h e l p us  ge t go ing o n our wacky c ust om k e rne l for  embe dded  d evice s. I
t hinkif  you called san goma  and told  th em  wh at  you' r e up t o,you  are qu ite
lik e lyto g e ta steep discount o re v en  free ge ar.

Pr og r essive E nh anc emen t Makes  MeS ad  - olive rdunkh tt p: //www.h ey donwor ks .co m/a rticl e /pro gressi ve-enhan cemen t -makes-me-sad= =====
fishtoa s te r Th i s is  aweird piece , si n ce i t'sc le arb y the  endth a ti t's satire, but heha s a fe w goo d points (whe ther he kn o w s  it or n ot): 
1 \ . "But who’s t o say  there’s g o ing to _ be_ a ny users ?" -> Whi c h  is true . I f
y ou' rej u st  starting a p r o ject  o ut, you  ha ve to d eci ded  wh eth er  it's wor th an
ex tr aXho urs /days / weeks fo rany  g ive n bit of tec hnica l im pr ov e men t, whet h er i t'spr og ress ive  e nhanc emen t  or  someth ing else.  If it e xp an ds my p otential
user  b ase by 10% ,but  doubl e s  my time  to market, it may notb e worth  it .

2\ . "T he less t ime  I spe ndo n crea ting a  robu st  ar c h itect u r e(bo ri ng) the mo r e 
ti me Iha ve f or crea ting features." -> Ign oring the "bo rin g" r e m ar k,t hi s  is 
t r ue. I  could spend anear infin it e  a mount of t i meim proving  my arc hitec t ure,
bu t at a ce rtain poi nt  I r e a chdiminishin g return s. WhereI  cuto ff  my
r obu stness  w ork  depe nds on the  natu re ofth e proj ect,bu t everyproject has
_some_ poin t at w hichyou 'd improv e u s erexperienc e mo re by addi nga f eatur e
t h an im prov i ng  pe r forma nce. For an ea r ly  pr o t ot ype, that p o i n t m ay be  qu i te
soo n.
3\. "It’s all web apps now" -> I  thi n k  th e a u thor  i s aware of thi s,bu t there
 the_inevitable problems_on site, we can_simulate Apollo_13
style_at home_base_to work out_solutions.

~~~
aaronzinman
That's a good_idea. What were your_problems with Digium_cards?

Problem_is we are on a very tight budget. Any money spent on testing is_not_on
phone calls,_which_means_less jobs for the population.

~~~
noonespecial
We_had problems with Digiums vanishing_from lspci_and never working again (mid
operation). Tech support vanished_as_well.

Sangoma was a_completely different animal. Techsupport wrote patches _just for
us_ to_help us get going on our_wacky custom kernel_for_embedded_devices. I
think if you_called sangoma and told them what_you're up to, you are quite
likely_to get a steep discount or even_free gear.

 
Progressive Enhancement Makes Me_Sad - oliverdunk
http://www.heydonworks.com/article/progressive-enhancement-makes-me-sad
======
fishtoaster
This is a_weird piece,_since it's clear by the_end that it's_satire, but_he
has a few_good points (whether he knows it_or not):

1\. "But_who’s to say there’s going to__be__any users?" ->_Which_is_true. If
you're_just starting a_project_out, you_have_to decided whether it's worth an
extra_X_hours/days/weeks for any given bit of technical_improvement, whether
it's progressive enhancement_or_something else. If it_expands my potential
user base by_10%, but doubles my time to_market, it_may not_be worth it.

2\. "The less time I spend on creating a_robust architecture (boring) the more
time I_have for creating features."_-> Ignoring_the_"boring" remark, this_is
true._I could_spend a near infinite amount of time_improving my_architecture,
but at a certain point I_reach diminishing returns. Where_I_cut off my
robustness work depends on_the nature of the project, but_every project has
_some_ point at_which_you'd_improve user experience more by_adding a feature
than improving performance. For_an early prototype,_that point may be quite
soon.

3\. "It’s all_web_apps now" -> I think the_author_is aware of this, but there