March 16, 2016 at 12:16 pm
g.powers (3/16/2016)
I was rather impressed with this automation (assuming it's true).A programmer wrote scripts to secretly automate a lot of his job — and email his wife and make a latte
http://www.techinsider.io/programmer-automates-his-job-2015-11
🙂
I can't think of any way any of those things could possibly go wrong :unsure:
March 16, 2016 at 12:25 pm
ZZartin (3/16/2016)
g.powers (3/16/2016)
I was rather impressed with this automation (assuming it's true).A programmer wrote scripts to secretly automate a lot of his job — and email his wife and make a latte
http://www.techinsider.io/programmer-automates-his-job-2015-11
🙂
I can't think of any way any of those things could possibly go wrong :unsure:
Interestingly, the article doesn't mention if his wife is in prison for homicide. 😉
March 16, 2016 at 1:28 pm
One of the other things I've found is that sometimes when I find a way to automate one process, I am able to adapt that solution to other problems when they come up. So not only is time saved on the original process, but also on some future processes. 😉
March 16, 2016 at 8:50 pm
The drawing in the article is what I've seen a whole lot of automated testing do. People don't know how to write the testing any more than how to write the original code. And, sometimes the code changes a lot whereas the testing isn't usually designed to withstand changes because they're in a hurry to write it so the can start testing the code that was held up by writing the testing to automate the next go round which can't because there were too many changes and.... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 17, 2016 at 3:36 am
Jeff Moden (3/16/2016)
The drawing in the article is what I've seen a whole lot of automated testing do. People don't know how to write the testing any more than how to write the original code. And, sometimes the code changes a lot whereas the testing isn't usually designed to withstand changes because they're in a hurry to write it so the can start testing the code that was held up by writing the testing to automate the next go round which can't because there were too many changes and.... 😉
If you can't write code then you can't write tests.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
March 17, 2016 at 10:52 am
Gary Varga (3/17/2016)
Jeff Moden (3/16/2016)
The drawing in the article is what I've seen a whole lot of automated testing do. People don't know how to write the testing any more than how to write the original code. And, sometimes the code changes a lot whereas the testing isn't usually designed to withstand changes because they're in a hurry to write it so the can start testing the code that was held up by writing the testing to automate the next go round which can't because there were too many changes and.... 😉If you can't write code then you can't write tests.
Perhaps also, if you can't update the tests, you shouldn't write code.
March 17, 2016 at 11:09 am
Steve Jones - SSC Editor (3/17/2016)
Gary Varga (3/17/2016)
Jeff Moden (3/16/2016)
The drawing in the article is what I've seen a whole lot of automated testing do. People don't know how to write the testing any more than how to write the original code. And, sometimes the code changes a lot whereas the testing isn't usually designed to withstand changes because they're in a hurry to write it so the can start testing the code that was held up by writing the testing to automate the next go round which can't because there were too many changes and.... 😉If you can't write code then you can't write tests.
Perhaps also, if you can't update the tests, you shouldn't write code.
Not sure what you mean Steve.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
March 17, 2016 at 11:14 am
Gary Varga (3/17/2016)
Steve Jones - SSC Editor (3/17/2016)
Gary Varga (3/17/2016)
Jeff Moden (3/16/2016)
The drawing in the article is what I've seen a whole lot of automated testing do. People don't know how to write the testing any more than how to write the original code. And, sometimes the code changes a lot whereas the testing isn't usually designed to withstand changes because they're in a hurry to write it so the can start testing the code that was held up by writing the testing to automate the next go round which can't because there were too many changes and.... 😉If you can't write code then you can't write tests.
Perhaps also, if you can't update the tests, you shouldn't write code.
Not sure what you mean Steve.
I interpret his statement to mean that testing is a part of writing code. Ergo, if you can't test your code, you have no business writing it in the first place.
March 17, 2016 at 11:17 am
Ed Wagner (3/17/2016)
Gary Varga (3/17/2016)
Steve Jones - SSC Editor (3/17/2016)
Gary Varga (3/17/2016)
Jeff Moden (3/16/2016)
The drawing in the article is what I've seen a whole lot of automated testing do. People don't know how to write the testing any more than how to write the original code. And, sometimes the code changes a lot whereas the testing isn't usually designed to withstand changes because they're in a hurry to write it so the can start testing the code that was held up by writing the testing to automate the next go round which can't because there were too many changes and.... 😉If you can't write code then you can't write tests.
Perhaps also, if you can't update the tests, you shouldn't write code.
Not sure what you mean Steve.
I interpret his statement to mean that testing is a part of writing code. Ergo, if you can't test your code, you have no business writing it in the first place.
In which case I agree. (Especially as that was my point. ;-))
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
March 17, 2016 at 11:28 am
Ed Wagner (3/17/2016)
Gary Varga (3/17/2016)
Steve Jones - SSC Editor (3/17/2016)
Gary Varga (3/17/2016)
Jeff Moden (3/16/2016)
The drawing in the article is what I've seen a whole lot of automated testing do. People don't know how to write the testing any more than how to write the original code. And, sometimes the code changes a lot whereas the testing isn't usually designed to withstand changes because they're in a hurry to write it so the can start testing the code that was held up by writing the testing to automate the next go round which can't because there were too many changes and.... 😉If you can't write code then you can't write tests.
Perhaps also, if you can't update the tests, you shouldn't write code.
Not sure what you mean Steve.
I interpret his statement to mean that testing is a part of writing code. Ergo, if you can't test your code, you have no business writing it in the first place.
I'm always surprised by how many developers I've come across who will pass off code without even trying to run it themselves, even if it gets caught in QA that's just bad form.
March 17, 2016 at 11:33 am
hence my statement. I was agreeing with Gary. Just wanted to clairfy.
March 18, 2016 at 8:25 am
ZZartin (3/17/2016)
Ed Wagner (3/17/2016)
Gary Varga (3/17/2016)
Steve Jones - SSC Editor (3/17/2016)
Gary Varga (3/17/2016)
Jeff Moden (3/16/2016)
The drawing in the article is what I've seen a whole lot of automated testing do. People don't know how to write the testing any more than how to write the original code. And, sometimes the code changes a lot whereas the testing isn't usually designed to withstand changes because they're in a hurry to write it so the can start testing the code that was held up by writing the testing to automate the next go round which can't because there were too many changes and.... 😉If you can't write code then you can't write tests.
Perhaps also, if you can't update the tests, you shouldn't write code.
Not sure what you mean Steve.
I interpret his statement to mean that testing is a part of writing code. Ergo, if you can't test your code, you have no business writing it in the first place.
I'm always surprised by how many developers I've come across who will pass off code without even trying to run it themselves, even if it gets caught in QA that's just bad form.
They are not developers. They are just employed as developers. :crying:
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
March 18, 2016 at 9:42 am
Oh the joy of a receiving a notification that an issue has been closed only to find that it was tested in a parallel universe where bugs don't exist, users are grateful, unicorns have feathers and stuff works in production but not development.
Viewing 13 posts - 16 through 27 (of 27 total)
You must be logged in to reply to this topic. Login to reply