I wonder which country will be the first to be run entirely by AI instead of corrupt politicians
HN user
d0m
former technical co-founder: http://www.listrunnerapp.com http://www.hackinghealth.ca
phzbox at gmail @phzbox
Apple/Google could easily make web apps native if they wanted
No, the distinction is that he had the option to remain at YC if he chose to. He could have simply turned down the offer from OpenAI. It's similar to receiving a job offer from another company... you’re not being dismissed from your current job. You get to decide whether you want to stay or move on.
I was thinking about this just the other day. If infinity isn't actually a thing in our universe, then maybe we're taking some risks by using math with all these infinite limits and integers. Maybe if we look at theorems without using infinity, we'd stumble upon new or different equations.
Hands down the best book I've read to level up my UI game. Highly recommended to developers who want to get better at UI design with no bullshit and a lot of practical examples.
Run the Alpaca chat and ask it :)
Personally, I used to be very passionate about coding. but over time I've realized that I'm more excited about products/design and working with great people. I know that going into management is often frowned upon among engineers, but I personally love it because I can continue to work on products without constantly banging my head about compiler errors or annoying bugs. Basically, what I'm trying to say is that it's possible to be passionate about building products without having to sit and code all day.
Very cool! I have such fond memories of The Little Schemer
That landing page is really amazing
I love this. How does it work copyright-wise?
Quantum Mechanics: The Theoretical Minimum --> Great book to learn about quantum mechanics and as a side effect math
Not that I care, but you could even copy the current twitter usernames to your new twitter, alongside all their public tweets and followers. So, when switching, a user wouldn't even need to add back their data or find back their previous followers.
Working on an offline/real-time library for agnostic backends. (Most libraries force you to go with a specific vendor like firebase/aws) or use a completely different backend/db (like couchdb/pouchdb).
Personally I really enjoy his writings on all kinds of subjects (coding, political, parenthood, startups, etc.) He's the main reason I did a startup and joined YC. I'm still a bit sad I didn't get to talk to him while I was at YC.
What's the best resource(s) to learn D3 for an experienced dev? I find most books/tutorials to be overly verbose.
I don't particularly like Apollo, but the reasoning is that if you fetch data with Apollo on the client-side, then that data is already available in their cache. If you were to use Redux, you'd have to copy that same data in your store.. so might as well use their cache instead. However, this is only for fetched data, not all client-side state management.
Personally, I don't like the "write client-side resolvers mimicking the server resolvers" approach. I'd much rather have a database that is synched with the server and listens for new changes. Once you have your "offline-synched-db", you get offline, optimistic-UI & real-time for free.
TL&DR: devs already knew redux so went with redux
For some market it is. Our users were 80%+ on ios
There are many design issues with their website which IMHO don't provide great confidence in using their components
Yeah.. Ideally you can find a job that plays to your strength. If you don't like and aren't good with this type of work, it's probably a sign that you should focus on something you find easy and like. It's easy to be good when you really enjoy something
Question from a non-ML expert: How can I be sure that my code working with one version will still be working after they update/re-train the models?
More specifically, for DOTA, they could track the progress and make sure there wasn't important regressions.. but this seems so general, how can they make sure it makes everyone' use-cases better?
Also discourse
Congrats on the launch, it looks awesome. I wished I had that a few years ago and will definitely give it a try
My friends and family are using Messenger rather than Facebook for that exact purpose.
I think they use "Close to the metal" as a way to say "Less abstractions"
Yeah, that's something I was discussing with a friend too. Would be great to be able to shop fresh food online in a way that's more similar to how we do it in a physical store.
I used to have the opinion that modals were bad, but now I think there's a good middle-ground where a lack of modal sometimes generates implicit states with many edge-cases that makes the UX more complex.
Seems like a bug or probably an oversight. Don't think that was intended
Here's how I look at it.. when writing code, you need to run it to try it.
Often people refresh the browser or re-run their CLI program until their feature is finished.
But if you think about it, every "refresh to check if it works" is just a manual test. TDD is just making that manual test automated.
1. Write that test (that you'd anyway have to run manually)
2. Write code until test pass
3. Repeat 1 until done.
Code that aren't designed with a test-first mentality is often really hard to test and require complicated tools or need to mock the whole world.
For the examples you've mentioned:
- I'd unit tests the db service layer (I.e. functions to fetch from db, make sure schema is valid)
- I'd unit tests the various API queries (I.e. filtering, pagination, auth)
- At the controller level, I'd just unit test the business logic and data fetching part.
- Then I'd add a few E2E tests for the UI and user interactivity.
But if you think about it, any of these tests would have had to be run manually anyway. I.e. You'd probably have queried your API with various options and refreshed the page(s) a few time to make sure data was fetched correctly.
^ This
Also:
1. cut features and enjoy saying no.
2. set deadlines and ship (if not enough time, see 1 above)
3. don't skip tests; makes refactoring/rewriting a breeze