199 karma · joined April 9, 2019
Certainly purchase data is very powerful (ask supermarkets!), but I think it pales in comparison to the breadth of data Facebook and Google collect.
Have you a good source for that? I seem to find lots of unclear sources. I found a source that they are down from their peak in 1993 (this source was 2013: https://www.pewsocialtrends.org/2013/05/07/gun-homicide-rate...), but that the last 10 years has been a climb back up (https://edition.cnn.com/2018/12/13/health/gun-deaths-highest... which I sourced from wikipedia, and granted is overall deaths rather than just homicides)
Edit: rather than trying to read OP's mind or surmise what they may be thinking, I'll give my own experience on this. I have seen companies spend money on diversity as lip-service, or targeting groups that don't really aid diversity much.
As much as I support female/LGBTQ/race rights and diversity, I suspect many companies I have been a part of would have got a better number of "units of diversity per dollar spent" had they spent money on people from lower socio-economic classes, or countries with poorer education/access to facilities (or maybe combined with the previous groups; I suspect the middle+ classes of female/LGBTQ/different ethnic origin groups are far better catered for than their working class counterparts).
But perhaps people don't consider social class or country of origin diversity? Perhaps "we hired lots of underprivileged people" doesn't give as much political capital? I'm not sure.
- Typescript type system is pretty awesome, and allows the expression of some things really elegantly; in particular, string literal types are quite cool for component props that feel "htmly", union and intersection types are great for making reusable/generic components and Partial<T> is cool for making typesafe component states (https://www.typescriptlang.org/docs/handbook/advanced-types.... is a great resource)
- on a related note, the Typescript docs are very comprehensive
- ... but docs for anything React related to Typescript (types of components, etc) are harder to come by
- for the actual UI code there is some time wasted getting type signatures perfectly correct, particularly for React and HTML components, but I've built up a bank of helper functions in this regard.
- using `any` nearly always comes back to bite you as you trick yourself into feeling typesafe
- there is always a tradeoff between having perfectly exact types and not writing 139587123598 interfaces; expressing, for instance, mapStateToProps, mapDispatchToProps and mergeProps to compose into component props, or the former as a subtype the latter is pretty fiddly to get right and imo not worth the extra code
- create-react-app typescript support has gotten pretty good now, but it's nigh-impossible to step outside their boundaries. For me, some older features of typescript I wanted that protobufjs generated typescript used was just not usable and I had to work around that with great difficulty
- nearly all packages now have type definitions for them which is sick
- at the end of the day, you can still resort to vanilla JS where typescript really, really gets in the way
How much of this did you manually input, and how much is scraped?
Keep up the good work!