Depends on what phase of my own coding existence we're talking about. . . For example, my Java coding life cycle goes kind of like so: Yes up until when I got my first patterns textbook, figured out what interfaces were for and what System.Reflection was, then no until I actually figured out how NOT to use those things all of the time. . . I have quite a few "Too clever by half" implementations that look strikingly like spaghetti code in that era. . .

Microsoft :P

On a more serious note, basically nothing if you're not planning to ever make the source available to other people. The point of the git model is being able to easily and flexibly allow people access so projects can have an explosive number of contributors. IDK maybe they're outsourcing your IT team.

Sooo . . . Short answer, no.

You're looking at this from the wrong angle - Agile, unit tests and rapid release cycle is actually fantastic. . . . For purely the front end system. As far as graphics and UX goes, agile is king. Small, fast, incremental change is king. But that doesn't help you build a backend, and basically no company I've worked for (or seen, recently, really) wants to acknowledge the glaring issue with never nailing down your product requirements when you're building the backend of your system. But it's like building a house with an uneven foundation - It's going to be lopsided at best, and it'll collapse later (probably with tragic timing) at worst.

Looks like a shitty version of C at this point, honestly. Haven't looked at it too thoroughly though.

After you've learned C/C++, Javascript (or another scripting language) and one full Object Oriented language, you're basically equipped to learn anything that exists presently for programming. It only gets easier, so at some point the boasted tech stops mattering as much as what it's actually supposed to accomplish. Some things you can very readily work around, other things, not so much. (Or at all in some cases.)

Buzzwords. The people who don't understand how things work think that you're some kind of god if you present more of them than anybody else.

Man in the middle is not difficult in the slightest. This is really, really easy to exploit - If you set up a man in the middle, or if they ever surf to a domain you control. Ever accidentally tried to visit a very common page and been one letter off? Congratulations, you landed on a potentially attacker controlled domain, and your device is now potentially compromised. This is actually very usable, and EXTREMELY dangerous. Basically every single machine that runs a Unix kernel of some description (so basically every mobile device ever) is potentially at risk. Why do you think that Google stumbled across this, along with the people running the library, and the red hat Linux devs?

Depends on where you live. If you live in Seattle/Vancouver they basically need anything with a pulse that can program right now, and will pay generously for it.

Java and C# have basically identical syntax. C# isn't going away unless Microsoft does, and Java isn't going away unless Android does. Definitely a language worth learning.

Ah, personal preference based on overhead. Gotcha.

What's wrong with Java? o.o