Monthly Archive for April, 2011

I’m just a stupid developer, don’t confuse me… part 3 of 3

I’ve been posting about a few principles that have helped me minimize the pain of understanding complexity in my own code. See part 1 of this series where I briefly discussed leaving yourself and others notes about the “why” of your design decisions. And see part 2 for discussions about simplifying your code.

Continuing with the movement towards simplicity; whenever possible make functions and scripts single use and encapsulated. We can think about breaking functions (or scripts) down into their smallest useable parts as simplification, or we can talk about it as encapsulation. We broke down a confusing custom function into separate parts in order to improve readability. What we also gained was some compartmentalization and modularity. It’s difficult to separate the two principles of simplicity and encapsulation.

Continue reading ‘I’m just a stupid developer, don’t confuse me… part 3 of 3′

 

I’m just a stupid developer, don’t confuse me… part 2 of 3

See part 1 of this series where I briefly discussed leaving yourself and others clues about the “why” of your design decisions.

The second principle I want to talk about helps with the “how” and “what”.

It can scarcely be denied that the supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience.
- Albert Einstein

Or how it’s more often paraphrased:

Make things as simple as possible, but not simpler.

Take the time to make things simpler. This is much more about the “how” and “what” of programming.

Continue reading ‘I’m just a stupid developer, don’t confuse me… part 2 of 3′

 

I’m just a stupid developer, don’t confuse me… part 1 of 3

Our human brain has the amazing capacity to remember and understand the things we do. What’s more amazing is our brain’s capacity to overestimate how much it has the ability remember and understand the things we do. My average shelf life for remembering how my code works is about two months. That is to say if I don’t touch a part of an application for up to two months, I can jump in and get back to work, no problem. After that I have to study it a bit and get my bearings again. The longer I go the worse it gets. Your mileage may vary, but no one can escape this problem.

There are a few things that have helped me minimize the pain described above, which I’ll be posting about over the next couple of days.

Continue reading ‘I’m just a stupid developer, don’t confuse me… part 1 of 3′

 

FileMaker Go now supports Charts, Printing and Signatures!

FileMaker Go for iPad/iPhone Updated

What’s New in Version 1.2.1
- Adds support for FileMaker Charts (compatible with FileMaker Pro 11).
- Records and saves signatures to the database file.
- Adds support for printing.
- Improves rendering, display, and printing of PDFs.
- Sends notification to user when there is a record lock conflict.
- Adds ability to open hidden files.
- Resolves compatibility issues when running on iPad.

Update:
Check out the “FileMaker Go 1.2 In Two Minutes”

 

Please Join us April 26th: John Sindelar and Jesse Barnum

Greetings FileMaker Enthusiasts,

Our next Philadelphia FileMaker Developer Group meeting has been scheduled for Tuesday evening, April 26th 2011 at 6:00 PM. The meeting will be held at the IT Solutions Fort Washington Office.

414 Commerce Dr., Suite 150, Fort Washington, PA 19034
Google Map: http://tinyurl.com/37mhhh

Please RSVP here if you are planning to attend this meeting:
http://www.fmpug.com/rsvp.php?eventID=1176 Continue reading ‘Please Join us April 26th: John Sindelar and Jesse Barnum’