Good reading for self-taught programmers?
-
@Gąska said in Good reading for self-taught programmers?:
@Arantor I distinctly remember this feature being touted as the latest and greatest in browser technology that makes everything faster, no more than 10 years ago.
Either your clock is running slow, or it's yet another occurrence of the constant reinvention of the wheel:
iCab, Mozilla Application Suite, and WebTV are the first referenced browsers to support link prefetching.
Browsing using a Google Web Accelerator [released in May 2005]
-
@Watson said in Good reading for self-taught programmers?:
So the Justification Problem shifts to trying to relate these features to the real-world things that the network is supposed to be making decisions about, and explaining why they're as relevant as they're deemed to be in the context that they're being used.
Worse, as soon as the network gets a reasonable number of layers, they're features of a high-dimensional abstract vector space. Explaining them is intensely difficult. OTOH, the first few layers recognise stuff that is incredibly simple, so it is not all impossible. Just hard. (You probably get rotation-independent features somewhere in layer 2 or 3, assuming you're doing image matching.)
Also, too many ML developers forget to allow the network to say that something doesn't really match at all. Negative cases are at least as important as positive…
-
@dkf Perhaps the abandonment of metamodel was too complete; discarding a-priori metamodel was probably valuable but accepting an entirely opaque quasimodel was likely an overstep.
Orr, fuckit, just introduce explicability as a further adversarial layer
-
@Gąska said in Good reading for self-taught programmers?:
@Arantor I distinctly remember this feature being touted as the latest and greatest in browser technology that makes everything faster, no more than 10 years ago.
I remember it too.
Google Web Accelerator is mentioned by some here. But I remember think it was baked into Chrome, too, at one point. Which caused a lot of confusion. People were not expecting it, as they would if they installed a random plugin.
-
@acrow said in Good reading for self-taught programmers?:
@Gąska said in Good reading for self-taught programmers?:
@Arantor I distinctly remember this feature being touted as the latest and greatest in browser technology that makes everything faster, no more than 10 years ago.
I remember it too.
Google Web Accelerator is mentioned by some here. But I remember think it was baked into Chrome, too, at one point. Which caused a lot of confusion. People were not expecting it, as they would if they installed a random plugin.Google Instant Pages and Chrome Prerendering, maybe? (They go together and were added ~2011.)
-
@Parody Back then I wasn't that interested in the exact name of the thingamajig. Tech news were reporting people seeing each others personal data via Google's shared cache, and losing data because the browser clicked all links in the background, including "Delete All Emails".
I checked whether it affected vanilla Firefox on Windows or Ubuntu, and carried on with my life. I considered the browser a tool. The stabler the better. Chrome was effectively in Beta at the time, and I've never really liked beta-testing unless I get paid for it.
-
@acrow said in Good reading for self-taught programmers?:
I considered the browser a tool. The stabler the better.
Me too, but at that time I was a glutton for punishment by using Opera.
-
Forgot to mention a book out of left field.
Stephen King's On Writing.
Surprising amount of advice on the creative writing that applies to programming too.
-
@DogsB said in Good reading for self-taught programmers?:
Surprising amount of advice on the creative writing that applies to programming too.
"Don't have too many characters"?
-
@acrow Oh, yes, my pet peeve.
"Something went wrong."
For fuck's sake! At least include information whether it was due to the database barfing, data processing failing or anything else really!
-
@Zerosquare said in Good reading for self-taught programmers?:
@DogsB said in Good reading for self-taught programmers?:
Surprising amount of advice on the creative writing that applies to programming too.
"Don't have too many characters"?
Don't Repeat Yourself.
Keep backups.
-
If someone wrote a footgun, it will later be fired.
-
@Rhywden said in Good reading for self-taught programmers?:
@acrow Oh, yes, my pet peeve.
"Something went wrong."
For fuck's sake! At least include information whether it was due to the database barfing, data processing failing or anything else really!
Is it better if it also says “The system administrator has been informed.”? I usually think “I'm the admin on that system and no, it's not told me anything useful at all.” but that might just be me. At the very least, if some sort of input validation fails, tell the user what that was.
Except if you're requiring all users to have unique passwords.
-
In case nobody's mentioned it, you'll also want to read somewhere between 100K and 1 million lines of code, preferably not awful code.
-
@Zecc said in Good reading for self-taught programmers?:
If someone wrote a footgun, it will later be fired.
Chekov's Footgun, yes
-
@dkf said in Good reading for self-taught programmers?:
@Rhywden said in Good reading for self-taught programmers?:
@acrow Oh, yes, my pet peeve.
"Something went wrong."
For fuck's sake! At least include information whether it was due to the database barfing, data processing failing or anything else really!
Is it better if it also says “The system administrator has been informed.”? I usually think “I'm the admin on that system and no, it's not told me anything useful at all.” but that might just be me. At the very least, if some sort of input validation fails, tell the user what that was.
Except if you're requiring all users to have unique passwords.
The software I work on used to say that somebody has been notified (added before I moved to that product).
The Product Manager told us to remove it after one particular customer report from someone high-placed came in saying that they had been waiting for 2 weeks to have a particular problem fixed and that we surely should have received the notification by now, only to have that person get more riled up when we even had to ask questions about what was going wrong.
-
@JBert said in Good reading for self-taught programmers?:
@dkf said in Good reading for self-taught programmers?:
@Rhywden said in Good reading for self-taught programmers?:
@acrow Oh, yes, my pet peeve.
"Something went wrong."
For fuck's sake! At least include information whether it was due to the database barfing, data processing failing or anything else really!
Is it better if it also says “The system administrator has been informed.”? I usually think “I'm the admin on that system and no, it's not told me anything useful at all.” but that might just be me. At the very least, if some sort of input validation fails, tell the user what that was.
Except if you're requiring all users to have unique passwords.
The software I work on used to say that somebody has been notified (added before I moved to that product).
The Product Manager told us to remove it after one particular customer report from someone high-placed came in saying that they had been waiting for 2 weeks to have a particular problem fixed and that we surely should have received the notification by now, only to have that person get more riled up when we even had to ask questions about what was going wrong.
My company has a tool that I am kinda in charge of maintaining, and it has a bug report feature that is supposed to include a screenshot of the program and then to send it to the appropriate team to get it fixed. It doesn't actually include the program itself, but rather sends me an image of the top left corner of the user's desktop, in the dimensions of the program's window. I haven't had time yet to look into it to get it corrected. As it's in Visual Basic, I assume it's probably a fairly quick fix.
-
@Gribnit said in Good reading for self-taught programmers?:
In case nobody's mentioned it, you'll also want to read somewhere between 100K and 1 million lines of code, preferably not awful code.
I don't believe this much not-awful code exists.
-
@error said in Good reading for self-taught programmers?:
@Gribnit said in Good reading for self-taught programmers?:
In case nobody's mentioned it, you'll also want to read somewhere between 100K and 1 million lines of code, preferably not awful code.
I don't believe this much not-awful code exists.
Not in JavaScript land, no.
-
@error said in Good reading for self-taught programmers?:
@Gribnit said in Good reading for self-taught programmers?:
In case nobody's mentioned it, you'll also want to read somewhere between 100K and 1 million lines of code, preferably not awful code.
I don't believe this much not-awful code exists.
I've heard tell of programs with a million lines of code in one source file. I've never wanted to investigate further.
-
@dkf said in Good reading for self-taught programmers?:
I've heard tell of programs with a million lines of code in one source file.
We'd all like to forget about SSDS, than you very much.
-
@Zerosquare apparently Microsoft noticed that acronym has become totally ungooglable and has since renamed it SSDT.
Link prefetching - Wikipedia
