I "was" in the same boat as you so don't feel bad. For the past few months I've been writing unit tests.
My application has the ability to receive commands and send telemetry back over a socket to a user interface. This exposes several features in how I can test it's functionality which makes writing unit tests much easier. Good code is code that can be tested well!
Something that isn't taught but is more so learned (I've personally noticed) is architecting your software to be testable. This has really made me think about how I should write code to not just "do it's intended purpose" but also "in how it will get tested".
My application has the ability to receive commands and send telemetry back over a socket to a user interface. This exposes several features in how I can test it's functionality which makes writing unit tests much easier. Good code is code that can be tested well!
Something that isn't taught but is more so learned (I've personally noticed) is architecting your software to be testable. This has really made me think about how I should write code to not just "do it's intended purpose" but also "in how it will get tested".