390
retard
194d

# Binary is easy to teach

• 81
Need more data to train that guy. Just a slow learner
• 46
Like @asgs said, just try to increase learning rate or increase the size of the data. Also try different cost function, might help
• 8
Wouldn't using 2^n be more effective?
• 20
EDDMOARLAYERS!
• 2
:’(
• 12
Waiting for hex chat...
• 12
I remember being bored one afternoon in middle school shortly after I learned binary. Manually typed out every binary number to 9 digits or so just to kill time. Got used to the rhythm pretty quickly doing that...
• 3
It would be 1010 correct?
• 6
1010
1011
1100
1101
1111
10000

Right?
• 14
@Bobj2008 you skipped 1110 :D
• 6
@retard oops lol
• 2
@Bobj2008 learn from David and slow down a little.
• 1
@sauronjs π will do π
• 17
Just showing it in table form is the easiest to learn in my opinion.
• 1
@asgs Just don't overfit
• 2
• 1
@asgs It's just Gen 1, NeAT will take care of it
• 1
@FinlayDaG33k what's that? Can you link?
• 2
Ich learned it with trying to fit one of those 16/32/64/...
For example 100:
100 - 64 = 1
36 - 32 = 1
4 - 16 doesn't work = 0
4 - 8 same = 0
4 - 4 = 1
0 - 2 = 0
0 - 1 = 0
Whole number in binary = 1100100
• 1
@shelladdicted count with me! 0x0, 0x1, 0x2....

Actually...

n := 3
for {
fmt.Printf("%X\n", n)
n++
}

//done
• 3
@Bobj2008 The alignment is bothering me. Can't even proceed to read without proper alignment.
• 1
In my experience it’s easier to start teaching other systems.
Hex is good because it contains all the digits people know, it’s just „extended“. Once they understand that, binary should make much more sense to them.
• 0
Just hope he doesn't trigger an OOM error!
• 0
Just thought this was a repost because someone liked my previous comment and I saw the post againπ
• 0
@systemctl but 68 isn't 1000100?
• 1
@pinguluk True, I just copied that table from the first DuckDuckGo search result