If only there was one of these for computer science degrees. I stopped part way through my degree because the tuition was ridiculous ($1000 per credit hour). Now I'm at a point where I want to finish, but all undergraduate programs in my area are oriented at full time students. The only place with online and night classes has equally ridiculous tuition ($60,000 to finish the program).
Switzerland is another option. They've got two good engineering schools that pay top international students to attend, and the tuition is negligible (compared to US). I'm starting my MS in CS there in the fall.
There is no age cut off. German constitution allows everyone to study.
Students who study abroad often have problems getting credits recognized, that will apply to you even more so. Then again, I don't think you have to take "Introduction to Programming" again if you already have 10 years of work experience. I think you'll be able to work something out with them.
There are some program thought in English, try this site:
I think isomorphic JavaScript applications are going to replace the current frontend paradigm. Microservices are becoming more popular, so imagine an isomorphic JavaScript application as a frontend consumer of many backend microservices. Plus there are a slew of security considerations that cannot be solved with current frontend JavaScript.
For instance, how do I call a protected API without leaking the API credentials to the consumer? Currently you can do this with trusted hardware or the traditional server side rendering. An isomorphic JavaScript application can solve this problem using server side rendering without needing a separate backend.
This is precisely what we're moving towards right now. It allows us to break away from our current, sub-optimal backend server serving up all the services to an isomorphic JS app that consumes variety and spits back out results from API calls. It allows for great flexibility -- not to mention speed and consistency.
I've been looking to abandon Chrome and I would definitely give Metro Firefox a try on my desktop. I enjoy the metro split screen with the Windows 8 Store Twitter client (it's awesome to get push notifications). If I had a nice browser for metro then I would definitely try to migrate.
Exactly this. Most people's huge, monolithic apps should be partitioned out into smaller, more modular apps. They're easier for multiple developers to work on, they're easier to spec out, they can have their own optimization/iteration cycle, etc.
An example, we have an app that so far consists of about 25 individual SPAs. It was originally an SPA, but we ran into tons of problems with routing issues that cropped up, and realization that when the user uses the apps, in any given session they'd probably only use 20% of what it offers. Developers get to work quickly on their modules, there's no up front initialization/download of the entire apps. Some of the apps are more prototype quality to get the job done, some have been refactored several times. But they all form a cohesive experience. It's also nice when you're developing a group of functionality that you don't have to start the app at the beginning.
Most users won't even know when their in a SPA vs Multi-page SPA.
This is my favorite 'feature' of knockout. It's as simple as knowing a single attribute 'data-bind' or comment pattern '<!-- ko ... -->'. The only down side that I've seen is not having an 'else' statement :/. That's just a by-product of how knockout's bindings work though and hasn't stopped me once from keeping it my preferred library.
