Live data from Hacker News

Steve Yegge: Notes from the Mystery Machine Bus

plus.google.com

151–160 of 186 posts

Re: Steve Yegge: Notes from the Mystery Machine Bus

#151
post #28

As much as some commenters are (weirdly?) railing against this classification scheme I think the underlying idea that software conservatism is about risk aversion is essentially accurate. Perhaps another way of framing this is to ask the question: are you optimizing for the best case or the worst case? This ultimately is a form of risk management. And I'm not talking in the algorithmic sense, meaning complexity expre…

Yegge took a massive shit on technical discourse, and if not countered, the ramifications thereof could be felt for years . His influence is disproportional to his value, and I am extremely disappointed to see anyone here taking his emotional arguments seriously. Unless firmly censured, I expect to see Yegge's ridiculous viral meme of "liberal vs. conservative" spread and repeated by inexperienced developers indefini…

I couldn't agree more. I shudder to think of a near future in which discussions include this "libral" or "conservative". I don't think it is nonsense because I think "it's a bad dichotomy for politics." I think it is bad because it is a poorly formed idea that reminds me of a high schooler learning some new thing and trying to apply it all over the place and see it everywhere like a psychoanalyst.

But the worst part about this is it is a pretty useless discussion despite the claims that this is some revolutionary culmination of a series of wildly over blog posts.

Re: Steve Yegge: Notes from the Mystery Machine Bus

#152
A political philosopher "he ain't." I still get the hype of Steve Yegge, I guess he's a writer only software blog audience world could love. It was soooo loqacious; he doesn't disappoint. :)

Nevertheless, I don't know which was worse, the claim about what political conservatism/liberal is or the software one. I guess the software doesn't matter because he's just making it up anyway, but still. Before anyone thinks too highly of this piece, I recommend people study some actual philosophy and humanities.

At it's very core this is just an elaborate (not in a good way) dressing up of the static vs dynamic typing discussion; hardly a revolutionary insight. I also don't see how this is "risk" based debate. But in any event, this is just hard to take.

Re: Steve Yegge: Notes from the Mystery Machine Bus

#153

Earlier quoted context omitted.

Most technical discourse turns into religious zealotry, and I think Yegge's observations are relatively true. For instance, look at all the debates on static typing versus dynamic typing. If you break it down, it boils down to aesthetics and fuzzy feeling. It really does. Interestingly, as I've aged, I've realized that our tools don't matter. All code turns into shit. At the end of the day thou, once you pick your to…

> For instance, look at all the debates on static typing versus dynamic typing. If you break it down, it boils down to aesthetics and fuzzy feeling. It really does. It boils down to cost vs benefit, actual studies, and mathematical axioms, not aesthetics or feelings. > How we ship products doesn't matter. All that matters is that we ship. Engineering tools affect both how you ship, what you can ship, and when you can…

>It boils down to cost vs benefit, actual studies, and mathematical axioms, not aesthetics or feelings.

Its not quite that simple. Well performed studies that are actually relevant to a particular project are _difficult_ to come by. By well performed, I mean free of biases and misattributions and relevant to your particular use case. For example, most of the links in the answers here (http://programmers.stackexchange.com/questions/10032/dynamic...), a question specifically requesting studies them don't have any significant empirical data. Further, if you dig deeper its also clear that studies often contradict each other. Further, lets say you try to do a cost-benefit analysis. How? Try to estimate how many hours a particular technique will save you and you run into the same problem people have been trying to deal with for years. Estimating the time it takes to do a project is _hard_. Add to that how rapidly things are changing in this space and how dependent the structure of code is on the application of that code, and its clear that we really don't have objective metrics for this kind of thing.

>Engineering tools affect both how you ship, what you can ship, and when you can ship it. The choice isn't arbitrary, and choosing involves careful reasoned thought, informed by real experience

This is far more revealing of how these decisions are actually made. Your experience and thought process may very well be arbitrary when contrasted with real data. It might as well be aesthetics and fuzzy feeling.

Re: Steve Yegge: Notes from the Mystery Machine Bus

#154
post #28

As much as some commenters are (weirdly?) railing against this classification scheme I think the underlying idea that software conservatism is about risk aversion is essentially accurate. Perhaps another way of framing this is to ask the question: are you optimizing for the best case or the worst case? This ultimately is a form of risk management. And I'm not talking in the algorithmic sense, meaning complexity expre…

Yegge took a massive shit on technical discourse, and if not countered, the ramifications thereof could be felt for years . His influence is disproportional to his value, and I am extremely disappointed to see anyone here taking his emotional arguments seriously. Unless firmly censured, I expect to see Yegge's ridiculous viral meme of "liberal vs. conservative" spread and repeated by inexperienced developers indefini…

I basically agree with you but:

> I expect to see Yegge's ridiculous viral meme of "liberal vs. conservative" spread and repeated by inexperienced developers indefinitely.

It's worse than that. Just look at this thread. I'd say most HNers aren't inexperienced developers, and yet they seem to be taking Yegge's sophistry seriously.

And I don't think his post necessarily "makes people dumber" for having read it. That's only the case if people accept it without a modicum of critical sense. And if so that's their own damn fault.

So I agree that that post is of very low quality. But still, I admire Yegge. His genius here is to frame the discussion so that it disarms the natural geek propensity to read technical discussions with a critical sense.

Re: Steve Yegge: Notes from the Mystery Machine Bus

#155
Great and obvious, but is this really new?

I think the issue he captures has been well known for a while. It is structured versus unstructured. Neither is better in an absolute sense, but one method can be better than another in a given situation. This is beyond just software, but business approaches in general. Startups are generally liberal/unstructured, Dow Jones firms are generally conservative/structured.

Re: Steve Yegge: Notes from the Mystery Machine Bus

#156
post #28

As much as some commenters are (weirdly?) railing against this classification scheme I think the underlying idea that software conservatism is about risk aversion is essentially accurate. Perhaps another way of framing this is to ask the question: are you optimizing for the best case or the worst case? This ultimately is a form of risk management. And I'm not talking in the algorithmic sense, meaning complexity expre…

Maybe you are unaware, but Java's checked exceptions are generally seen as a mistake (only slightly less so than C++'s checked exceptions), and really only made sense for Java's originally intended purpose: embedded systems.

Re: Steve Yegge: Notes from the Mystery Machine Bus

#157
post #28

As much as some commenters are (weirdly?) railing against this classification scheme I think the underlying idea that software conservatism is about risk aversion is essentially accurate. Perhaps another way of framing this is to ask the question: are you optimizing for the best case or the worst case? This ultimately is a form of risk management. And I'm not talking in the algorithmic sense, meaning complexity expre…

Yegge took a massive shit on technical discourse, and if not countered, the ramifications thereof could be felt for years . His influence is disproportional to his value, and I am extremely disappointed to see anyone here taking his emotional arguments seriously. Unless firmly censured, I expect to see Yegge's ridiculous viral meme of "liberal vs. conservative" spread and repeated by inexperienced developers indefini…

He right about it being political, and about there being different contexts. The liberal & conservative labels unfortunately misframe the discussion in to a political context, and a bi-partisan one. Worse, he did it in the midst of election fever (gee, you think that is a coincidence?).

Basically, you can write off intelligent discourse for the next few months, but this too shall pass.

Re: Steve Yegge: Notes from the Mystery Machine Bus

#158

Earlier quoted context omitted.

Yegge took a massive shit on technical discourse, and if not countered, the ramifications thereof could be felt for years . His influence is disproportional to his value, and I am extremely disappointed to see anyone here taking his emotional arguments seriously. Unless firmly censured, I expect to see Yegge's ridiculous viral meme of "liberal vs. conservative" spread and repeated by inexperienced developers indefini…

I couldn't disagree more with that. From reading his other essays, it's obvious the guy has a broader perspective on programming than most software developers. I believe it's experienced developers who will spread this because it takes experience in many different languages and paradigms to really understand what Steve described. I have different coding styles for Lisp, Haskell, D, Ruby and CoffeeScript for instance.…

> Steve at least offers a classification for the different styles found in programming communities today. He may not be right on spot, but at least it's a start.

Yeah, he really saved us there. Up until now we had no way of classifying different styles of programming...

I'm wondering how many other people read his essay and immediately thought of this:

http://www.youtube.com/watch?v=p20GYzCnfr0

Re: Steve Yegge: Notes from the Mystery Machine Bus

#159
Yegge's entire essay seems like an application of JWZ's regex admonition. "I know, I'll present my hypothesis using political terminology!" Now you have two problems.

Political terminology in the United States is MASSIVELY warped by entities who spend literally millions of dollars in an effort to connotatively redefine words. When you (re)define words like "conservative" or "liberal" you risk alienating people who have been conditioned to have an emotional response to either definition. If you define a term in a way that seems pejorative to your reader, the reader will weight every subsequent statement against the rigor they think you brought (or did not bring) to those definitions. Your essay will entirely fail to persuade if it rests on (perceived) faulty definitions.

When writing to a largely US audience, no attempt at honest communication will be aided by the application of political labels.

Here's a test: can the essay be rewritten without that political terminology? Reader "nirvana" used the terms "cowboy" and "architect" to describe his two axes. ( http://news.ycombinator.com/item?id=4367328 ) I very much prefer those terms. Yes, they're also connotative and subjective, but as analogies they map much better onto the subject being discussed.

Post reply on HN