Jepsen[1] is the killer app that's leading me to learn more about
the Clojure and Go ecosystems.
I mostly write Python by day but since Jepsen revealed consistency
problems in etcd[2], I've had to learn more Clojure/leiningen to see
if the ?quorum=true option fixed them.
What I've learned so far is that Clojure's error reporting sucks unless
you use something like Cider[3] and that etcd till fails to pass Jepsen
with ?quorum=true
I'm about as old and I've lived in the bay area all my life. I've seen the popularity of things on his resume rise and fall. I'm not on any social network and my bank account has never exceeded five figures. I could be this guy. Maybe I will be in a few years.
But even though he probably has plenty of skills that could be useful I doubt I'd seriously consider this guy at my present employer. Why? Because his whole signal to noise ratio is way too low. He's got a ton of red flags and "resume smells":
* Freelancer for 11 years
* No mention of employers or marketable projects in last 5 years.
* Laundry list of antiquated technologies (some listed multiple times)
* Lots of irrelevent stuff (reasons for leaving, college honors from distant past)
* Random WTFs thrown in for good measure (oldcoder.org? christfollower.me?)
* No clear mention of goal, purpose, motivation or passion.
* Comments showing pride about being a "generalist"
You never get a second chance to make a first impression and unless you're introduced by a trusted third party the impression your resume makes will be the first. Each and every word should help a potential employer want to talk with you. Your content should be informative and relevent. Writing it may not be easy but remember what is written without effort is, in general, read without pleasure.
Says the game developer who sells virtual goods...
I've lived in the bay area longer than BART has been in operation, and I'd rather see my fares raised to pay the BART employees even more so that they can focus on the safety and security of the system instead of having to be worred about being evicted to make room for some virtual good merchant.
BART workers directly help millions of people in the bay area every day and provide far more value to the bay area community and economy relative to what they are paid then do the participants in this forum.
You'll need to deploy your own private log analytics. While there are plenty of products developed over the past decade to help you do this, the "in" approach these days is a combination of Hadoop for storage and ETL and a more traditional data warehouse for summary queries and reports. Several presenters[1] at Hadoop World 2010 covered this.
Do you think it's possible to have such a game with out mortal combat as the central theme and still make a big impact in the gaming world. Cooperative but not cooperating to kill the other team?
Worth noting is that "kill the other team" is a blanket term that encompasses many different levels of violence. Yes, in some games you do actually kill people, but there are so many variations - in platformers you often just jump on their cartoon heads, in strategy games it's more about conquest, like playing Risk.
Looking through my own gaming library, there are a lot of completely non-violent games where you could class it as "mortal combat" - for example in Osmos you play a single-celled organism (sort of) trying to survive by absorbing those smaller than you and avoiding those bigger than you.
There are many games out there less violent than Call of Duty that kids could play to bond or make friends, but they get overlooked because they get lumped into a category, and then the media parade the most extreme examples from that category in front of us.
Sports games. I had heard that the killing aspect could have been been removed from the game in Germany for legal reasons. Bullets were to be replaced with paintballs and killing with simply eliminating opponents. They never ended up passing the law banning violent games though.
Both my kids spent considerable time "role playing" and focusing on non-combative activities like chatting and trying out different variations of character choices so I'd say the answer is definitely yes, especially if the game builds on age-appropriate social curiosity or borrows from familiar cultural elements. My daughter especially loved things like playing "barbie" by showing us different combinations of clothes she obtained and playing pranks like walking around cities dressed as an NPC, hoping to fool other players with emotes.
It looks like it did. The internet archive crawled bits of Lycos Circles from 2005 to 2009[1] as well as the original eCircles all the way back to 1998[2]
This isn't good advice; learning Prolog doesn't make learning Erlang any easier at all (not even the syntax, but especially not the semantics). The syntax of Erlang is actually very simple, and mostly an accident of history since Erlang was originally implemented in Prolog[1].
Even though Prolog and Erlang are very different languages that rely on very different paradigms, they do have one thing in common: recursion. Learning Prolog will force you to learn how to think recursively, and will make it easier to then learn Erlang.
That said I'm not sure it's a big win compared to learning Erlang directly.
You may be right - logic programming isn't easy and the semantics are different, so it may make things more confusing for a complete beginner (I learned Prolog long ago). For a deeper understanding I would still recommend trying it.
1- https://en.wikipedia.org/wiki/DBC_1012