moss

6 ms·

1.
by moss 8y ago
Thanks for this -- I can't speak for the person you're responding to, but I had the same confusion and it was definitely because I was thinking of Cringely.
2.
by moss 10y ago
I'll often use sequence diagrams or entity relationship diagrams when I need to explain how a piece of code works (or even just visualize it for myself). I don't tend to be very pedantically correct about it, but having a picture
3.
by moss 11y ago
All the time. Many times per day. I've been programming for fifteen years, and I think my willingness to Google things has only gone up over that time. There are a lot more things that I know off the top of my head now than when I star
4.
by moss 12y ago
This article is from a year ago and change. Have there been any recent developments? I've seen the link going around lately, but I can't tell whether it's because there's news or just because it happens to be going aroun
5.
by moss 12y ago
Having lived through this winter in the Northeast, I can promise you that SF is beautifully warm all year round. Case in point: it is a place where people use the word "freezing" to describe temperatures 10-20 degrees above the me
6.
by moss 13y ago
::cries::
7.
by moss 13y ago
There are so many things to love about this speech, but I think my favorite part is this: "the only thing that actually works is not ideological, it is impure, has elements of both arguments and never actually achieves any kind of part
8.
by moss 14y ago
Pairing with other experienced programmers works very well for me, and has made me more effective as a programmer. I've also seen our junior developers learn a lot from pairing with each other. In my working environment, with other people w
9.
by moss 14y ago
The article's link to the original paper doesn't seem to be working. Here it is: http://csis.pace.edu/~grossman/dcs/XR4-PromiscuousPairing.pd...
10.
by moss 14y ago
My understanding is that the Promiscuous Pairing idea was started by real developers working on a real project with tight deadlines. The point of the paper is that, counterintuitively, the approach worked very well _in practice_. So I would
11.
by moss 15y ago
You're proposing what sounds like a pretty novel interpretation of the first amendment. Do you have any evidence that it's widely accepted, or that it's correct?
12.
by moss 15y ago
To push the metaphor a bit too far, I think it's more about people realizing they just don't want cake that much. As you say, it's perfectly possible to build a good community if you're willing to put some work into it. People who run commu
13.
by moss 15y ago
This is really slick! It's the first realtime, WYSIWYG tool I've used that still feels like a Wiki.
14.
by moss 15y ago
Consider saying this explicitly during the sign-up process! I avoided using my Google account to log in, but I probably would have gone ahead and done it if I'd known that you weren't going to email my contacts.
15.
by moss 15y ago
* There are memorable keyboard shortcuts for everything. * It can generate comparatively more code for you. * It's faster, though I fear it's working on losing this advantage. * The autocomplete is smarter, and has a few different options.
16.
by moss 15y ago
Much of the time, I'd agree. But working on a large system in Java, I repeatedly see a few places where Java's boilerplate overwhelms the code I actually care about. Operations on collections: List<String> result = new ArrayList
17.
by moss 15y ago
It's suitable, not suitible - normally I wouldn't be so pedantic, but in a thread around the idea of people having to prove they know meanings/spellings/etc, it seems apropriate.
18.
by moss 15y ago
The building I work in once had a contest: whichever floor recycled the most paper in a month got an ice cream party.
19.
by moss 16y ago
Tempting, but the system's only covered by end-to-end tests that take years to run. I'm afraid to change it!
20.
by moss 16y ago
This is delightful. What I'd really like to see now is one that could learn from people's reactions to it: pay attention to which of its tweets were retweeted or favorited and try to generate more like those.
21.
by moss 17y ago
I think I'm blithely misreading the article here, but I'm inclined to take it as advice about how to do TDD, rather than an argument against it. Specifically: if a class has lots of tests, this is a sign that the class is too complicated. R
22.
by moss 17y ago
My favorite thing about this article is that it made me stop and think through why the bug would actually exist in so many browsers. I can make sense of the IE bug: "" doesn't start with a protocol, like " http:// , so it's not a full URL.
23.
by moss 17y ago
It sounds like your philosophy of testing is about what mine was a year ago. Since then, I think I've modified it in two big ways: 1) I've found that potential bugs, and design problems, are often easier to spot at a lower level. Because of
24.
by moss 17y ago
If you clicked that link, you have not actually disabled your public profile.
25.
by moss 17y ago
Sane people do not always have sane exes.
26.
by moss 17y ago
What is the proposed benefit of publishing badly researched articles making weak arguments for both sides?
27.
by moss 17y ago
http://www.diagrammr.com/edit?key=dFE4tu7OUIr
28.
by moss 17y ago
You're right: calling it "very easy" was overstating things to the point of absurdity. I do think Java's behavior has a big advantage in being easier to understand than the theory behind it is ("less than 10%"), but I had completely glossed
29.
by moss 17y ago
What iron_ball said, plus a share of "I agree so strongly that I almost want to just repeat everything you said". Alternately, it could mean: "I was reading LiveJournal five minutes ago, and haven't quite finished switching over to the Hack
30.
by moss 17y ago
This. Java sets up an environment where the parameter passing behavior just isn't surprising. If you've been programming in Java for a little while, it's very easy to have an intuitive feel for how parameters will act, without having to go

More ›