To be clear for Overwatch only console party voice chat is peer to peer, not the in game Overwatch voice chat. This means you have to join a PSN party to reveal your IP. This is also true for Xbox One.
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)
Since this was a critical issue I think "David" should've brought key stakeholders (or leads) together and set expectations for who was doing what parts and when it would be complete.
Wish there was some info about what the site does without signing up.
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.
A great deal of people leave companies (or positions) because of the relationship they have with their manager. If you're not in a position where you can comfortably discuss your salary with your direct manager, find a better opportunity.
I do a lot of interviewing and I almost always ask people to rate themselves on a scale of 1-10 in their primary language with a note that I recognize I don't expect our scales to match.
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.
Wayne Chang does a great job of telling a story using bits of history to over represent reality.
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.
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.)
The most common problem is conditional nesting, like with wrapper divs. In addition to :plain there is also :erb. I think the poster was implying that occasionally you'll need to structure code in a way that is not optimal (work arounds) to do something that requires no special work in erb.
I also wanted more specifics though, I felt like this was a fine opinion piece but lacked any specific world lessons.
An interesting post, but I felt you stopped short of any specifics that would help sway someone on the fence or without an "educated" opinion already.
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.
I was a hiring manager at Electronic Arts for a team that exclusively used Erlang. It's very hard to find Erlang talent.
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.
I am a coauthor of the original emysql. I wouldn't recommend using Erlang for your average web application. I would recommend it when the problem you're solving thrives on an idiomatically distributed and fault tolerant platform.
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)