What’s in a (s… on Semantic versioning APIs of .N… Semantic versioning… on What’s in a (strong)… SOLID refresher | Cr… on The open closed principle… What's in a (St… on What’s in a (strong)… GrahamTheCoder on Tool Up!
Tag Archives: DotNet
Package managers are awesome. Here’s a versioning scheme that can ease the pain of complex dependency graphs, while encouraging library authors to think about their consumers. Continue reading
Ok, so it’s probably more than seven, but people who are attracted by clickbait would be scared off by the true number. The great thing about increasing user focus in the development process is that we become more likely to … Continue reading
Update: I wrote a more recent post on this topic Package managers Package managers are brilliant. The obvious win is the convenience of versioning your dependencies without having to commit binaries to Git. Lots of people use package managers for third party dependencies, … Continue reading