thinkstoomuch

5 ms·

1.
by thinkstoomuch 10y ago
I think "Best Practices" are a good thing, so long as you understand why they are best practices and in what situations. They are bad thing when they are simply dogmatic cargo-cult programming without that understanding. Moreover,
2.
by thinkstoomuch 12y ago
I follow this workflow: 1. Never do work on a branch that is being tracked on the origin. Always segregate your work on a local-only branch by doing a 'git checkout -b my-work' 2. Since I prefer not to have merge commits that don&
3.
by thinkstoomuch 13y ago
I wholly agree with this, and feel that all project plans should be constructed to mitigate the very high risk of initial estimates. Too many project processes treat estimates as commitments with no backup plan when they (inevitably) go awr
4.
by thinkstoomuch 14y ago
>Comments cannot. I disagree. While the comments won't break your code, they can certainly ease the introduction of bugs, and cause cognitive delays when they're wrong or out of date. Comments need as much care as the code itself, with
5.
by thinkstoomuch 14y ago
Interesting, I come out to 55 degrees this way: 30 degrees between hours. 10 is at 300 degrees, 11 is 330 degrees. 50 minutes into the hour is 5/6 of 30 or 25. 330+25 == 355.
6.
by thinkstoomuch 14y ago
>Stop worrying about the procedural code [...] I don’t see a lot of value coming out of the abstractions we create. I completely agree here. If you're not getting value out of the abstractions, don't introduce them. However, abstraction
7.
by thinkstoomuch 14y ago
To me, technical debt comes in both the intentional and non-intentional form (and more often than not, the latter). In fact, I'm a firm believer that all software tends toward entropy, so feature additions inherently add to technical debt i
8.
by thinkstoomuch 15y ago
From purely circumstantial evidence, this appears to be Backify's issue completely. It's run by Tarandeep Gill, who seems to have garnered a bit of a reputation. He was behind the "IE users are stupid" hoax. source: http://blog.forret.com