simpfai

Thanks! At the moment I'm only focusing on soccer because that's what I know best : ) However, I can easily see this being extended to other team sports.

The main bottleneck is obtaining data around the teams that a player played for. Right now I'm depending on wikipedia because the soccer data is very rich and easy to parse. I'm not sure this is the case for other sports. The data could always be crowdsourced if there aren't any good data sources for other sports.

I built football11challenge.com after spending a ridiculous amount of time solving this challenge on twitter: https://twitter.com/Carra23/status/1250066001821130759

I wanted to extend on the initial premise by allowing users to define and share arbitrary constraints for a soccer starting 11 and automate verification of a squad given the set of constraints.

It needs a little bit of polish but overall I really learned a lot working on it. Typescript + React is wonderful combination. It was my first time working with Django and it was a pleasant experience.

Do play around with it and any feedback is welcome. Thanks!

Here's an example of a "challenge": https://football11challenge.com/challenge/601246266

Hi all, a few months ago a friend and I had a fun time solving this interesting soccer related challenge that was trending on twitter: https://twitter.com/Carra23/status/1250066001821130759

We spent the better part of an hour coming up with our own starting 11. After careful deliberation we arrived at our final squad ...only to discover that Kevin de Bruyne played for Chelsea at some point(in our defense his stint at Chelsea was forgettable...). The entire process was extremely entertaining but I was left disaffected by the manual verification process. We had to think of a player then run over to Wikipedia to peruse the list of clubs that they played for. I thought it would be fun to create a web app that:

Lets users define and share arbitrary constraints for a starting 11 Automate verification of a squad given the set of constraints.

Do play around with it and any feedback is welcome. Thanks!

Here's an example of a "challenge": https://football11challenge.com/#/challenge/601246266

Failure to apply a patch for a two month old bug led to this entire nightmare scenario. What are some best practices to ensure that ones dependencies are always up to date?

-asking as a relatively inexperienced dev

According to Connor McGregor, Mr. Mayweather "can't even read" so your fear is definitely valid.

http://www.telegraph.co.uk/boxing/2017/07/13/cant-even-read-...

I found this paper[1] to be a particularly good source of information on the legal landscape of using algorithms in the judicial system.

[1] Barocas, Solon, and Andrew D. Selbst. "Big data's disparate impact." (2016). APA https://www.accmeetings.com/AM16/faculty/files/Article_461_D...

He may be referring to the on boarding process + first commit. Generally you'll have a few classes that introduce you to Google's build tools and any technologies that are relevant to you/your team. Then you'll start work and go through your first code review. This is probably what is refereed to as 'initiation rites'. Depending on the size of the change you may get a handful of comments or quite a few. After going through the code review process you will have successfully internalized Google's commitment to code quality. Generally you'll get a bunch of comments and suggestions that seem nitpicky but help keep things consistent and a few that are eye opening and help you become a better engineer.

Does anyone know of any resources for someone looking to learn more about Game AI for real time strategy games?

I know Google's Flutter(https://flutter.io) is still in its infancy but can anyone comment on how it compares to React Native?

well said

I guess it depends on what your aims are. Are you new to mobile development in general and just want to learn how to develop for your preferred platform(iOS, Android etc..)? If thats the case then definitely use Firebase or any other backend as a service for that matter. This will allow you to focus on building your app and not have to worry about implementing an API that provides access to your mongodb database(this would also be a worthwhile exercise). Hope that helped.