I need to do this as well. I use most messengers out there and it serves a purpose to separate them into groups of different friends. The problem is that some of them still use the shitty fb messenger, and the inability to switch off 'last seen' makes them keep track of my online behavior. I have unpredictable, sporadic behavior and just don't log in to fb messenger for days sometimes, and that makes them think I had an accident or something. Is there a hack to disable 'Last Seen' on fb messenger?
While I’m not sure if it’s possible to turn of fb ‘last seen’ the attitude of friends using that or similar info (ie read receipts in iMessage) to jump to conclusions was precisely what I had to “train” my friends on. Personally the big reason for me is that I like to be in control of engaging in a conversation depending on what I’m doing, how I’m feeling, how much thought I have to put into it, etc. At first I made a lot of excuses (I was riding my bike and saw your message pop up but couldn’t respond, sorry!) but eventuallly just explained that my level of social media/communication engagement was just fundamentally different.
Of course I completely except that this means sometimes I miss out on something or that I can’t be the one to re-negotiate plans last minute, but overall it’s a good trade off. My close friends also know to just add a “need answer today” or “..now”. And also that I will still respond to messages that are truly of a critical time sensitive nature “car broke down! Can you pick me up?”
I do really wish most connunications apps cane with more status options (unavailable, busy, do not disturb, response may be delayed, etc) or customizable auto responses.
This would not work in Brazil, at least currently, where our 3G/4G are laughable... But it's a good start. The machine learning applicability could be awesome. Maybe one day we can have a smartphone guiding the blind without the need for an actual human to be on the other side.
I took a linguistics class a couple of years ago. The cognitive advantages are so extensive because according to a school of thought (Chomsky and Pinker) language itself is part of our human nature, it's innate, and is a product of biological evolution of our human brain. Knowing and switching between different languages on the fly requires a lot cognitive focus but if practiced enough, it becomes second nature, even better if languages were learned while still very young. I grew up speaking three languages (Mandarin, Portuguese, and English) and I do see the cognitive benefits when I'm programming daily in 2-4 different languages (Scala, JS, Python, PHP for instance). I don't confuse language features from one language with the other while I see co-workers mess up from time to time.
How about WhatsApp's backend being extremely scalable because it was written in Erlang from the start?
Or even Twitter that rewrote much of their backend in Scala to deal with scaling issues (I'm not saying that Rails isn't scalable, I don't want to start a war over this issue; the important thing is they saw a problem and solved it) while contributing many many open sourced libraries for our use?
Foursquare uses Scala extensively. LinkedIn is using Scala extensively for its new projects. The commercial and successful use cases for Scala are widespread at this point. For Haskell and OCaml it's going to take a while.
Well, when people say FP they mean different things. The Erlang/Clojure kind bears little resemblance to the Haskell/scalaz sort discussed in the article. Neither does most of the Scala code written at Twitter (which is mostly OO with a sprinkling of functional).
That's hardly true. Erlang's event loops are based on a very similar kind of state encapsulation as Haskell's state monad. Really Erlang is littered with explicit monadic patterns but lacks a good system for abstracting over those patterns so you just call them "OTP" instead of a monad.
It says a lot about the scale of adoption the big language players have that despite the aforementioned inroads into the enterprise that Scala has made, it is still very much a niche language; Haskell at this point in time, even more so.
Am curious to see how Scala 3/Dotty backed Scala works out. Enabling better tooling and faster build times via a generally less kitchen sink-y/more regular language should bring Scala adoption to new levels. Dotty is under active development, even saw a Github issue talking about the migration tool[1]. It's going to happen, just a matter of when.
Even if their kids aren't left with much money, they will definitely leverage their parents' influence across so many areas and be able to do anything they want.
Soon we will start seeing news of young graduates committing crime to pay off their student loans. Heck, it would be interesting to see a movie with this plot line.
Maybe there could be a new kind of social network, one where in order to maintain your online friendship connections, you have to occasionally/physically get together with your friends and if it doesn't happen it means that the connection doesn't really mean anything so you gradually lose it. This would automatically accomplish what some people with hundreds of fb friends try to do by cleaning up their friend list by asking those who want to remain friends to reply.
Sensationalist title but there are some parts with which I agree to some extent. I've heard about Meteor over a year ago but never thought about a use case where I felt the need to use it. Last week, we had a last minute project that required some sort of webapp that could allow X number of users viewing a certain page on the browser and editing things off simultaneously with good enough conflict resolution. Of course, I could have done it with Rails on the backend, rolling out my own reactive system with Server Sent Events updating the client. But as curious as I am, I decided to checkout Meteor and it was perfect for my case. In less than an hour (with Meteor) I had everything working as expected. The app was for a big social event and all it mattered in the end is that it worked and impressed everyone involved. No one really cares what you build it with, as long as you deliver. In my opinion, Meteor is worth a shot if you're building a small scale reactive system.
If finding a Scala position in the US (I assume) is already this difficult, here in Brazil it's infinitely harder. I guess our startup is one of the very few that has a fairly large system in production running on Scala, Play, and Akka. It's next to impossible to find people with experience yet alone experience in production. The key is to find people genuinely interested in learning.
So going from "I don't read resumes" and "I don't care about your resume" to "I usually read resumes" seems a bit self-contradicting. Regardless, I agree with your point of view. When we were interviewing, we got a bunch of impressive resumes but in reality...
If I get on the phone with you because of your cover letter and haven't read your resume, I will probably never read your resume.
Regardless of whether I ever look at your resume, it's very unlikely to have any impact on our hiring process. We use practical tests and, to a much lesser extent, 1:1 interviews on concepts; the practical tests have been so valuable that we're moving towards doing more of them and less subjective interviews.
