@Matthewb Ok, I see what you're doing. I already said too much.

Now it's 149809!

@JhonDoe I think it should be, as long it's her son I'm pretty sure you should be fine. I hear there's a sister as well.

@taigrr is Johnny Tables an actual person? I'm hoping you're talking about Robert'); DROP TABLE students;-- Roberts and got your little boys' names mixed up. In which case, ++

Hah, I had the exact same sentiment when I read that question.

I prefer getDocumentById('password').type = 'text' for dramatic effect

Ah hah hah, so true. Also, imagine if all the things you accidentally changed knew it was you.

@irene like Flash.

Heh, I only just realized I could instead have used the devrant logo to illustrate this point

Good luck! How did it go?

@mt3o there's package locks for that, which is frowned upon when used on people. And using shrinkwrap is downright dangerous!

@kamen Absolutely.

@kamen Yes, but code doesn't change its mind when circumstances change (which is what keeps us in business, btw)

Shouldn't that say:

str1: 'se',
str2: reverse('lp'),
str3: 'ea'

Hi bubbles, try some of the great courses on codecademy.com for example, you'll get everything in order soon enough.

Don't worry, you're not stupid, you just need to practice more so you'll learn the different patterns and how to recognize them.

JSON is a string representation (serialization) inspired by JavaScript objects (not limited to JavaScript). The relationship with arrays is this: JSON.stringify([1, 2, 3]) === "[1, 2, 3]".

The importance of serialization is that you can send a string, but not an object or array, over the internet or store it in a file. The importance of in-memory representation of arrays without using strings is that it is much much faster.

Well, this is great: https://cscircles.cemc.uwaterloo.ca/.... In Python 3, and even the examples are in Dutch! Also available in English, French, German... Latvian?... and... Mandarin, I guess?

You could try freecodecamp.org, anyone into web development will be pretty impressed if you finish the whole thing, even "just" the front end part.

Other than that, build a portfolio (fcc will help you start that).

Maybe build a free online game? You'll even get some experience handling user requests, bug reports, etcetera.

Edit: if you find anything interesting, please do respond to my earlier rant if you have the time. I'm looking for stuff to teach beginners.

@groenkek thanks, I later realised you'd have to account for one of the items being 0 though (maybe you did, I don't read mathematica)

JavaScript:

const total = input_array.reduce((acc, num) => acc * num, 1),
output_array = input_array.map(x => total / x);

(more or less)

This is fantastic 😂

"poetic literals allow the programmer to simultaneously initialize a variable and express their innermost angst"

Be sure to choose a cause you don't agree with, for extra motivation.

You the man, man. Have yourself a beer. 👊

@terraria99 in unix/linux, you can suspend any job with ctrl-z. If you then open the file with vim again, you end up with a lot of suspended instances of vim in your memory.

Maybe they just tried to undo? :D

@svgPhoenix well, if precedence was different it might have been "1false"

Ok, actually it was to call attention to this "10.234" thing.

@forkbomber are you sure the length is not valuable information to an attacker? Surely, even if x=20 you would only have to check strings of length 20 or 21 and not everything from 1 to, say, 32? What if x=2?

@willol how do you get the code to use your mock instead of the real thing?

In a unit test you would do this by making sure the actual function f is never called from the calling function, by using inversion of control (for example, dependency injection), and swapping the function f with a function that always returns the value (or throws the exception) for the situation you are testing. This is called a mock function (other relevant terms: stub, spy).

You basically say:
If the function f returns "failed"
..(by replacing the function f with an actual function { return "failed"; })

...then I expect my program (the calling function) to behave in some way.

This way, it does not matter the functionality hasn't been implemented yet in your actual dependency; when it does (presumably because you will be coding that next), your function will be ready for it.

In JavaScript this will get you "unexpected token" because 2b is not a valid variable name nor a literal of any kind. Which is probably what Shakespeare intended.

It really ttys the room together.