It may be possible, but perhaps not, to just lower the pump output so that it takes 30 minutes to water the plant. That might be too little output to work though, because that is 2 orders of magnitude longer.
Well, you could use 2 timers with the same period, if they are accurate.
You would plug in timer 1, so that its output (output 1) is on. You would set timer 2 so that output 2 would turn on as soon as timer 2 receives power. When there are only 30 seconds left in timer 1's on cycle, you would plug timer 2 into a separate outlet.
Since they are synced, but only overlap by 30 seconds, they will only both be on for 30 seconds. You would then need some kind of AND that would only turn on the pump if output 2 and output 1 are both on.
That's the same reasoning for text passwords, yet there are huge password dumps every year.
It only takes one place where security standards aren't implemented properly to have your print leaked forever.
Never mind a malicious user managing to alter the code to leak the print before it's hashed.
Or even someone physically accosting you and retrieving a brain scan. They could do the same thing and force you to give up a password, but at least the password you can change later on.
As with any medication, side effects vary. When I took melatonin, I would very quickly fall asleep but would still wake up extremely tired. I also experienced very severe depression when on melatonin, that started about 2 days after use, and ended about a day after stopping use.
I do know people that have had it work very well for them, however.
1. If you right click on an object in the console, you can store it as a global variable. This makes an exact copy of the object that is in the global scope.
2. They used $_ which is a shortcut to get the result of the last command. So in the example, temp9 was the last command, so $_ is a copy of temp9
3. The important bit is the copy(var) call. This will copy any var into your clipboard!
You wrote that? I love that site! I actually saw it for the first time last week when a company I was interviewing with used it as part of the interview process.
I loved how smooth and fluid it made the whole process, that they could switch between languages during the interview and the rewind functionality.
I believe that the author meant to write 0.25 seconds, instead of 0.5 seconds. She says that the one step halves the running time, and later on she is investigating how the 0.25 seconds are split up.
A >50% speedup is not to be sniffed at! I completely agree with your point though, unless it is mission critical that this code runs as fast as possible, then you are better off keeping it simple!