Posts

Showing posts with the label programming

Extra Life Notifications release v1.0

Image
Just a fun side project I've thought about for several years. My phone notification has been the Mario coin sound since forever, and a friend once joked about making the 1UP sound after 100 notifications. Never had the time to dig deep enough into Android development but was able to put this together with Gemini and Claude assistance. I started the process to publish it in the Play store, but the 12 tester requirement is too much for a personal project, so feel free to grab it and sideload from Github .

Benchmarking C# using BenchmarkDotNet

The other day I came across the BenchmarkDotNet package  and had to try it out , and I think it works really well. Gone are the days of using a stopwatch for ad hoc benchmarking! There's some initial setup cost with creating a new project, but with more deep diving I wouldn't be surprised if a benchmark project could be incorporated directly into a project and/or test suite.

The importance of design for TDD

Image
Stop me if this sounds familiar. You've read multiple articles about the importance of TDD (test driven development) and unit tests. You understand the basics of unit tests and frameworks for mocking up data and examples. Maybe you've created unit tests that helped you in refactoring, or finding issues in the service methods, so you understand the value of good unit tests. But you can't help feeling like you're missing something in how you're doing TDD. Your unit tests are so simple they feel useless, like a test that mocks some data for a repo and then verifies that it got the mocked data. Or maybe you don't even know what unit tests to create, so you start in on your implementation and add unit tests after the fact to cover your code. What's missing? It's possible you aren't doing enough design work to fully understand the problem you're trying solve, and without understanding the problem you can't effectively test the problem. Once you und...

9 Steps Of Software Development

Came across this recently and thought it was an excellent overview of the ideal software development process. As written it's more of a waterfall process, but the flow could also be used for agile processes in smaller iterations. Gather requirements Systems analysis Software design Module design Unit tests Coding Integration testing Systems testing Acceptance testing