I don't find copy pasting boring at all!

This is like the gazillionth time I've seen this in just a week's time. This is not original or cool, and HR does not have time for this shit. This doesn't show off web skills, it shows off unoriginal copy-paste skills.

/salt

I haven't had a chance to work with it yet. I've read that C++ intellisense has gotten a lot of improvements, I can't wait to check this out! I hope it works out of the box with UE4, although I doubt it and we'll have to wait a week or two.

I just want to say I don't have a single ounce of regret of moving from a web/mobile job to a native desktop job.

Wax on, wax off, wax on, wax off.

You can only memorize it by applying it again and again. Just be aware that the entire interface is different in say, C# or Java. You're learning C specific networking code here.

See Erik Meijers video last posted here which dicusses some of the reasons why you shouldn't do TDD. I'd take a milder approach. Try to make as much tests as you go aside from trivial stuff, and when solving bugs, don't push the fix unless there's also a test case that passes with it. It keeps your mind from going insane from the boredom of writing tests. Besides, software evolves and changes, so a lot of time on creating tests beforehand is a waste.

The algorithm was invented by Andrew Donald Booth in 1950 while doing research on crystallography

Because it's totally obvious that you'd need such algorithm when studying the structure of crystals :|

Bullshit. For example, there's a clear difference in skill between asking how automatic dependency injection works, and how to create methods.

Python for the basics, then C for the gritty shitty gory details of networking. Although, I don't think the language matters as protocols are language agnostic.

If I recall correctly it's now the rule of five ;D

Proprietary :(

Aside from Mono, .NET is slowly turning cross platform via Roslyn. I wrote a small game engine in .NET/Mono on Linux a few years ago. Worked fine :)

They're using Entity Framework and thus also MSSQL if I recall correctly. I don't know the exact details, but you might find out some more if you skim the source code over at https://github.com/voat/voat

These days there's a huge circlejerk concerning scalability. In practice, however, it often doesn't matter, as in many cases the bottlenecks lie somewhere else, if that amount of data throughput is even met. By the time it actually becomes a problem, you should look into how things can get improved or not. Of course, it doesn't hurt to create your service / program with optimization and scalability in your mind, but it shouldn't be a primary concern unless you're Amazon. Pre-mature optimization is the root of all evil; first get it to work, optimize (or scale) later.

Personally, I don't think you should be worried, given Java is huge behemoth and will not easily vanish in my opinion. If you are still worried, however, you should feel comfortable continuing with C#. In fact, C# and Java are very similar, and I'd say if you know C#, you will already implicitly know Java. Remember that Java is very corporate, and can't move as fast as C# could. As a result, I see C# as an improvement over Java, in a sense that it can do the exact same plus more. If you're comfortable with C#, you will have no trouble learning Java's syntax in less than a day, in case you really want to make that Android application.

The other way around, from Java to C#, might take you a wee bit more time, given there are more things to learn like properties, generators (yield), operator overloading and such. As a final remark, I'd like to say that .NET is turning more cross-platform friendly by the day with Roslyn, and you may use ASP.NET for creating web applications. Did you know Voat was made in C# and ASP.NET?

These are every important facts, and cannot be repeated enough. These kind of errors are small, but can be catastrophic for certain algorithms, such as numerical integration and the solving of partial differential equations. The theory behind minimizing these errors is bigger than one might suspect at first glance, and are definitely not trivial.

Yes, we should rewrite the entire thing to Go. I mean Rust. I mean Nim. I mean Crystal. Wait, what's the flavor of the month again? There's nothing wrong with .NET. Isn't Reddit even written in Python, which is considerable slower than CLR? Either way, it doesn't matter. I also don't see how you can suggest Rails over any other alternative out there. This post reeks of trolling. The mere fact you think a project like this can't be anywhere close to complicated shows your post has to be taken with a grain of salt already.

It's good up until the point it is not good. Just start learning, and when you think you've hit a wall, look for more (maybe better) resources.

Excellent, excellent talk! Do however take in mind that Erik's talk is done by the 10th person; and thus his sole purpose is to disagree with everything concerning agile. It's his purpose to clear out our cache, and to disturb the system.

The jerk in this video is so immense, my legs became hollow.