What's next after Testing on the Toilet?
If you have visited a Google engineering building, you may notice that the
bathrooms are equipped with software engineering tips located above
the urinals and in the bathroom stalls. These were cleverly named
Testing on the toilet. It provides a way for
software engineers to learn something during this important time of
the day.
A recent extension to this program has been called Learning on
the loo. As a logical extension of these, you can easily imagine
quite an extensive set of software engineering lessons:
- Release Engineering in the Restroom
- Code reviews on the crapper
- Batch Processing on the Bidet
- LDAP in the lavatory
- Profiling in the powder room
- Joins on the john
- Compression and unzip by the urinal
- Widgets in the water closet
- Software in the sewer
- Threads on the throne
- Paging on the pooper
- Shell programming on the shitter
- Unittests on the urinal
- #!/bin/bash in the bathroom
- Lifecycle management in latrine
- Optimizing in the outhouse
- Objects in the outhouse
- Work queues in the washroom
- Reliability in the restroom
- Copy protection in the chamber pot
- Components on the commode
- Outer joins in the outhouse
- Privileges in the privy
It's somehow appropriate that my blog is named
sigcrap.