And that is a fine example of why you don't rely on such a Rube Goldberg machine for stuff like this...
A poor engineering decision killed the fish.
I see all sorts of crazy contraptions people have rigged up over the last 5 years since the appearance of the 'maker movement'. Surprised that fish are the only victim so far!
Sure you can wire up your coffee machine to listen for a tweet and have coffee ready for when you get in... then when you get there your flat is on fire...
Excuse the cynicism but as a professional engineer it scares me how dangerously and poorly thought out some of this sort of stuff is.
The number of professional engineers we have is vastly too small to make good use of the enormous power that computers have handed us in the last 20 years.
I see our options as: a) be condescending dicks every time a novice makes a novice mistake, b) leave enormous amounts of technical value untapped until professionals can get around to it, or c) use our professional engineering smarts to build tools that amateur engineers can succeed with. I favor C.
I pick a combination of (a) and (d). If someone does something dangerous and stupid we have to snap out of our predisposition to feel sorry for them. Ridicule is fine. As long as you then tell them how not to make the mistake again and why it was bad. When I blew up the fume cupboard at school due to a hydrogen gas explosion I didn't receive or deserve any sympathy but I apologised to those who were showered with glass :)
Option (d) which you missed is not to build them tools but teach them how the universe works and give them the knowledge of how to make their own tools.
Any fucker can stick an LED in arduino with a series resistor picked from a web form. However when someone gets the IV curve, the difference is remarkable.
A2) Point out mistakes to share the benefit of your experience.
The problem is that people have a real hard time distinguishing between A1 and A2, and this drives a lot of people to say that we shouldn't even try for A2, and just try to build stuff so people can learn from our experience without the troublesome burden of communicating with us.
Good point. I think A2 can be distinguished from A1 if the writer is willing to put in a little work. Some of the best lessons I learned were from people saying, "Oh, yeah, I made a mistake like that once. Here's how I think about it now. And let me tell you the story of an even bigger mistake I made."
But that sort of compassionate oral tradition only takes us so far. The number of people who will ever approach the level of a professional engineer is small. I think if we want to squeeze the full value out of digital technology, it's going to have to be approachable to the non-expert. Being compassionate in discussion can help there, but I think it's even more important to be compassionate in construction.
On one level I agree with you however I think that the barn door is open and the horses are heading for the treeline.
I trained as an industrial electrician before becoming a professional programmer (I programmed long before either) so I have an incredibly healthy respect for electricity and machinery.
That said I also think the benefits of putting hardware and software into the hands of talented new users is well worth the (potential) downsides, I broke many many things to learn how to not break things, that is how you progress in the early days.
It's not like his machine itself killed the fish, the rain did. The warning system he set is what failed. If he hadn't built it, the fish still would have died.
Comments
And that is a fine example of why you don't rely on such a Rube Goldberg machine for stuff like this...
A poor engineering decision killed the fish.
I see all sorts of crazy contraptions people have rigged up over the last 5 years since the appearance of the 'maker movement'. Surprised that fish are the only victim so far!
Sure you can wire up your coffee machine to listen for a tweet and have coffee ready for when you get in... then when you get there your flat is on fire...
Excuse the cynicism but as a professional engineer it scares me how dangerously and poorly thought out some of this sort of stuff is.
The number of professional engineers we have is vastly too small to make good use of the enormous power that computers have handed us in the last 20 years.
I see our options as: a) be condescending dicks every time a novice makes a novice mistake, b) leave enormous amounts of technical value untapped until professionals can get around to it, or c) use our professional engineering smarts to build tools that amateur engineers can succeed with. I favor C.
The LHC disagrees with you...
I pick a combination of (a) and (d). If someone does something dangerous and stupid we have to snap out of our predisposition to feel sorry for them. Ridicule is fine. As long as you then tell them how not to make the mistake again and why it was bad. When I blew up the fume cupboard at school due to a hydrogen gas explosion I didn't receive or deserve any sympathy but I apologised to those who were showered with glass :)
Option (d) which you missed is not to build them tools but teach them how the universe works and give them the knowledge of how to make their own tools.
Any fucker can stick an LED in arduino with a series resistor picked from a web form. However when someone gets the IV curve, the difference is remarkable.
There are really two versions of A:
A1) Be assholes.
A2) Point out mistakes to share the benefit of your experience.
The problem is that people have a real hard time distinguishing between A1 and A2, and this drives a lot of people to say that we shouldn't even try for A2, and just try to build stuff so people can learn from our experience without the troublesome burden of communicating with us.
Good point. I think A2 can be distinguished from A1 if the writer is willing to put in a little work. Some of the best lessons I learned were from people saying, "Oh, yeah, I made a mistake like that once. Here's how I think about it now. And let me tell you the story of an even bigger mistake I made."
But that sort of compassionate oral tradition only takes us so far. The number of people who will ever approach the level of a professional engineer is small. I think if we want to squeeze the full value out of digital technology, it's going to have to be approachable to the non-expert. Being compassionate in discussion can help there, but I think it's even more important to be compassionate in construction.
On one level I agree with you however I think that the barn door is open and the horses are heading for the treeline.
I trained as an industrial electrician before becoming a professional programmer (I programmed long before either) so I have an incredibly healthy respect for electricity and machinery.
That said I also think the benefits of putting hardware and software into the hands of talented new users is well worth the (potential) downsides, I broke many many things to learn how to not break things, that is how you progress in the early days.
> On one level I agree with you however I think that the barn door is open and the horses are heading for the treeline.
The horses are on fire.
Agree entirely though.
It's not like his machine itself killed the fish, the rain did. The warning system he set is what failed. If he hadn't built it, the fish still would have died.