dideler

Avoid over-commitment

It takes a few minutes to entangle yourself in commitments that can take years to unwind.

Learn when and how to say "no."

If you're over-committed, say, "I'd really like to take on that task/role, but I'm concerned that with my current commitments, I might not be able to perform the task to the high standards to which I hold myself."

Before you say "yes" to anything, sleep on it.

dideler

#!/usr/bin/env python

import sys

filename = sys.argv[1]

# These do not remove \n
with open(filename) as f:
    s = ''.join(f.readlines())
    

dideler

The program below can take one or more plain text files as input. It works with python2 and python3.

Let's say we have two files that may contain email addresses:

1. file_a.txt

foo bar
ok ideler.dennis@gmail.com sup
 hey...user+123@example.com,wyd
hello world!

dideler

# Based on http://ejohn.org/blog/keeping-passwords-in-source-control/
# 
# John Resig needed a way to keep sensitive data (e.g. config files with
# passwords) out of source control. So he decided to encrypt the sensitive data.
#
# I decided to modify the script so it's purpose is quickly encrypting or
# decrypting any sensitive file you have on your computer.
#
# Usage: make encrypt
#        make decrypt

dideler

Snippets of code that I've played around with, which could be useful to others.
Nothing impressive, but you may learn a thing or two.

dideler

class A 
{
 public:
  int x;
 protected:
  int y;
 private:
  int z;
};

dideler

Note: I'm currently taking a break from this course to focus on my studies so I can finally graduate

Table of Contents

1. Overview
2. Introduction
3. Interactive Start
4. Linux and Server-Side Javascript
5. Linux Command Line
6. Linux Development Environment

dideler

--title The Friendly Interactive Shell (fish)
--author Dennis Ideler | @dideler | ideler.dennis@gmail.com
--date Prepared for Software Niagara's DevTricks | June 25, 2013
--footer dennisideler.com
--## 'today' is a date option, but kinda useless.
--## heading and title seem to do the same thing.
--horline
--##withborder
--fgcolor black
--bgcolor white

dideler

Based on the article: Using checklists for code review

In general, people are pretty good at the code review process, but it's sometimes surprising what can slip through. A natural consequence of the way our brains look at the world is that it's easy to pay a lot of attention to small details and code style flubs, and completely miss the big picture.

Obviously, not everything is applicable for every change. If the review request isn't making any changes to UI, then skip the first two checklists entirely. If a change is a bug fix, typically don't review it for architecture and design principles.

Put the big stuff first (e.g. architecture). You don't want to work through a ton of small issues before realizing that everything has to be rewritten.

Do a pass through the code for each and every item in the checklist. By only looking for a very specific type of defect, each pass goes relatively quickly, even for large changes. Focu

dideler

A formula that lays out, on a page-by-page basis, exactly what should happen when, in a screenplay.
Each page is roughly equivalent to a minute of screen time.
Page counts don’t need to be followed strictly, but it’s important to get the proportions fairly close.

Opening image (p. 1)

Sets the tone for the story and suggests the protagonist’s primary problem.

Theme is stated (p. 5)

A question or statement, usually made to the protagonist, indicating the story’s main thematic idea.