Terms in a EULA aren't law, and there's no reason a judge has to respect them. That said, I kind of hope it doesn't become a class action. The plaintiffs in a class action never get anything near an amount that covers their actual loss.

I can't claim to have gotten a job because of LinkedIn, because I still have the job I had when I opened my account. I get offered jobs about once a month because of my LinkedIn account, though. That said, my current job is with a company that does contract work for game companies, and the reason I created my LinkedIn account was that my boss felt it might be some nice low-effort marketing. I have no idea how many contracts we've gotten because of it.

I'd recommend checking out the newer versions of VS, especially if you use XAML.

If katakana/hiragana are present in typed Japanese there will also be spaces. There might not be if it's pure kanji, but anyone who can read that is already having to figure out a lot from context (verb tense, etc) so putting a line break in the wrong spot is not likely to increase their cognitive load significantly.

I think you actually mean katakana, not kanji. Japanese use two phonetic character sets: katakana and hiragana. Historically, hiragana was used by women and katakana was used by men, and you can still see that history in the characters themselves. Hiragana tend to be more round and have loops, while katakana tend to be more angular. In modern usage, hiragana is used for native Japanese words and katakana is used for foreign words. Kanji are Chinese characters, and each is a word in itself, representing a distinct concept. They are not used as syllables, because that's what katakana and hiragana were created for. When kanji are strung together it is to merge the concepts together to describe a new thing that can't be described adequately by any existing single character (again, just like we do with Greek and Latin roots). All the characters in both katakana and hiragana were derived from kanji that have the same pronunciation, and most (possibly all?) retain the meaning of the original kanji, even though that's not typically how they're used. It's pretty common to see kanji and hiragana together, and there are two general cases. First, small hiragana are sometimes placed above or below a kanji character as a pronunciation guide, called furigana, because children are generally taught hiragana first and gradually introduced to kanji as they get older. Second, hiragana are often added to the end of a kanji word (one or more characters) to indicate verb conjugation, because Japanese has verb tenses and Mandarin (which kanji were actually created for) does not. Anyway, I hope I didn't go too overboard there. I actually do have some formal training in both Chinese and Japanese. Not enough to claim even moderate fluency, sadly, but enough to understand how the writing systems work.

Blocks of kanji that should be read together as a single word are quite common, actually. It's similar to how we string together Greek and Latin roots to make new words. For example: Locomotive = 機関車

In my first programming class we had these workstations with an 8080A, an octal keypad, and 3 rows of 8 LEDs (with pin-outs if you wanted to be fancy and wire up a 7-segment). I can't seem to find it on Google, though.

Mookie Baylock wrote:

I almost never use IDE's basically because I have no time to lose learning all the tricks I already know on my text editor.

That's the fallacy of motion: you're too busy digging that ditch with a shovel to learn how to use the backhoe, even though the combined time to learn the backhoe controls and use it to dig the ditch is less than the time it will take you to dig the ditch by hand. But hey, you've already got the shovel in your hand, and the backhoe is way over there by the shed, so let's just mumble something about how real men don't need machines to do their work and get to it.

Luxury! I had a TRS-80 with no tape drive and a broken game cartridge slot. Literally all I could do with it was type in BASIC programs that would disappear as soon as I switched it off.

Every online class I took in college required that we post at least once per week in the class forum. Granted, that doesn't necessarily mean that the other students read what you write, but how many other students were actually paying attention when you corrected that teacher?

I'll start worrying about that around the time natural language recognition is a fully solved problem. Should be any day now, given that we've been "5 years away" since like 1960.

I'm inclined to also say no, but really what that means in this case is that their resume would not be at the top of the stack. If they've only ever done Java, then I would expect a serious deficiency in their knowledge of memory management/garbage collection, since they're used to having that handled by the VM. Java also doesn't have pointers, so expect that to be another pain point. That said, my company does hire a lot of kids fresh out of school. We start them with a 3 month paid internship (roughly $10/hour). If they're able to get up to speed in that time (and we have enough work), we offer them a full position. So far it's worked out pretty well. Out of 20-25 interns over that last 4 years there's only been one that we had to let go due to incompetence. The rest we either hired, or they got positions at other companies in our industry.

He's not talking about health insurance. It's more like professional liability insurance, which covers your financial liabilities if you are not able to fulfill your end of a contract. That type of insurance is often called a "bond", and if you have it you can tell potential customers that you are "bonded", which indicates to them that their risk will be lower if they hire you as opposed to your unbonded competitors. In some legal jurisdictions you are required to be bonded in order to practice certain professions. For example, in California, in order to offer your services under contract to build/remodel/repair houses and other structures you must be bonded (and have a license to do the type of work you're offering). Of course, unlicensed and unbonded people do offer their services in that field, and if you ask around with their customers you will hear a lot of stories of embezzlement and fraud. Even when they aren't outright criminals, it's not unusual for those contractors to do inferior work, since most of the licensing process is about making sure you know how to build stuff properly (California has a lot of earthquakes, so that can literally be a matter of life and death).

The most important advice I ever got on creating a CV is that it should be one page. No more, no less. If it's less, it'll look empty. If it's more, well, you can pretty much guarantee that any additional pages will be lost as it gets passed around to the various people that might review it. Plus, with only one page you get to avoid the endless war between office drones who prefer staples and the ones who prefer paper clips (and no matter which one you pick you'll always be wrong).

Obviously, it's that way so that noobs can more efficiently spam copy/pasta. Formatting is preserved so to facilitate finding and editing the magic numbers.

Wouldn't the person who wrote the tutorial be the mentor in this case?

At first I thought you were just being needlessly snarky. I must admit now that this is the most reasoned argument I've seen yet for not using LibreOffice.

Because neither of those give you a similar user interface plus support for modern file formats?

Why not LibreOffice?

Have you considered adding a comment? I find that's generally a good idea for clever code (with or without quotes).