5 ms·
> Light and flexible pieces of wheat straw in San Francisco had easily been conveyed pneumatically from the tub grinder into the hammer mill. Okay, that is a v
by hinkley 4y ago
> Light and flexible pieces of wheat straw in San Francisco had easily been conveyed pneumatically from the tub grinder into the hammer mill.
Okay, that is a very basic failure of engineering/imagination. I’m not saying shame is in order here, but several someone’s should be made to feel uncomfortable over this cock-up. Including the hiring manager because they went for kids instead of people with experience.
Why on earth would you assume you could move corn residues with air? Have you seen a corn field before? Have you touched corn? This is the other problem of moving engineering far away from the problem. SF only sees so many refugees from Iowa and Illinois. Most of those go to Chicago or Seattle.
> But with some deeper searching, we found a great, off-the-shelf belt that would arrive quickly.
Arrive quickly because the locals have been solving this exact problem for a hundred years. When you find an off the shelf solution for your problem, that’s when a good engineer or software developer takes umbrage and considers whether they have a bad, bad case of NIH.
- gammarator 4y agoThe tone of this comment is unduly negative, but I agree that they should be hiring folks with relevant experience. Ag mechanization is a well established degree, combine harvesters and augers exist, etc.
- hinkley 4y agoWe talk about this at least once a week here, usually in the scope of software, but it’s a problem that exists in other domains (though VCs and us are constantly pushing for more businesses to run like software, which is nuts considering how not in order we know our own house to be). Ageism and cultishness are how you end up with simple oversights that anyone who has been around the block a few times would either prevent, or at least have enough self consciousness not to breathlessly talk about it in front of strangers. I think what we miss consistently about the VC model is that we make the 10:1 ratio about chance and betting big, but I suspect the dominant force there is that 4 times out of 5, experience will save you from doing something expensively stupid. However once in a while it’s a clever generalist or someone who “doesn’t know any better” that uncovers a major advancement that the experienced people are blind to. So less than half of those failures are not thinking outside of the box, and most of the rest are not even knowing there was a box to begin with. We tend to see this as an either or scenario. Throw a bunch of kids together or hire a bunch of cranky old men and women who say no all the time. That’s a false dichotomy. Hire some of both, don’t let the older ones steal all of the glory.
- throwaway0a5e 4y agoThis is mostly a cultural problem. Some professions will readily say "imma keep my mouth shut because this is not my area of expertise" whereas every software engineer is a subject matter on everything up to and including open ended and subjective questions that humans have been trying to conclusively answer all of history. (The various types of mechanical engineers are nearly as bad.) One could argue that the cultural problem is just a reflection of a demographics problem but I don't care enough about that aspect to make that argument. As an aside, the failure in TFA doesn't sound that dramatic. Seems like the age old tale of a customer running material handling equipment at the edge of it's comfortable range and an tech needing to be flown out to tell them where to slap vibrators on it or what other minor change needed to be made in order to make it work better. Yeah, they probably should have seen this coming and shipped a more flexible solution or at least have had shovel ready options that didn't involve flying engineers out but whatever, it's a prototype and this stuff happens.
- hinkley 4y agoI belatedly figured out that my whole style of learning is based entirely on model building and testing, similar to what scientists do when they are exploring a new phenomenon. I keep meaning to look around for research on whether this is common to all autodidacts, just one mode, or if I’m rare. The upshot of this is that I seem to be able to avoid the Expert Beginner trap and get into more of an Expert Journeyman, which is somewhat more useful and less dangerous. I’m often deputized to take over things I don’t actually know all that well, because I’m seen as having some knack for playing twenty questions and then being able to improvise reasonably well without running back to the delegator every fifteen minutes, or setting the building on fire for fear of asking for clarification when it’s warranted. I am also pretty mechanically inclined, took a lot of things apart and back together, including but not limited to bicycles I’ve subsequently taken above 40 mph (like cars, there are many kinds of defects that only show up at 2x “normal” speed, because forces tend to quadruple). Software people who know hardware of some sort are, at least in my experience, generally safer about trying to defy the laws of physics. But the danger with model testing is that I often sound like I know exactly what I’m talking about when I don’t (and sound too similar when I actually am the expert, so people either trust me too much or not enough). I’ve played with various levels of wiggle words and uncertain phrasing to try to fix this, always with mixed results. Sometimes even stating it as an educated guess, based on X and Y, causes other people to agree that sounds perfectly correct even if it’s not (one of the original definitions of a meme). Sometimes I avoid that trap of not believing my own model in my head, even if I don’t let on, sometimes I don’t. I should probably have more care about others aping my demeanor, but I tend to mentor anyone who is comfortable asking clarifying questions. It’s the ones that want to fake it til they make it that I can’t help. The danger is, as always, in believing your own PR. Questioning it constantly is paralyzing and exhausting, both for yourself and for observers (especially the exhausting part). Questioning it not at all is exquisitely dangerous.
- vondur 4y agoI don't think it's that negative. They clearly should have brought in people with relevant experience in the field before implementing the system. How much money and time did they waste fixing their system to account for Corn Cobs?
- xg15 4y ago> Why on earth would you assume you could move corn residues with air? From what the article describes later on, it appears the air pressure was actually generated by the tub grinder itself, not by any additional device. So the appeal of the original design might have been that no active conveyance solutions was needed at all: Because the grinder's air exhaust stream - which you get "for free" - already provides enough pressure to move the material up the pipe, as long as the material is light enough. That lets you greatly simplify the design, because now you can connect the grinder and the mill with a simple pipe and be done. For me it makes sense that they used the simplest possible solution that worked for their previous use cases. When trying to use their system with corn, they probably wanted to give their previous approach a try, before taking the time and effort of modifying the system. Edit: Got it wrong, both grinder and mill were creating the pressure. But the basic point is still correct I think. The choice was not air vs belt, it was "use the airflow that's there anyway" vs "build some active transport in addition to airflow".
- hinkley 4y agoFor every complex problem there is a solution that is clear, simple, and wrong.