I just had a thought. I'm sure it's one of those things everybody but me has been doing for years:
At the end of the day, leave an info/warning/error in the test code explaining what the next step should be.
That way, instead of staring numbly at the screen for fifteen minutes in the morning, while you wait for the coffee to kick in, you can just run the latest test and follow your own orders!
Merry Christmas, Happy Hanukkah, or whatever festival you choose to celebrate this winter season.
-Neil
skip to main |
skip to sidebar
Followers
About Me
- TechNeilogy
- Post graduate degree in climatology with work in artificial intelligence, but entire professional life spent in software engineering. Have done soup-to-nuts: embedded systems programming to expert system design and implementation, assembly language to DSLs to functional programming, device drivers to user interface design. Once had to re-learn to communicate with humans after spending 15 straight months programming a VxD in 80x86 assembly language.
License and Copyright
Unless specified otherwise, all source code in this blog is Copyright (c) Neil P. Carrier as of the posting date, and is licensed under the MIT License, "AS-IS" and without warranty of any kind.
Blogroll
For a list of the blogs that I follow, please see my profile page.
General Programming
Languages
Source Control
Logging
Way Cool Tools
Code Hosting
Web Stuff
Solar System
AI, NLP & ML
Graphics
DBMS
Rabbits
"If you only knew the things I have seen in the darkness of night..." -M.C. Escher
