It's the only git operation I do with a gui. But as I said elsewhere, there are a lot of little integrations I do make use of. For instance I find it helpful to have git blame up on the side when editing a file.
I almost always operate in my own feature branch, squashing and then rebasing along the way... sometimes I'll just keep amending my feature commit as I work. I find it just saves me a lot of pain along the way.
I think with tools like Claude code you can more easily tackle niche areas that would benefit from custom crafted features and then using the app would feel like it was purpose built for the specific task at hand. Sure the code might not look hand crafted, but if it works and solves problems in the world...
I find inheritance in tests leads quickly to hell. Striving for every last bit of reuse seems like the right thing to do but it hurts in subtle ways that compound over time. If you must, use composition and spend the time on a DSL that clearly documents the setup in each test.
As much in applications code it is easy to curb, for test code it is just really hard to get people to understand all this duplication that should be there in tests is GOOD.
As always, there's a tradeoff. I used to go for doing all setup in each test for clarity, but one of my co-workers eventually convinced me that doing this in a fixture is better.
There'll always be some duplication, but too much makes it harder to see the important stuff in a test.
It depends on how much setup is done, and where it is. 10 tests that share a setup fixture are good. 100,000 starts to get unmaintainable.
I have lots of test fixtures each responsible for about 10 tests. It is very common to have 10-20 tests that share a startup configuration and then adjust it in various ways.
When you say inheritance do you mean DRY as in "Don't repeat yourself"?
I'm not sure what you mean by inheritance in tests but DRY is criminally overused in tests. That could be a whole separate article but the tradeoffs are very different between test and app code and repetition in the test code is much less problematic and sometimes even desirable.
Both actually. But having to open up three files to figure out how this thing is setup and then override setup to change it slightly in my one case. You get the idea. A really good DSL can help in the areas where creating the SUT is very complex.
Even a single cat takes a while to warm up to people. My ten year old tuxedo cat is always by my side or lying on me somehow but he was quite standoffish the first few years.
My parents have a farm cat that purrs around anyone and chases them to get pets. We have no idea where he really came from he showed up quite young one day.
My neighbor had a barn cat that would come up to you and start head butting you and trying to take your food if we were eating on the deck. I'd have to periodically pick him up and take him to the other side of the house which would buy us about 10 minutes.
Another time I had summer company over and he must have sneaked in with doors opening and so forth because I found him later very comfortably situated in my bed.
It depends on the cat. My girlfriend and I have four cats between us. The youngest one was warmed up before she got here (by her choice it seems, she pounced on my girlfriend when she approached her cage in the shelter), and made herself at home within minutes.
Just like humans, cats have their own psychology and their own personalities.
I have to imagine that if a human consciousness were suddenly placed inside a cat body, the experience would rival even the deepest psychedelic experiences.
Similarly, married ten years and my wife and I have never seen each other use the bathroom. And barring dire emergencies I can't actually envision, we never will.
It's stories like these (and poor parenting I guess) that causes things like my cousin standing up to wipe for close to 30 years until his gf filled him in one day.
reply