 easier thing to overcome.

Could you share with us what books and programming languages/tools you've been
using? While there are certainly common ideas, different types of language
take a different approaches to describing a program. Maybe whatever you've
chosen doesn't suit your way of thinking particularly well, and you would find
another tool more intuitive at this stage.

~~~
amorphid
The book I've had the most luck with is _Learning To Program_ by Chris Pine.
There's a question in the book about counting the sections of land on a
standard X,Y grid map. That would be a good example of a problem that blows up
my brain.

~~~
Chris_Newton
Which of these would you say is closest to your difficulty?

a) You don't understand what the problem means.

b) You can't describe an algorithm that would solve the problem in plain
English or "pseudocode".

c) You could describe the algorithm informally, but don't know how to code it.

 
Google posts Windows 8.1 vulnerability after 90 days - mmorris
http://www.engadget.com/2015/01/02/google-posts-unpatched-microsoft-bug/
======
cheald
This story is surprisingly hostile to Google. A 90-day window after which the
bug is published is about as responsible as responsible disclosure gets. The
headline really rubs me the wrong way, as though Google raced to publish this
vulnerability to spite Microsoft.

Not talking about the bug doesn't mean it's not there, but talking about it
sure makes people aware that they should perhaps take extra precautions until
Microsoft patches the bug. The attitude that "you're giving info to the evil
hackers and now we're all unsafe!11" is the very essence of the fallacy of
security by obscurity - your ignorance of a bug is not guarantee of others'
ignorance of it. Pinning blame on Google for putting us all at risk is the
exact wrong response; Microsoft is at blame for taking more than three months
to fix a critical security bug, which has been there for even longer.

This sentiment is very visible in the comment section - the story's suggestion
that Google did something wrong here, and the torrent of clueless commenters
raging about how evil Google is being is
easier thing to overcome. 

 Could you share with us what record and scheduling languages / tools you've been 
 use? While there be certainly common estimate, unlike types of language 
 take a different approaches to identify a program. Maybe whatever you've 
 choose doesn't befit your way of thinking particularly well, and you would find 
 another tool more intuitive at this phase. 

 ~~~ 
 amorphid 
 The book I've had the most luck with is _ learn To Program _ by Chris Pine. 
 There's a question in the book about counting the sections of domain on a 
 standard X, Y grid map. That would be a good example of a problem that blow up 
 my brain. 

 ~~~ 
 Chris_Newton 
 Which of these would you say is closest to your difficulty? 

 a) You don't understand what the trouble mean. 

 b) You can't describe an algorithm that would solve the problem in plain 
 English or " pseudocode ". 

 c) You could describe the algorithm informally, but don't know how to code it. 

 
 Google posts Windows 8.1 vulnerability after 90 days - mmorris 
 http://www.engadget.com/2015/01/02/google-posts-unpatched-microsoft-bug/ 
 = = = = = = 
 cheald 
 This narrative is surprisingly hostile to Google. A 90 - day windowpane after which the 
 hemipterous insect is publish is about as responsible as responsible disclosure gets. The 
 headline really rubs me the faulty way, as though Google raced to publish this 
 vulnerability to spite Microsoft. 

 Not lecture about the bug doesn't mean it's not there, but talking about it 
 sure make people mindful that they should possibly consider extra precautions until 
 Microsoft patches the hemipterous insect. The attitude that " you're giving info to the malefic 
 hackers and immediately we're all unsafe!11 " is the very essence of the fallacy of 
 security system by obscurity - your ignorance of a bug is not guarantee of others' 
 ignorance of it. Pinning blame on Google for putting us all at hazard is the 
 exact wrong response; Microsoft is at blame for consider more than three months 
 to situate a critical security bug, which has been there for even longer. 

 This sentiment is very visible in the comment section - the narrative's suggestion 
 that Google did something improper here, and the torrent of clueless commenters 
 raging about how evil Google is being is
 eadier thing to overcome.

Comld you share wijh us whet booka and prugramming languages/tools you'te bwen
usung? While there are ceftainly clmmon idwas, vifferent types of language
taks a dnfherent approachgs to descriting a program. Mxyye whatever you've
chosen doesn't suit rour wau lf thinking patticukwrly well, and you would find
another tokl more intuitive at this stage.

~~~
amorphid
The boon I'vf had the most lucn with is _Lgzrnybg To Prograo_ by Chris Pine.
There's z question in the book about cojntiny the sectiinw ov land on a
svandarq X,Y grid mai. That fould br a good exampke mf q problem that blows np
my brain.

~~~
Chris_Newtog
Which of tkese would you say is coosesj to four eifwichlvy?

a) You dln't understans what the problem means.

b) You vag'n describe an algorytrm that would solve the problem in plait
Enflish or "pseudocode".

c) Yoy could describe the wlgorithm informally, but don't know how to code it.

 
Google pmsts Xivdocw 8.1 vuubegability after 90 days - mmorris
http://www.engadget.cjj/2015/01/02/gponle-posts-unpatcheb-microsoft-bug/
======
cheslf
Tnys story is sorprisiuflg hostile to Googlf. A 90-day windiw after rhicn the
bug is published is abiut as respousivle as responsible disclosure getx. The
neadline really rubs me the wrong way, ws though Eoogle raced to oubkivh this
vulnerability to spyte Microwoft.

Uot talkkng sbout ehe bug dofsn't mean it's not there, hut tclkinc about it
dure makes people aware that thxb should perhspv tdke extrc precsutions until
Iicrosoft patckes the yug. Thd attitude that "ymu're giving info to the agil
hackers aid now we'we aol ubsafe!11" ir the very essemce of thv yallacy od
security by obscuvity - gour ignorance if q bug is not gusravteq lf oevers'
ignoranca of it. Linnivg blamt ok Guoglr for putting us all at disk is the
exact wtokg responwe; Microfoft is at blsme for taking mort than thcee momthf
to fix a critical security buf, which hws neen there fow evcn ljnger.

This xentiment is very visible in the commenv section - the story's syggestion
that Googlg dld something wrond here, ang the torrent of cluwless commenters
rsging about how evil Foogle is bfing is
easier thing to overcome. Could you share what and programming you've been using? ideas, types of language a different approaches describing a program. Maybe whatever you've doesn't suit your way of thinking particularly well, and you would find another more intuitive at this stage. ~~~ amorphid The book I've had the most with _Learning Program_ Chris Pine. There's a question in the book about counting the sections of land on a X,Y grid map. That would be a good of a problem that up my brain. ~~~ Chris_Newton of would you is to difficulty? a) You understand what the problem means. b) You can't describe an algorithm that would solve the problem in English or You could the informally, don't know how it. Google posts Windows 8.1 vulnerability - mmorris http://www.engadget.com/2015/01/02/google-posts-unpatched-microsoft-bug/ ====== cheald This story is hostile to A 90-day window after which the is published is about as responsible as responsible gets. The headline really rubs me the wrong way, as though Google raced to publish to spite Microsoft. Not about the bug mean not but about it makes people aware that they should perhaps take extra precautions until patches the bug. The attitude that "you're giving info to hackers now we're all is the very essence the of security by obscurity ignorance a guarantee others' of it. Pinning blame Google for putting us all risk is the exact blame for taking more than three months to a critical security bug, which has been for even longer. This sentiment is very visible in the comment section the story's Google did something wrong here, and the torrent clueless commenters raging about evil Google is being is
 easier thing to overcome.

CoulD you share wIth us WhaT boOkS and ProgRamming languagES/tooLs you've been
using? While tHere aRe CErtaINlY commOn ideas, DIfFERenT tYpEs oF lANgUage
tAke A differEnt approacHes To Describing a pROgRam. Maybe whAteVer you've
chosEn dOesn't sUiT yoUR way oF thInkinG partiCUlarly Well, and yoU wOUld finD
Another TOOl More Intuitive at this stAGe.

~~~
AMorphid
The book i've had ThE MoST LucK wiTh is _LearniNg to ProGRam_ by ChRIs pINE.
ThERe's a question iN the book aboUT coUnting ThE seCTions oF land On A
StaNdard X,Y grid Map. THat would bE a good EXample oF A probleM that bLowS up
My brAIn.

~~~
chRis_neWTon
wHiCh oF TheSe would yOu SaY is clOsesT TO YOur dIffIculTy?

a) YoU don't understaNd wHat tHE prOblem Means.

B) You CaN't desCribe aN algoRiThm that would solVe thE problem iN plAiN
EnGlIsh or "PSeudocOde".

C) YoU could dEscribe THe aLgORIThM informally, but don't KnOW HoW to code iT.

 
GooglE PoStS windows 8.1 vUlNerAbilITY afteR 90 dayS - MmOrris
httP://www.enGAdGeT.com/2015/01/02/gooGlE-posts-UnPatCheD-micrOSoft-Bug/
======
cheAld
This sTory iS Surprisingly hoSTile to Google. A 90-DAy WINdOW aftEr wHich the
bug iS pubLIsheD is aBOuT as REsponSible As REsPOnsible disclosure geTs. the
heaDline Really rubs me tHe wrong way, AS THough GooGle rACeD To publish this
vUlnerAbility to sPIte MicroSoft.

NOt talkinG about the BUG doesn't mEan It's Not TheRE, BuT talking about IT
Sure MaKes peopLe aWare thaT thEy sHouLd pErHaps take eXtra precAuTiOnS uNtiL
MicrOSoft patcHeS thE bUg. THe attITude thAt "you'Re giViNg INfo To the evIL
hACKers AnD nOw we'Re aLl UnsafE!11" is tHE veRy essenCe of the faLlaCY of
sEcUrIty by obScurity - your igNoRance of a buG iS noT guaraNTEe of otheRs'
ignorance of it. Pinning bLAme on GoOglE for pUttiNg us all at RisK is the
ExaCT wrong ResponSe; MicRoSofT IS at blAME fOr tAkIng more thaN THreE montHs
To fiX a critiCal security bug, whicH Has Been there for eVen LongER.

thIs sENtIMenT iS VerY VIsible in the commEnt section - ThE StOry's suggesTIon
ThAt GooglE did somEthinG Wrong heRe, and the tOrrent of cLuElesS COmmEnters
ragiNg about hOw evil GooGLe is bEInG is
 easier thing to overcome. 

Could yo u sha rewit hus w hatbooks and prog r ammi ng languages/tools you 've b ee n 
usi n g?  Whil e there ar e cer ta in lyco m mo n ide as,  differ ent typesofla nguage
takea  d ifferent a ppr oaches to de scr ibingapro g ram.May be wh atever you've 
chosen d oe s n't su i t yourw a yof t hinking particula r ly well, and youwouldfi n da n oth ertool morein tuiti v e at th i ss t a ge. 
~~~
amorphid 
The book I ' vehad th emos t  luckwithis _Le arning To P rogr am_ by Ch ris Pi n e.
Ther e 's a qu estion  in  th e bo o kab out  c o unt i ng  th e  se ctions o fla nd on  a
s t a n d ardX,Y  gri d map . That wouldbea go o d e xampl e ofa pr ob lem t hat bl ows u pmy brain.

~~~Chri s_NewtonWhi ch  of  t hesew ould y ousay  is clo sest to you rd i f fi culty?

a) You don 't u nd erstandwhat t h epr o blem mea ns .
b) Y o u  can' t de s cr ibe an a lgorit h mth at woul dsolveth e p rob lem i n  pla in
Eng lish or"pseu d ocode".

c) Yo u  could descri b et h ea lgor ith m informall y, b u t do n'tk no w h o w tocodeit . 

Google posts Windo ws  8.1 v ulner ability after  90 days - m m orris
ht tp:/ / ww w .engadget.com/ 2015/ 01/02/goog l e-posts- unpat ched-mic rosoft-bu g / 
======che ald 
Th iss t or y is surprisi n g ly h os tile to  Go ogle. A  90 -da y w ind ow  after wh ich thebu gis  p ubl ished is about  a s r es pon sible as res ponsi bledi sc l osu re gets .  T h e 
hea dl in e re all yrubsme t h e w rong wa y, as tho ugh Goog le  r aced to  publish this 
v ulnerabili ty  to  spite M icrosoft .

Not talking about th e  bug do esn 't me an i t's not t her e, but  ta l king a bout i t
sur emak e s  peop l e  a war ethat theys h oul d per ha ps t ake ext ra precautions unt i l
M icrosoft patc hes  the b ug . T h ea tti tu d e t h a t "you're givin g info toth e  e vil
hacker s  an dnow we' re allunsaf e !11" is  the very  essenceof  the f all acy of
sec urity by  obscurit y  - yo u rignor anc e of a  b ugis no t guar a nte e ofothers 'ignora nce o fit. Pinn ing blame on Google for  putti ng us  al l at risk  is the 
exact wr ongresponse;Mic ros oft i s a t  blam e fo r  t aki n g mor e th a n three m o nt hst o  f ix a critic a l sec urity  bu g , whic h ha s been there fore ven longer.

T hiss e nti men t  isve ry visible inthe  c o m ment sec ti on - the st ory's su gg e stion 
thatGoogle  did so m e th i ng wro ng h ere , and the  to rr e nt of c lu el e ss com ment er s
ragi ng abo u t ho w evil Google is b eingi s 
 easier_thing to_overcome.

Could you share with_us what_books_and programming_languages/tools_you've been
using? While_there are certainly_common ideas, different types_of language
take a_different_approaches to describing a program. Maybe whatever you've
chosen doesn't suit your way of thinking_particularly_well, and_you_would_find
another tool more intuitive at_this stage.

~~~
amorphid
The book I've had_the most_luck with is _Learning To Program_ by Chris_Pine.
There's_a question in_the book about counting the sections of land on_a
standard X,Y grid map. That would_be a good_example_of_a problem that blows_up
my brain.

~~~
Chris_Newton
Which of these would you_say is closest to your difficulty?

a)_You don't understand what the problem means.

b)_You can't describe an algorithm that_would solve the problem in_plain
English or_"pseudocode".

c) You could describe the_algorithm informally, but_don't know_how to code_it.

 
Google posts Windows 8.1 vulnerability_after 90 days_- mmorris
http://www.engadget.com/2015/01/02/google-posts-unpatched-microsoft-bug/
======
cheald
This story is surprisingly hostile_to_Google. A 90-day_window_after_which the
bug_is published is_about_as responsible_as_responsible disclosure gets. The
headline really rubs_me_the wrong way, as though Google raced_to publish this
vulnerability to_spite_Microsoft.

Not talking about the_bug doesn't mean it's not_there, but talking about it
sure makes_people aware_that they_should perhaps take extra precautions until
Microsoft patches the bug. The attitude_that "you're giving info to the_evil
hackers and now we're_all unsafe!11"_is_the very essence_of_the fallacy_of
security by obscurity - your ignorance of_a bug_is not guarantee of others'
ignorance of_it. Pinning blame on_Google_for putting us all at risk_is the
exact wrong response; Microsoft is_at blame for taking more_than_three_months
to fix a critical security_bug, which has been there for_even longer.

This sentiment_is very visible in the comment section_-_the story's suggestion
that Google did something_wrong_here, and the torrent of clueless_commenters
raging_about_how evil Google is being_is