Once I didn't get any sign of being drunk regardless of the drinks being >50% and 70% vol. and higher, even though we danced, made push-up and have had fun on a trampoline. To this day I still don't understand how not only I, but also the friends who drank the same didn't get drunk. There must have been a secret ingredient in that moonshine, because I didn't eat anything before that.
wow, and I thought that only happened to me!
Some weird american voice was on the other side and it sounded a bit like a comedy show, but interestingly the voice was not made out of pieces and put together into sentences, but actually coherent and responsive to my questions. Living in Germany, this was actually weird enough to think that someone is in control of our cell-phones.
But why did we both have the caller-id of our mom's?
Looks really good, but as others noted, the examples should really work `as is` within the REPL. Also I think wikipedia has better example code. Everybody knows fibonacci and can compare it.
on the same boat.. but have given up on using Chrome for bookmarks. It's too slow on Linux when you've more than 50 tabs.
Firefox loads under a minute with 510 tabs from various tab-groups. (I use a tab-group for each group and field of study and yes I use most tabs actually)
The search in the sidebar is so enormously useful, it helps me to find ANY bookmark made by hitting CTRL+b or middle-click (two-finger tap here). I heavily use tags, which is really making the search better, but I wish these tags could be automatically generated by an algorithm.
2 Weeks is what it usually takes to catch-up with all new libraries in all the languages you care about. Not more. Easy as googling it and checking github explore, then trying each one out. Simple as that. Do that every 6months and you're set. What could go wrong? :)
Sorry, but you don't learn actually anything new there buddy (there is more). You're right that MS packs all the un-branded wisdom into products with custom API's, SDK's coming with 20 new buzzwords describing the improvements. Well, because people love good packages. For MS software there are the Rx extensions and F#, but I'm sure that you can live with just ReactJS too. However here is some short but good read: http://www.infoq.com/news/2013/08/reactive-programming-emerg...
But if you once learned what FRP is, what Software-Engineering means, OOP Patterns, Functional Programming, then you'll be set for at least half of your life man. Also Real-Time Applications for the Web are a big misconception, they can only be of use where you really really need hard-real time applications. Which is mostly not the case with web-apps. What you need is a reactive web application, but please don't eat the BS in the reactive-manifesto.org. It's not wrong, but not intended for engineers and comes packaged with just hot-air, that according to the writers is "useful" to communicate to managers. I digress, but reactive programming is the concept you would be better of focusing on instead of real-time, except you are having one of the rare cases that actually needs hard-real-time synchronization.
OT: Am I hell-banned or something? My submissions appear dead at arrival.
Be and keep worried, but don't let your angst control you!
The post describes a peripheral vision of progress, but no relation. It doesn't matter shit what new software, libraries and technologies are out there. What matters is that you have your own goals and advance in that! The rest doesn't matter, don't worry about others, you cannot help anybody, if you cannot help yourself.
I always tell me friends who don't know anything about computer science that my job is to make everyone else's job obsolete. After convincing them how their career might one day be replaced by software, robots and algorithms, I explain how they don't need to be alone with that fear. Of course I know how this makes me look like either a freak, an asshole or both. But the important part about the discussion is to communicate what really is going to happen. It happens, but the progress advances as slow as the growth of a tree. One day, it will be large, it will be a forest and then there will be no way to ignore it anymore. This is why it matters to open someones eyes. Of course only those who you deem worth, most people still won't listen and let time pass.
So yes, I share the same fear. Our destiny and true job is to make ourselves obsolete. Creating Software that can create machines, products and manage people, schedules and ressources. Creating Software that can create better versions of it's own or even create other Software to fulfill it's goals. This sounds like a big stretch, but we're talking about a time-span of 20 to 30 years.
We write code that will one day replace the need for us as a regular' work-force, but not as an actor in the process.
The Future won't stop there, it'll instead create new markets and jobs where we proceed as architects using our creativity and intelligence, until our machines create hardware that surpasses the constraints on the software, which were set by us.
This will require us to allocate new resources for energy, either beyond earth using SpaceX like programs, the invention of a replicator (using quantum teleportation and molecular re-organization) or light to mass converters.