514 karma · joined October 2, 2019
"They just so happen to look like gorillas!"
This is not okay.
I know it's just a pile of linear algebra and there's no conspiracy to screw a particular country.
But once it's brought up that your system is causing harm by increasing inequality in the world, you can't just say "But that's what the algo is spitting out!".
At least try to fix it.
Your IP is coming from the cloud just like all the actual bot traffic.
That was my main concern when I was looking into firebase a while back. Just wondering if the situation has improved.
This is in part because an article about pig facial recognition frontpaged on HN before: https://news.ycombinator.com/item?id=19277846
From their site: https://www.sqlite.org/whentouse.html
>SQLite does not compete with client/server databases. SQLite competes with fopen().
I only thought about it because I was also saving the expiration in a session table in mysql and my expires column is a `timestamp` which is 4bytes. I was using a language that uses more than 32 bits for dates, so you're right, it probably would've sent out the right cookie.
Apparently there's no good way to do this other than pick a date that's far enough out in the future.
A stackover answer gave an example setting it for 10 years. I thought I would be defensive and set it to 20 years.
But then it will immediately break because 32 bit dates wrap around in 2038!
To play devil's advocate, "objectively" these beheadings are still happening somewhere in the world. It's an undeniable truth even though you don't want to see the evidence for it. For a lot of people this is their flat earth. No evidence means it's not happening.
Why not allow the content to be seen, let the world be horrified that there are people driven to become like this, and try to understand what led them to do those things?
This is because most content is self-policing by upvotes. Downvoted post dies in new so trolls know they can't reach a large audience. It's actually kind of amazing how quickly can newcomers can learn and adapt to the implicit rules and begin reinforcing it on others.
This does lead to problems when a smaller sub gets brigaded by a larger ones (or ends up on /r/all) and the original community can't outvote the outsiders.
That said, style warnings are incredibly hard to detect and enforce (e.g., -Weffc++ is so noisy I've never been in any codebase where I could leave it on)
The best way to learn something is by contextualizing it. For example it doesn't matter if you forget a math formula if you know how to re-derive it. If the formula is truly important, every time you access it, the entire DAG of knowledge leading up to that formula will be "refreshed". This is a very natural spaced repetition that erodes from the edge of your knowledge graph since the basic building blocks are refreshed so often. New knowledge is extremely easy to acquire, and your graph can be "refactored" every so often.
The space repetition apps I have use doesn't have a similar concept of interrelationship. For example it's possible for you to learn the flashcards for "three" and "one" but not know the word for "two". This is insane way of doing things. You are just refreshing random isolated nodes. Not only does it make it a lot harder to learn (since random out of order information is harder to compress), the knowledge graph you build is a tangled mess that's not as usable and doesn't degrade gracefully.
`npx create-react-app some-app-name --typescript`
(it was actually exactly 1000 dependencies which is freaking me out because the number was so round. wondering if it am counting lines wrong `ls | wc -l`)
https://dribbble.com/shots/popular/animation?timeframe=ever
Codepen has stuff you can actually see source code of:
Also New York Times and other news site sometimes have really sophisticated interactive story telling or visualizations.
Game development? Much lower pay relative to other programming jobs, insane hours, and usually requires much deeper and specialized skills.
I guess it's not low pay on an absolute scale like teaching is.
What I found helpful was to prototype all the migrations and queries (of whatever feature or user flow you're building) in a .sql file first with mocked values. You'll be surprised by how much you can do if you're simply forced to write pure sql. Once you've reached the limit of what you can do you can move the queries back into your app to wire the rest up. This is usually not much work if you use raw queries instead of ORMs. You usually end up writing a lot more efficient apps this way!