Skip to content

Instantly share code, notes, and snippets.

View vishnudas-raveendran's full-sized avatar

vishnudas vishnudas-raveendran

View GitHub Profile
@vishnudas-raveendran
vishnudas-raveendran / AudioAlertForLongColabProcesses.py
Last active March 20, 2022 06:29
For long running processes in Google colab, I will find it useful if there is some audio alert indicating end of processing. This processing often runs into hours. So I move-on to other errands, while doing those I don't want to be distracted checking in once in a while if the processing is completed. You can also use some chime like alerts here…
#For long running processes in Google colab, I will find it useful if there is some audio alert indicating end of processing.
#This processing often runs into hours. So I move-on to other errands.
#while doing those I don't want to be distracted checking in once in a while if the processing is completed.Hence the alert.
#You can also use some chime like alerts here, but with all the devices in the house including my laptop
#chiming all the time because of notifications. I would prefer this to be very specific, hence the voice prompt.
from gtts import gTTS
from IPython.display import Audio
import time
@vishnudas-raveendran
vishnudas-raveendran / clean_code.md
Created June 9, 2021 17:41 — forked from wojteklu/clean_code.md
Summary of 'Clean code' by Robert C. Martin

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.


General rules

  1. Follow standard conventions.
  2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
  3. Boy scout rule. Leave the campground cleaner than you found it.
  4. Always find root cause. Always look for the root cause of a problem.

Design rules