Last post I explained why I don't teach the SOLID design principles. Read the post for more detail, but the primary reason is that SOLID encourages heavy use of dependencies. Applying SOLID to a codebase for even a short time will yield dependencies on abstractions everywhere -- quickly producing a codebase that is unintelligible.
This is just a spot to keep miscellaneous links. It also shows you what a geek I am.
Friday, September 26, 2014
Beyond SOLID: The Dependency Elimination Principle
http://qualityisspeed.blogspot.com/2014/09/beyond-solid-dependency-elimination.html
Friday, September 05, 2014
git cherry
My mnemonic for git cherry, i.e. git cherry upstream [head]
My quick understanding is that in many cases it means: show me everything that's NOT in upstream.
In other words:
git cherry branch-without-stuff branch-with-stuff
or
git cherry less-stuff more-stuff
or
git cherry present future
or
git cherry past present
So to see what's in develop but not yet in master, type this:
git cherry master develop
Which means, essentially, show me everything in develop that's not (yet) in master.
My quick understanding is that in many cases it means: show me everything that's NOT in upstream.
In other words:
or
git cherry less-stuff more-stuff
or
git cherry present future
or
git cherry past present
So to see what's in develop but not yet in master, type this:
git cherry master develop
Which means, essentially, show me everything in develop that's not (yet) in master.