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!
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.
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!
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?
Equifax makes their partners have a fully implemented and tested patch management program and audits annually (or via a third party) that you stick to it, making this situation even more hilarious.
Failure to patch wasn't the cause of this breach. The causes of this breach were:
1. Reliance on a consumer-grade component in a security-critical system holding high-value data.
The portal should have had a small, audited code base with secure coding techniques and minimal reliance on third-party components.
2. Excessive attack surface on a system holding high-value data.
The machine hosting the portal should never have had read access to SSNs. Sensitive data should have been "thrown over the wall" to a secure backend with a constrained interface. This would have greatly reduced the scope of the breach.
If you're lazy and dealing with a non-critical system, `yum update --security -y` as a nightly cron job goes a long way.
If you're working on something important, say critical national economic infrastructure, you do the equivalent with automated staging and testing happening before any potentially breaking changes are made to live servers.
Yum isn't going to patch Struts, though. That's an application package.
There are services that monitor your package configuration(s) and let you know when something has been updated.
There are also mailing lists. Unless you're a Node developer, you probably only have a couple dozen dependencies in your app. Subscribe to them.
Finally, you can just check in your lockfile and update packages as part of your dev builds, then commit it whenever something changes. Your CI/CD will make sure you are always running the latest version of every application dependency in production.
Although I'm sure Equifax is not going to be very forthcoming about this aspect of it, not having plaintext passwords visible after logging in as admin/admin also helps.
Nobody's saying music majors are incompetent. But this woman's sole qualification is that. She is not a "kernel dev hacker" AFAICT. Do you know if she is in any way qualified to be CSO of a huge corp handling so much sensitive customer data?
She held another position as director of security, but no hands on technical roles ever. It really looks like the resume of a middle manager who moved to CSuite. I didn't see anything that indicated she was technical
Don't hire an unqualified person. These two things are not equivalent. Their major in college is only one small part of that picture.
I have known people without degrees (or without relevant ones) that learned on their own and were great. I have known people with a CS degree that were terrible.
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.
The Berkeley Overmind was designed for a 2010 Brood War competition. The website (http://overmind.cs.berkeley.edu/), although no longer updated, still contains many videos and links to articles that describe the internals of the AI and the design process. The Ars Technica article in particular goes quite in depth.
At the very least I don't think Flutter is wrapping native UI components. Flutter renders its own widgets written in Dart and using Skia as the underlying graphics library. So it seems more like QML in that sense.
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.
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