Codeacademy

yeah i did an &&

emily, you can nest one if/else inside another if/else. if that helps?

^ that's what i did

Thanks guys. I tried "&" but I don't think any of the lessons had mentioned "&&" before. I was so close!

I think their preferred method was nesting, but the && trick seemed more natural to me?

I'm still stuck on buzz tbh

I keep toying around with } and { everywhere

is it supposed to be an if else? two ifs? two fors? couldn't all of those work if I formatted it correctly?

"else if" rather than "if else" should do it.

syntactically it's:

if ( )

else if ( )

else if ( )

else ( )

That's the one.

Or, well, that works for FizzBuzz, but if you're still stuck on Buzz you want:

if ()

else if ()

else ()

This is good fun, FizzBuzz was the first one I feel like I've actually solved through thinking rather than just arbitrarily moving { around until it just works (used nested if to fix it)

It hurts my brain a bit that on my screen { and ( are almost indistinguishable, and it took me ages of c+ping before I realised the % is just the percent sign.

ah got it, it was just one } that was haunting me

i hope they keep putting out lessons all year. so far they only have 3 up, and i can't imagine it's a breeze to make a new lesson every week.

from the looks of it it's an actual startup w/ people who work there

so I'm guessing they're more concerned about keeping the traffic after week one + making the lessons is the easy part

it can be hard to see but if you click next to a { or } it will highlight its mate (and i think highlight red if it doesn't have one).

oh that's nifty

oh that's nifty

really interesting to see that theyre using triple equals so early on.. i code for a living and i'm still not completely clear on the difference between == and === in javascript

yah they just said == can occasionally cause problems?

I think that's a deliberate policy to get people in the habit of using === unless they're absolutely sure they want ==, which can cause some hard-to-find bugs

a lot of JS tutorials seem to be doing that now (I last used JS in like 2003 but decided to brush up on the basics a bit last year to do some HTML5 Canvas stuff)

quite tempted to try this tonight instead of doing some homework which is due tomorrow

(I also code for a living but my skills are very out of date and I'm stuck in an obscure (not difficult, just not resulting in any transferrable skills) rut at work. I can either be scared of this when in 5 weeks' time there are 250,000 new people who know just as much as I've been getting by on in paid jobs for a decade - and yes, I do think that's possible - or I can at least look at it myself...)

it's pretty good, I really like the site and its mission. Granted, I already know basic programming, but I'm curious to see how far this goes.

ok, I've never heard of === before, is it just a Javascript thing?

*Checks Wikipedia*

Aha, I see: The languages JavaScript and PHP extends this syntax, with the "==" operator able to return true if two values are equal, even if they have different types (for example, "4 == "4"" is true), and the "===" operator returning true only if two values are equal and have equivalent types as well (such that "4 === "4"" is false but "4 === 4" is true).

huh, i thought == checked for type as well

i couldn't figure out the && thing, so i just used i % 15 = 0. kinda felt like i was cheating.

i will admit to feeling legitimately proud of myself when i was able to make fizzbuzz work for a variable that you enter. looking forward to the next lesson...

well the prob is you haven't covered 45 and 60 and 90 and stuff!

just make a separate if statement that looks like

if ( i % 3 === 0 && i & 5 === 0)

put it before the fizz and buzz statements, and make them else if statements. i think that's how i did it. i rewrote it to use nesting later.

oops that last & should be a %

oops that last & should be a %

Wait, is the thing of not covering 45 etc directed at ytth? Because those numbers are divisible by 15, so they should come up as FizzBuzz.

Has everyone else had a go at the Java courses? Haven't had time to look at those.

i went back and played around with it after reading the thread and was able to make it work with the &&. but yeah, emil.y is right - if it's divisible by 3 and 5, then it will be divisible by 15, so the program told me i had done it right - i just felt like there was a more elegant way.

i did the 'functions in javascript' course, but i didn't like it - it seemed like a refresher that would be good for someone that was already familiar with this, but just needed some tips on how to avoid bugs in their code.

oh yeah; i suck at math

doing this from scratch - i learned a little C++ about ten years ago and lol HTMl at around the same time but i'm half considering taking courses so hopefully this gives me half an idea what i'm in for

Had a rough week but was able to finish the first lessons this morning. It was okay; I haven't done much beyond basic html before (unless you count basic and logo back in grade school), and this made some sense. Felt more like I was parroting than learning, but it was only week 1.

yeah, tbh i felt like i was filling in blanks but couldn't write the same code from scratch or anything- i may go over the first lessons again.

finished for this week!

it's def getting harder

If I want to recommend this to people how exactly do I do it? Like, just point them to the courses page, or is there a separate week-by-week thing?

Wait wait nevermind it's codeyear not codeacademy! Got it.

Did first half today. Dice game this week?

i am finding bits of this insanely confusing - in lesson 5 of "functions in javascript" there's this bit where you're supposed to look at the code and predict the answer and though i knew the likely answer i just couldn't work out what the code was doing to get it

i.e. how does

var result = 1;
for (var i = 0; i < exponent; i++) {
  result = result * base; }
return result ;

even work?

like: if you have defined result as 1, what enables it to recognise that 'result' is capable of being a number that is not 1?
would it break if you changed the fourth line of the above to

result * base = result;

result is a variable (hence "var") which means its value can change.

it would break if you changed the fourth line, not because of maths but because of the syntax of assigning a value - you can't assign a value to an expression like that.

i.e. the interpreter will read the line left to right, syntax being variable = expression, not the other way round.

ok, that does help.

another reason the above flummoxed me utterly: it took me forever to remember what 'i' was (i kept thinking 'integer', which is not useful).

tbh I don't much like this syntax

for (var i = 0; i < exponent; i++) {

Legacy syntax derived from C.

Loosely speaking, being on the left-hand side (LHS) of the "=" in an assignment and being on the right (RHS) mean very different things. The RHS is used to compute a value (e.g. the current value of result multiplied by the current value of base) and the variable on the LHS is updated to take that value. The value of the LHS before the assignment plays no role at all, and it doesn't make sense to put result * base on the LHS because that's not a variable you can assign a value to.

i did the functions lesson and new york, new york thing yesterday. trying to catch back up this week.

mostly it went well, i'm a little confused about using return within a function to check if a condition is true or not but that's ok.

this week starts with a really great review of all topics. it helped clarify a bunch of things for me.

So I'm doing this. I took poorly taught C++ classes in high school (and basically haven't used it since), so a lot of the stuff is pretty familiar so far. JavaScript does seem pretty loosey-goosey with variable types. Using + in console.log() to combine strings and numerical variables really bugs me.

whoa u guys hi

tho i might be totally imagining that he said he had a show coming up, but maybe we cld visit his studio or something

oh no wait here we go https://instagram.com/p/zOGmAbL3CT

cool, yeah i'd be up for going to the show for sure

cool man its on

i've been doing the web design courses w/ this - they're fun!