benstopics

8 ms·

1. 61.▲
   by benstopics 4y ago

   “ Never fix a bug and refactor in the same pull request.” I’m sorry, but this is backwards. Bugs are many times caused by badly written code and you can tell when it’s the case. Refactoring the code many times fixes the issue without ever h
2. 62.▲
   by benstopics 4y ago

   Thanks for building this. The speed boost is pretty insane, this would actually be great for an API layer for performing multiple operations on large query results in memory to reduce requests to the database. I imagine you could add a simp
3. 63.▲
   by benstopics 4y ago

   This is an interesting concept. Reminds me of changingminds.org which I am guilty for reading hundreds of his pages. An idea I had was a way to login and keep track of what pages you’ve already read or how many times you’ve read them so you
4. 64.▲
   by benstopics 4y ago

   Thank you for 1) making the font I’m actually going to try using it in VSCode simply because I think it will be fun and oddly enough easy to read, and 2) teaching me what a ligature is.
5. 65.▲
   by benstopics 4y ago

   I think you are doing it correctly, you just need to break that iceberg into smaller chunks. You’re getting caught up in the ideological nonsense that surrounds TDD and Scrum. “It can categorize a single transaction correctly” should be tra
6. 66.▲
   by benstopics 4y ago

   I think the issue with this is that as individuals we attach our identity to our dialog and put it out into the world to share it, express ourselves, to provide value to the world, and also to collaborate and iterate and learn ourselves… wi
7. 67.▲
   by benstopics 4y ago

   The first thing that came to mind was either for/else, try/except, or refactoring out to a function which were all mentioned in the article. This solves the problem in all cases except a multi-level continue as it was called, and
8. 68.▲
   by benstopics 4y ago

   EDIT: I put a lot of emphasis on testing but didn’t mention what technologies I would use. For C# I would use XUnit or something similar there’s a few good ones. For integration testing specifically the db and api layers together I would us
9. 69.▲
   by benstopics 4y ago

   My choice of techstack has nothing to do with the feature list because at the end of the day it is whatever gives you an advantage which is whatever you are better at than everything else so long as it has a rich third party library ecosyst
10. 70.▲
    by benstopics 4y ago

    You could scale the API with Kubernetes and MySQL with Vitess off-the-shelf or architect the sharding yourself. My only concern with MySQL would be that, contrary to PostgreSQL, you can’t rollback DDL statements which makes migrations a PIT