SassyGrapefruit

10 ms·

61.
by SassyGrapefruit 5y ago
why? Just go to the commit hash in the blame and run blame again. All in all it has a negligible impact on the readability of the code. It's mostly aesthetic for me. It's ugly and only solves far fetched problems. Do you scratch
62.
by SassyGrapefruit 5y ago
>Moreover, what's the harm? It's more information, not less If your code is outliving your source control system you got bigger problems than whatever is in your comments. I can confidently say that in 25 years in this industry
63.
by SassyGrapefruit 5y ago
Yep. Re-use is difficult. When you overdo it you cause a whole new set of problems. I once watched a person write a python decorator that tried unify HTTP header based caching with ad hoc application caching done using memcached. When I as
64.
by SassyGrapefruit 5y ago
I think most of what martin says is rubbish, but this is not. I have never had `git blame` fail...ever. I know what user is responsible for every line of code. Doing this is contemporaneous. Its right up there with commenting out blocks of
65.
by SassyGrapefruit 5y ago
You were never alone Juggles. We've been here with you the whole time. I have witnessed more people bend over backwards and do the most insane things in the name of avoiding "Uncle Bob's" baleful stare. It turns out that
66.
by SassyGrapefruit 6y ago
Can confirm. I once watched an engineer build a beautiful, functional subscription management system. When I asked him some practical questions he said "Elegant programs allow us to code as though the physical machine doesn't exis
67.
by SassyGrapefruit 6y ago
They are materially different. A pardon reflects forgiveness and seeks to redress civil disability typically as a result of a systemic injustice. A commutation is a lessening of the penalty. It implies that the act was wrong and the sentenc
68.
by SassyGrapefruit 6y ago
"free speech" is like the power of pardon. In that until toxic individuals insisted on testing its most extreme boundaries it was allowed to remain, in theory, nearly unlimited. "Free Speech" is a great thing when it&#x2
69.
by SassyGrapefruit 6y ago
yeah its gone completely sideways for me
70.
by SassyGrapefruit 6y ago
I can confidently say I've never encountered this. To diagnose I'd have to see what exactly you are doing, but I suspect you have issues with the way you organize your work. Git is not a magic wand. Making effective use of a hamme
71.
by SassyGrapefruit 6y ago
Agreed! I have trouble taking anyone's advice seriously(even if they contribute to a major library) when they say the phrase "Never do X". The only thing I feel confident in saying I'll never do is committing to the pros
72.
by SassyGrapefruit 6y ago
This is strawman. If you phrase like this... "Make your code more testable by moving things that are cumbersome/expensive to test but extremely unlikely to break into functions you don't test. Instead focusing your efforts on
73.
by SassyGrapefruit 6y ago
This comprehensive, developer focused eco system has been promised again and again. The challenge is that those metaphors take a long time to create and are fragile. A new need arises or the paradigm shifts and all that equity evaporates. I
74.
by SassyGrapefruit 6y ago
I watch more people overcomplicate their lives when it comes to unit testing. The problem discussed in this article is not one of mock vs. fake its actually about how this individual chose to engineer their application. First I'll intr
75.
by SassyGrapefruit 6y ago
I don't understand your reasoning. >Maintaining safety equipment takes time and effort we could be using for something else You haven't established the relationship between"safety equipment" and your preferred style c
76.
by SassyGrapefruit 6y ago
>If you create and submit small PRs and git-squash those PRs into the main branch, you'll get the best of both worlds. I definitely advocate for this. But I've worked some at some spots with "never squashers" that del
77.
by SassyGrapefruit 6y ago
>I've always disliked Git's squash feature, and here's one of the many reasons to dislike it. Had this happened in a code base with a 'nice history' (as the squash proponents like to present it), that small commi
78.
by SassyGrapefruit 6y ago
>So... Are you saying that moving your ssh port to a different address doesn't actually increase your security at all No I think if you read particularly the "Why all the hate..." paragraph you'll see I'm saying
79.
by SassyGrapefruit 6y ago
This article engages in quite a bit of mental gymnastics to avoid calling this tactic exactly what it is. Security by obscurity What are you doing here? SSH generally runs on port 22. You move it to an alternate port to thwart a naive intru