|
but it'll be better than the current multiple CPU's that can't even agree on the same answer to the simplest of problems.
Message Signature
(Click to edit ->)
|
|
|
|
|
CPU == Central Political Unit?
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Or "Cr@ppy Policy Unifier".
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Nope, it will generate an exit code error
|
|
|
|
|
What is incredible in all this is how peoples opinions are based 100% on their desires.
|
|
|
|
|
Here's a fantastic article / interactive graphic story that explains a great method for learning and memory retention. I'm sure you'll really like it if you check it out. It definitely deserves more attention because it is done so well.
How To Remember Anything Forever-ish[^]
|
|
|
|
|
Thanks going to give it a try.
There's a ton of stuff I have to repeatedly google so I downloaded the anki app in hopes it will help me.
I may not be that good looking, or athletic, or funny, or talented, or smart
I forgot where I was going with this but I do know I love bacon!
|
|
|
|
|
I followed the link, but I forget why and came back here.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Who are you?
I may not be that good looking, or athletic, or funny, or talented, or smart
I forgot where I was going with this but I do know I love bacon!
|
|
|
|
|
Quote: And you may ask yourself
How do I work this?
And you may ask yourself
Where is that large automobile?
And you may tell yourself
This is not my beautiful house!
And you may tell yourself
This is not my beautiful wife!
|
|
|
|
|
Only happens Once in a lifetime!
I may not be that good looking, or athletic, or funny, or talented, or smart
I forgot where I was going with this but I do know I love bacon!
|
|
|
|
|
Unless you bump into a psycho killer.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
And then you'll be on a road to nowhere.
|
|
|
|
|
I've got a book about that.
It's around here somewhere...
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mike Hankey wrote: Thanks going to give it a try.
It really is a cool method for learning. I first learned about spaced repetition while learning Spanish from Pimsleur language learning series.
|
|
|
|
|
Looks like a good system. There's some things that I just can't remember, simple things that I have to look up often. Had a professor in college that said he didn't remember simple things because he could look them up, but it slows things down and you lose your train of thought when you continually have to look stuff up.
I may not be that good looking, or athletic, or funny, or talented, or smart
I forgot where I was going with this but I do know I love bacon!
|
|
|
|
|
Mike Hankey wrote: it slows things down and you lose your train of thought when you continually have to look stuff up.
I agree and this is definitely true in relation to programming languages, APIs etc. Especially if you work on multiple platforms.
|
|
|
|
|
raddevus wrote: I agree and this is definitely true in relation to programming languages, APIs etc. Especially if you work on multiple platforms.
Strongly disagree.
This is why fast search (and tools built on it like intelisense) is far more important then trying to remember: changing (evolving, extending, standardising..) API definitions makes memorising a detriment if not a danger and really should be avoided.
"Well when I learned it it started at 1, since when did they change it to zero?"
= not only 'what I memorised is now useless information' but 'it WILL cause my code to fail.'
(Well in vb it starts at one, but c# starts at zero, but they are both .net)
Applicable to any field: If my 50 year old doctor is going to rely on what he memorised back in med school 25 years earlier than I'm going elsewhere. I'm way happier if he looks stuff up and/or asks his peers.
Yeah it's fine for remembering peoples names
and in say programming simple info like what symbol to use for addition and [less obvious] modulo in language X... or even bit deeper such as the logical vs boolean operators (which many compilers might not flag the ambiguity when it looks like the wrong choice may have been made)
but when it comes to API's and interfaces (i.e. communication between 2 entities) particularly between platforms absolutely always far better look it up (particularly if not used for some time), or significant new versions of one or/and the other entity have been released...
Does looking it up slow you down? Rubbish. With google etc, you're talking seconds or less to check.
Whereas, [given these things do change, given platforms do differ, ...] it's "remembering" the wrong thing that'll significantly slow you down and cause failures.
Message Signature
(Click to edit ->)
|
|
|
|
|
I have just started learning Hebrew so will certainly give it a try.
|
|
|
|
|
Anyone who has graduated from medical school knows this is how you deal with a firehosed delivery of new facts and has to convert them to "knowledge."
It also helps memorization to write and speak what you learn--and, even better, to explain it to someone else.
|
|
|
|
|
Harrison Pratt wrote: It also helps memorization to write and speak what you learn--and, even better, to explain it to someone else.
That is a fantastic point. That is exactly what Paul Pimsleur of Pimsleur language series also found:you must speak the language to really learn it.
|
|
|
|
|
Back in the 1920's, AT&T wanted to install electrically operated telephone exchanges to replace the operator based exchanges. At that time, you would place a call to "Butterfield 5678" and an operator would manually plug your phone line into the Butterfield 5678 socket.
Almon B. Stroger, an undertaker who believed that the wife (an operator) of one his competitors was rerouting calls for him to her husband, developed the first stepping switch which became the basis for telephone exchanges.
Back to AT&T, they wanted to know how people remembered things so they committed $20 million to a study before they implemented electro-mechanical exchanges.
AT&T found that people remember things in groups of 2's, 3's and 4's. That's why our telephone numbers are xxx-yyy-zzzz (area code, exchange prefix, local number).
Further, they assigned the lower area codes to the larger population centers, like New York is 212, Chicago is 312, etc. to appease the financial industry.
This was good until the mid 1970's when population and phone usage increases overwhelmed the phone numbers and exchanges had to be split.
Then came cell phones.
This is also the basis for IP addresses (plus it works real well for remembering a hex number as 4 groups of 3, e.g., 192.168.1.3).
Just some trivia.
|
|
|
|
|
Although the intro is way more important than everything else, it's about inspiration. If a factoid is interesting to remember, it'll get remembered eventually all by itself.
|
|
|
|
|
The file organization is WAY different. Had to look around a bit for the bootstrap css file.
I think I prefer this to the previous MVC organization.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Oh come on! Who thought this one up?
The World’s First Remote Controlled Real Flame Candle With Safety Features And An Impactful Social Mission[^]
It's ... not really a candle, but with a remote control ...
I don't even want to know what the mission is. OK, OK ... I'll check.
Ah. Every time you buy one of these (overpriced) things, they give two books to needy children. Presumably so they can sell them and buy food, I dunno.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|