• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle



  • When I read Infinite Jest the first time I was in college I was dealing with a lot of “life’s crossroads” type issues, some of which I didn’t even know about until I looked back on them. The book helped me understand that I needed to stop relying on my “innate” talents and privileges and actually start putting in work for the things I wanted if I was ever going to have a hope of a good life. It also put into perspective a lot of substance use/abuse stuff in a really subtle way that ended up being very beneficial to me.

    Now, on my second reading, there is none of the profound and personal wisdom present in the text. It is an enjoyable read, but for completely different reasons. I guess that first read was kind of just a “right place, right time” scenario for me.

    2 years ago I read Divergent Mind by Jennara Nerenberg and it completely changed my perspective on the mental care industry and revealed, with studies and statistics, how women are systematically underserved when it comes to medical issues (both physical and mental). After reading that book it was like a big empathy door was kicked open in my brain that had been shut my whole life, and I suddenly started understanding some of the deep context behind the experiences of women in my life that I was previously never aware of.










  • Well so before you code it you still have an idea of what you want the program to do, right? So you write a test for the program to pass or fail based on that idea of functionality, and then you write the program to pass the test.

    So for something simple like programming a calculator you might write test code that verifies whether your addition function properly adds two numbers together then write the actual addition function.

    Later on as you continue to build the program your addition test will still be out there verifying that you haven’t broken anything with subsequent code.

    Some people will tell you that TDD tends to work better with established codebases in corporate environments where you have huge interrelated programs and maybe hundreds or even thousands of developers working concurrently as opposed to simple projects or startups where you might want to prioritize having a product set out before you start to implement rigorous testing requirements.

    A lot of people don’t like TDD because they see it as extra overhead and don’t want to spend time writing test code when they could be writing “real code.”

    Proponents of TDD tend to point to the fact that it contributes to stability in the overall codebase and allows you to quickly and easily find and diagnose problems, and it can make you a better developer to think ahead rather than just dumping code into the codebase and assuming it’s going to work.