5,255 karma · joined May 21, 2009
http://www.maxcantor.net
my name is max cantor.
my email is firstname at firstnamelastname dot net
purveyor of vim cheat sheet posters
http://www.vimcheatsheet.com
HN cut out the middle man. Instead of linking to something on Reddit about 4chan, we finally just linked straight to 4chan.
To phrase it differently: I feel comfortable with a framework or community forcing me to change how I achieve some higher-level goal. But when that convention prevents me from doing something, period, I start to worry.
These are merely two perspectives from which we can view the same phenomenon.
1.) He doesn't care whether the guy is the thief. He is publishing the photos in an act of non-vengeful vigilantism, with the hopes that someone will see or recognize the guy and contact the OP.
2.) He is assuming the guy is the thief. And, he is publishing the photos to harass/humiliate that person.
Personally I am comfortable with #1 but certainly not #2, for the reasons you cited. In #1, the guy's innocence (or lack thereof) is irrelevant to the OP's motivations.
This is actually a very empowering mindset: If you push a "Pull" door, or pull a "Push" door, you are not the moron! In fact, it is the person who put a "Pull"-handle on a "Push" door! This viewpoint turns PEBKAC on its head. If a user runs a script that he thinks will configure his bootloader, but instead it erases his filesystem, who is the moron? The user, or the process which produced a script that can be run in a way that will erase your filesystem?
The worst offenders I've ever seen in this vein are Atlassian. The admin interface to their products, particularly JIRA, is basically a glorified database query GUI; there is no indication how each of the parts fit together, and 9 out of every 10 possible configurations you can create are actually broken.
The problem is that you can't design a better interface without thinking about how other people will actually use your app, and that's extremely difficult. However, it's useful to look out for signs that you are Doing It Wrong. The "programmer's interface design" from the article is one of them. Another is the phrase "Well, at some point, somebody might want to..." If you hear this phrase repeated frequently during discussions about feature or interface design, panic! It means you don't know what your use cases actually are.
This is one of the ways I think Agile development can be extremely helpful, but no one seems to practice it in a way that leverages this type of benefit. Thinking about things in terms of user stories forces you to make these kinds of decisions, and you almost can't help but design the interface better.
Also, are you uncomfortable with the publishing to the extent that it is a punishment? I interpreted it as an attempt to get people's attention and thus make it more likely that his property is returned, rather than a punishment.
Reading stuff like this always makes me feel like a second-rate geek! I've had my fair share of soldering iron burns (for my senior project in college, I cracked open an RC car's remote and connected it to a BASIC stamp, which I controlled via RS-232 and a network socket), but the parts of this article which the author considers "easy" stuff are still a mystery to me. For example, "According to the application note I could use a simple signal diode, so I just pulled a 1N4148 diode out of my component drawer." A simple what diode? A 1N4-what diode? My component drawer? I don't even have a... help! S.O.S.! Man overboard!
I'm sure that I could come to feel more comfortable with stuff like this if I went out of my way to learn more about it, but the applicable extent of my electronics hacking day-to-day has been unplugging the rumble packs from my Xbox360 controller. Most of the things I use on a day-to-day basis are not devices that I feel comfortable screwing around with!
Bacon API?
HFT API?
Physics API?
API API?
(FWIW I did not downvote you)
... FOR NOW! (dramatic reverb)