Subtle but important distinction, don’t want to scare people away from talking in Overwatch but players should avoid console parties with players they do not trust.
(Source: I’m a lead programmer on Overwatch at Blizzard)
345 karma · joined August 31, 2010
Subtle but important distinction, don’t want to scare people away from talking in Overwatch but players should avoid console parties with players they do not trust.
(Source: I’m a lead programmer on Overwatch at Blizzard)
https://coachella-streamer.herokuapp.com/?ids=18,35,42,44,47...
Also, I would remove the question asking for business description and planning/modeling needs from the signup form. I think you're likely to get very little effort put into that section from a new user who has no attachment to your app. It could be placed better as the user begins to interact with your app (however that works) ..
edit: Oh I see, you have to go to the default landing page to get more info. https://opstarts.com/ -- Should fix that, at least make the navigation element in the upper left of app go to that landing page.
Overall feels pretty interesting. One thing of particular interesting is "cloud based load testing" service available for hosted repositories.
http://tfs.visualstudio.com/en-us/learn/load-testing
I'm a huge fan of Github and I don't see myself changing anytime soon, but I'm interested to see what features end up a part of the TFS offering.
While the author certainly doesn't deserve to be treated with disrespect, I think there is some looking inward that needs to happen here too.
After they answer I ask what they learned last to raise their knowledge along their scale, what they're learning now to try to grow further (if anything, sometimes you're just executing not learning,) and if the candidate is applying for Senior Software Engineer or higher what "gotchas" they typically look for in a junior coworker/employee that would be rated lower on their scale (during a code review, for example.)
I usually get really thoughtful answers and gather a lot of insight about the candidates mastery of the language, mentoring and overall thought process.
He claims in several places to have worked at Napster, despite the fact that he was only a volunteer Moderator for chat on the service. Even in his linked in he lists himself as an "Administrator" but that title specifically represented a user access level above "Moderator" (both volunteer community positions) that he did not have.
http://www.linkedin.com/in/waynechang
He also represents himself as a consultant to AllAdvantage, when in reality he created "click bot" that automated AllAdvantage use.
This lawsuit is interesting, but I strongly encourage digging into the history of Wayne before coming to any conclusions.
(Note: I was an actual Administrator for the Napster service, but never employed. I am quite familiar with Wayne "ttol" Chang from #napster on EFNet, and I've had several 'disccusion' about his LinkedIn profile with other people in similar position to me.)
I also wanted more specifics though, I felt like this was a fine opinion piece but lacked any specific world lessons.
While I prefer HAML to ERB, I understand that occasionally wrapper divs can be a hassle in HAML. I assume this is what you're alluding to in Breadth and Scope, but maybe there is more?
The point of this post may not have been to add clarity for people not familiar or already opinionated, but if it was, the more specifics the more helpful it'd be for someone like me.
https://github.com/jacobvorreuter (emongo, erlmc, dynamic_compile, etc.)
Jake was a long time member of the Erlang team, and a lot of side projects were influenced by pain points from our day to day work.
Many candidates have used Erlang in an exploratory capacity and have no real experience supporting a production Erlang application under load or troubleshooting concurrency problems in a distributed system.
That said, it was great to see a lot of passion for Erlang. I enjoy writing it, and hope the language and community continue to evolve.
Maybe that'll work for you!