Coding is fun, but for me, solving real world problems is even more fun, with or without coding. What I see around me is that most people seem to be completely unaware of their surroundings, or can't match a necessity to a solution. Coding is great until you reach a certain level, above that, you should be able to put your hands in the dirt and build something else from it. Coding is like playing in a box, however great solutions are created outside of the box :D. Answering the main post. I would definitely be coding with 100M in the bank. But I wold also invest some time in some other projects to create useful information / content or any product not directly connected to technology., to solve some sort of world needs, like food chain, water supply, social care, etc.

Yes it is, and the solution might not be so futuristic as everyone seems to think. First, what is a bug? Is it a bad code implementation? An unexpected input, caused by an user, or problematic hardware? For each one of the possible causes of a "bug", your software must be able to execute and debug itself simultaneously, in order to keep track of its own actions. You also need a process that uses a list of known patterns for common "programming errors" / "best practices" to identify possible pieces of code that might be causing unexpected behaviors, the biggest trick here is to have another process that replaces the identified bad practices with good ones. If the issue is caused by a bad implementation, one possible solution for it is to have a different implementation for the same function, to check if the software is producing the expected result or not. Or in alternative, you might create "step by step" tests to validate the same process. The next part, (maybe not the most difficult one) is to create a process that works as a time-machine to "go back in time", (like an auditer), that saves the state of the application in different execution times, as all the changes produced by the software. When an unexpected result is caught, the software should be able to trace back the error root, identify the cause, patch itself with one solution from your pattern list, run the application again from a saved state before the bug happened and use the auditer to reproduce the inputs after the bug, to try to achieve the wanted result. If the result is still not the expected, another solution is applied, and it repeats this last steps until the expected result is found. I must add that my solution for this problem, is not applicable to any kind of software, it is far from perfect, and maybe some steps could be very difficult "software problems" that not any programmer can solve (everyone can try), but all processes here are "doable". In conclusion, what you asked is definitely possible and most of the processes that I described already exist in software nowadays. However, the cost of implementing a software like this, and the difficulty to have a good code replacement tool makes it very difficult to implement, or adjust and expensive. It also can cause slower execution times, every time the software patches itself. In any case, I strongly believe that this sort of "self assisted" / "self fixable" software, will sooner or later make its way into the IT world, very likely as a software improvement tool , with or without AI.

Why isn't JAVA (JSF) still popular to make web pages? Why aren't we coding binary apps that run remotely instead of loading tons of frameworks built over each other under the browser? Why isn't Flash popular anymore, if it was so great? Or Silverlight? The answer of this might not be as simple as you could think. Javascript is not popular just because of browsers, instead, it is definitely the main reason why people use it so much. But the reason why so many people like Javascript is related to the nature of the language. It is a kind language for someone who wants to learn to code, at the same time, the diversity of coding techniques that you can apply to it, are another strong point of the language, and also why so many people like it. Javascript abstracts you from data types, memory management, teaches you about data structures, hierarchies, concepts of parents and children, objects, functions, arrays, synchronization, callbacks and lots of other things that are slowly brought to you as you spread your knowledge, increasing your awareness of what it really means to code and to be a programmer. Nodejs was another reason why Javascript became so popular. It was the missing link between client and server. It is easy to learn, because of the familiar language you probably already knew, and above all, it complemented your programming awareness by dealing with all the actions that you couldn't or shouldn't do from the browser. In conclusion, I really think that Javascript would still be very popular without the browser, and valuable as a learning language, especially for new programmers who don't know where to start.

Books of CSS? Actually, I've seen some titles from "famous" designers, but what I've learned is that you simply learn more with CSS oriented sites than any book. Learn how to use the browser's console to mess with any page, (Even this one). Learn the meaning of ID's, classes, conditional CSS, children, parent. and later transitions and animation. Start with the basis and as you get better, search for tutorials to learn more.