nolemurs

16 ms·

121.
by nolemurs 10y ago
I think you maybe misunderstand the point of this web site. The designer has no interest in selling all or even most of the logos at the sort of market rate they could actually command. The website is much more useful as a portfolio/ma
122.
by nolemurs 10y ago
The title of this article should really be "Why bad scientific code beats bad software engineer code." It contrasts a bunch of bad things scientific coders do, and a bunch of bad things bad software engineers do. There's no &
123.
by nolemurs 10y ago
> prefer powerful and efficient tools that I can use without any learning, since the two aren't mutually exclusive. They're not necessarily mutually exclusive, but in my experience there's often a trade off. I would argue
124.
by nolemurs 10y ago
So, here's a question. I make a commit to implement a feature, then I realize there's a bug in my implementation, so I fix the bug, and then squash it into a single commit. What is the scenario where anyone is going to be perusing
125.
by nolemurs 10y ago
I mean, I'll agree, if you insist on trying to create an abstraction to understand git, you can beat your head against the wall for days trying to figure out how it works. On the other hand, if you just take a couple hours to really tr
126.
by nolemurs 10y ago
So you want a long command line argument were you tag specific line numbers and have to get it all right at once? That sounds terrible to me. Being able to add bits and pieces to your staging area and then once you've got it all ready
127.
by nolemurs 10y ago
If you don't have `stage` how are you going to generate a commit which has only some of the changes you've done (potentially including partial commits from files)? `stage` is unnecessary if you have a really simple workflow, but i
128.
by nolemurs 10y ago
Once you understand Git's data model, the UI is perfectly intuitive and very efficient. When you want to do something in git, it generally requires just a single command - you just have to know what you actually want to do. Attempts at
129.
by nolemurs 10y ago
You have to think about the purpose of the history. Git history serves a few purposes. First, it provides an overview of development so that someone can use `git log` to quickly figure out what's been done. Second, it provides context