Saturday, October 17, 2009

Approaching a programming task

I find getting started on any task is always the hardest part. I've always found it not too hard to complete an assignment once I got the ball rolling.

Although, hard assignments are still hard assignments. If someone asks you to program a Java to C Translator entirely in assembler, that's going to be difficult and/or time-consuming at the least. Still, once you start the project, you start making the project smaller and moving it to completion.

Procrastination is our adversary and yields little. The more we procrastinate, the longer we live with a burden over our head. The pressure of knowing we need to do something builds up while we procrastinate and deadlines grow closer. The second a task is completed, that pressure is relieved.

Also, if you don't start it, it never get's done. Lesson learned.

Friday, July 24, 2009

Design from a Developers View

Graphic design is a trick. I've found it's easier to look at images that resemble what I want and create them in photoshop (or gimp) than to assemble the images from scratch. I guess this comes with practice.

I've also learned a bit about structuring the site. Thinking about design as an experience rather than a picture is a bit more productive, I'm finding. As the user travels through the website, what do you want them to do? What would be a good action for the user to take and how can we make it quick, easy, and intuitive?

I tried a flowchart of sorts, earlier today. Basically, I grouped my users into two groups, then imagined what each group would need to get out of the site to have an enjoyable experience. This peice is important because if they aren't enjoying themselves, they'll leave before they start!

Once the user is doing what they'd like and beginning to find the site useful, we must prompt them to create an account; this should be effortless. Perhaps some javascript to display a signup form in the middle of the screen, gray out the rest of the page, register them via ajax, and return them to what they were doing would be least obtrusive. Once they're returned to their content and finish that experience, they should glide into the next experience all lined up to preform a new action.

Every step of the way they should be comfortable and feel welcomed. Every action a user takes that contributes to the site (submits a review, buys a product, invites a friend, etc...) should be quick, easy to find and accomplish, and immediately rewarded. Something friendly like a thankyou and a visual reward like a smily or a direction which they might find enjoyable to pursue.

How can we make anyone using our site happy while still having the purpose we attracted them to the site for fulfilled?

Thursday, July 23, 2009

Time Management: Homework vs Programming

There are so many amazing things I want to start working on:
  • IRC Chat Bot
  • My personal website
  • http://www.penspire.com landing page
  • and more!
I just feel so pressured between homework and work-related code. I'm trying the sleep-less code-more approach and it's not working (my body takes what it wants). Trying to find a balance.

The purpose of this blog

I'm going to be brief. I am starting this blog to track the evolution of my programming style and knowledge. Starting with my progress on http://www.penspire.com and growing with myself, this blog will reflect all my trials and techniques.

People are encouraged to comment and criticize.