garybernhardt

6 ms·

1.
by garybernhardt 15y ago
It's on the front page, but at the bottom. DAS is a small one-man business, so I did the design myself (and I'm not a good designer). Sorry about that. :)
2.
by garybernhardt 15y ago
It's a joke. Relax.
3.
by garybernhardt 15y ago
I like the sliced screencasts because they're so repeatable. I practice my talks a lot, and I can get the timing down perfectly because it's always the same. Highly recommended. :)
4.
by garybernhardt 15y ago
No, it's more subtle than that. By wrapping in parenthesis, you're making it an expression. When you just say "{}+[]" in e.g. Chrome, the first {} is parsed as a block. So what you see printed is the result of "+[]", which is 0. This is why
5.
by garybernhardt 15y ago
There's no laugh track; that's the audience.
6.
by garybernhardt 15y ago
It's Keynote. I recorded those sessions as screencasts, then sliced them into tiny pieces so I can advance them perfectly with my talking. There are 37 slides in that four-minute talk. In some cases, the slices are only two or three frames
7.
by garybernhardt 15y ago
I could port it to Python if you want? ;) I probably wouldn't have done this when Python was my main language, though. That community has a much harder time laughing at itself than Ruby's does.
8.
by garybernhardt 15y ago
Done: https://github.com/garybernhardt/base/commit/65e8ca5d432be72...
9.
by garybernhardt 15y ago
I was tempted to leave the disclaimer off, both in the README and the blog post. But I think there's a strong enough chance of someone actually using it as it is... ;)
10.
by garybernhardt 16y ago
You can just create a new branch before you start the rebase, which achieves exactly the effect you ask for. Rebase is how you "create a new branch with only the clean commits". But, most of us don't bother copying before rebasing. The refl
11.
by garybernhardt 16y ago
I don't rebase everything. Merges still have their place. An early draft of this post talked about the relationship between rebase and bisect, but I cut it out to focus on one topic. The tl;dr is that heavy merging makes it harder to reason
12.
Rebase Is Safe(blog.extracheese.org)
24 points by garybernhardt 16y ago|27 comments
13.
by garybernhardt 16y ago
This is my personal list of RSS feeds, which I've been curating for many years, so I knew exactly what data was coming. It was a one-time hack: it got my RSS feed list into the database, and was never excuted again. It was also only for loc
14.
by garybernhardt 16y ago
JSON syntax is Python/Ruby primitive syntax for lists and strings (although the reverse isn't quite true). Why add a library import and additional code on each side just to emit and consume what is effectively the same data? :)
15.
by garybernhardt 16y ago
I considered using Vim at the time. The nice thing about doing it all on the command line is that it's repeatable and persistent. I have a huge shell history, and that command will now be in my history for months. I rely so heavily on my hi
16.
by garybernhardt 16y ago
I don't think that Google Reader can export as JSON... ?
17.
by garybernhardt 16y ago
Also, MQ's "qdel" command is the one that led to the data loss mentioned in the original blog post. So it doesn't really answer my concerns. :)
18.
by garybernhardt 16y ago
I often do it multiple times per minute. That wouldn't fly if each required a clone. :) (See another post I made in this thread for what I'm doing that involves so much history mutation.)
19.
by garybernhardt 16y ago
Yep – and I did it all, using those tools, for a couple of years. :) Now, when I go back to Mercurial (which I know better than Git, mind you), I get frustrated. Those tools are much more blunt than their Git equivalents.
20.
by garybernhardt 16y ago
Git gives me everything I needed MQ for, but with the complete safety of the reflog. There is no such thing as a change I can't undo. The fact that patch management is "special" in Mercurial is the problem! With respect to history modificat
21.
by garybernhardt 16y ago
Did you read the end? ;) """ I'm sorry for recommending software with a confusing interface. But you'll be spending a lot of time with it; it's worth getting over the initial hurdle of confusion. """ Note that I call it the " initial hurdl
22.
by garybernhardt 16y ago
The command that lost data was hg qdel. Strip won't lose data; it dumps bundles (although they're a pain in the ass to restore from). Like I said, I used Mercurial for three years. And not "I play with it sometimes at night" kind of used, b
23.
by garybernhardt 16y ago
Augie, I understand what you're saying, and I don't buy it. Git, when taken as a full DVCS capable of rewriting history, is safer than Mercurial, when taken as a full DVCS capable of rewriting history. A DVCS that is incapable of rewriting
24.
by garybernhardt 17y ago
I'll think about it. With the awful response from Reddit [1], I'm not sure that I want to make another go at it. :) We'll see. To respond to your example, I'd almost certainly go with something like your Count_Xs_in_Row path, or some simila
25.
by garybernhardt 17y ago
This post was aimed at the person who is interested in TDD, but hasn't had their first big insight into how it works. It's about "do the simplest thing", not about a full TDD process to build a working production system. As I said to someon
26.
by garybernhardt 17y ago
The thing preventing infinite implementation is a combination of (1) the rules of simple design and (2) the definition of "simple". I write about those in the follow-up to this post: http://blog.extracheese.org/2009/11/the_limits_of_tdd.ht