|
If I were to pursue this project, I'd be looking for help from others to create it. Just wondering how many might want to help?
|
|
|
|
|
|
"Works on my machine."
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I guessing that they do not want to have all zones to come on at the same time, causing the water pressure to drop and therefor limit the volume of water that gets to any specific zone.
but, yes, devices like these, or light/socket timers, central heating systems, solar controllers etc. can be pretty bad...
|
|
|
|
|
|
Its all about the failure modes and savviness of the users. With the one-zone-at-a-time, any watering issues are clearly user error, whereas the other way, it looks like the timer is broken and needs to be returned.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
|
N_tro_P wrote: can imagine people reporting on said issues where as what "user" failure do you think is avoided as being reported if it allowed all zones to run?
The user failure, is that they didn't program the timer correctly. That's just as likely no matter which way the timer works. The difference is whether the user sees it as their failure, or a failure of the timer. One behavior skews the user's response to the system failure to suspect their own error rather than the timer being faulty, so naturally, that's the one the manufacturers of the timer went with.
This happens all the time -- the user's response to a perceived system failure is managed. Another example -- the oil pressure gauges in Ford vehicles. They're a gauge with a variable position needle, but they have two display states -- oil pressure OK, oil pressure is zero. Why? Because otherwise, users see a fluctuating needle and assume something's wrong. So, their response to a perceived failure is managed.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
Aside from the externals (water pressure/rainfall) factor(s), I wonder how much of this is due to the limitations of the early, mechanical, systems which has resulted in blinders on the designers.
|
|
|
|
|
|
Don't forget to document your results.[^]
I already made myself some enemies by saying what I found in the code (and the mental state of whoever did this). The only 'better' way would be to write it down in every detail. 
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
That sounds a lot like some of the code I've written after a big night.
Cheers,
Mick
------------------------------------------------
A programmer is a person who always checks both ways when crossing a one-way street.
|
|
|
|
|
Especially the 'kick vat and yell profanity' part.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
My bug-fixes don't work unless I sacrifice a few beers.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Anyone can do ordinary source,
it's the 'special sauce' that diffentiates programmers,
maybe their flavour isn't always one you like.
OPAW: one mans trash...
Sin tack
the any key okay
|
|
|
|
|
Oh light of wisdom, tell me all that again after you worked there for a few years.
Half a dozen triggers on every database table, each one hundreds, sometimes thousands of lines long. Each tiny change in the database can cause an avalanche of triggers going off. Good luck trying to predict any particular results when you have to fix a bug, which are numerous each and every day. What a treadmill!
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
missed the joke icon on the reply?
but seriously some bad programmers really do pour their heart into their efforts,
just gotta nudge (not bludgeon) them back onto the proper path.
rather than simply announcing bad practice - particularly with an audience, hint/show/sell them on the better way.
You've already admiteed your current approach is creating enemies, usually means it's not what you are saying, but how you are saying it.
Sin tack
the any key okay
|
|
|
|
|
No I did not miss the icon, nor was the reply meant to be all too serious, at least the first part.
If you knew me, you would know that I'm not one of those self proclaimed style or whatever cops. I can live with very much, even with GOTOs or global variables as long as they are used wisely. The only question I ask usually is, why someone thought this was needed. Give me a good answer and I might even adopt it.
This somewhat anarchic style works great if you happen to have people who know what they are doing. It does not work with a bunch of former VBA and Access guys who think they know it all and eagerly try to pull anybody elso to their dark side as well. That's also the reason why interviews now are over for me as soon as I hear VB (in any flavor) or Access.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
and so you demonstrate my point: it's not what you are saying, it's how you are saying it.
not saying that's bad, just realise that's all it is.
Sin tack
the any key okay
|
|
|
|
|
Sure, but saying it quickly answers the question wether or not it's a good idea to stay there.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Now enough of this gloomy stuff!
Here[^] is a good compromise for next weekend.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Triggers are like women: You can't live without 'em, but too many, and you wither up and die miserably.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I live very well without both.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Well, as long as you've got enough wine and loud, happy song, OK.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Something like that
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
