95 karma · joined February 1, 2012
But to suggest that rejection should be our default behavior is absurd. Discussion should be encouraged because, more often than not, neither side is 100% correct. The way we further ourselves is by talking to those people with dissimilar views.
"We're sorry, but something went wrong."
when I tried to authorize the application in GitHub. If this is your project I'd love to try it out if there's another way for me to sign up (or another date I can try).
I was mostly going off the assumption that people would select one or two intervals at a time, learn them through error, and then select a few more but this is an easy change for more clarification.
- That's not a feature yet but I'll definitely add it to the todo list since people train in both ways.
- Whenever you answer, the sound plays again: if you get it wrong it repeats, if you get it correct then it plays a new interval. But I can see how that isn't clear so I'll change the wording / possibly animations.
Thanks again!
Hi HN,
I've been taking guitar lessons and one thing that is recommended to most musicians is ear training - where two different notes are played and you must identify the number of steps between the notes. My app, Earbuilder, should help with that process.
You can find it here: http://www.earbuilder.com/
It's my first web app, and my first real foray into JavaScript. You can take a look at the source and you'll see that it's pretty poorly structured, but I've picked up a book and hopefully things will improve with my second web application.
Please let me know if you have any comments, suggestions, or hate because I'm looking to improve this over the coming weeks!
I tried to find if there was some theory behind it but all I could really find was "saturation degree".
I had to code a project in C once - nothing big, maybe 200-300 lines of actual C code. Instead of going straight to the computer, though, I sat down with a coffee for 2 hours and wrote the entire thing on paper.
Have you ever sat down at a computer and not known exactly where to start on a project? Usually this is because you've started too early. There's not enough content in your head to form a mental model of your problem.
Sitting away from the computer introduces a barrier and forces you to reconsider whether you have assimilated enough material before sitting down to program.
The way I figure, which may be incorrect, is the following:
You have x options (here it is 16). x^2 gives us 256 different options for this example. However, if it's only correct correct half of the time then we have to repeatedly cut down our search which results in series:
sum (x^2)/(2n), n=1 to m
which is
(x^2 H_m) / 2
Is this correct? Could someone explain how many random extra comparisons would be needed to thwart a timing attack?
Obviously, if I use a different name, artwork, and rule set there isn't really a problem.
EDIT: I saw your above comment and you make a good point about different check-in times.
The stuff that you are able to put into neat little folders _should_ go into neat little folders.