Author Archive

Peter Vejrum Terp

My name is Peter Vejrum Terp, I am a travel geek, and tech hippie . I've been working as a professional Internet programmer, project manager and more since 2000. At the moment I work with SEO, and I've been doing it full time the last couple of years. I am cofounder of www.backpackerplanet.dk and www.backpackers-online.dk

Optimising webproject flows

Written by Peter Vejrum Terp on . Posted in Peters Blog

At the moment Im started optimising the flow on projects, programming and similar where I work. First you need to know that my job position is “Development specialist”, “Project manager” and daily technical manager for on a travel website.

Well back to where I started –  the case is that we need to improve the quality and the speed of how fast things is done. Therfore I tried to create a list of rules that each of us developers and project managers should follow to make the flow more effective.

When receiving a project / task – before startup 

  1. When receiving a project, walk through the tasks/subtasks of the project and determine if you understand every part of the project. If you don’t then ask the the project manager about the different parts until you fully understand.
  2. Retell about how you have understood the project.
  3. Always review The project when you get it, assess what 20% takes most of the project time and give information to your project manager. It is very likely that the 20% is less important than the value of the hours to make it work.
  4. Create a note or a short list of who(m) can assist you on the project if you have problems.

When recieving a project / task – in action

  1. Create a daily check list with small tasks, and with only 3 must do today tasks. The rest has to be a lower priority. Of course you will do more tasks thant that on a day, but you need to have a focus on the most important things, and the top 3 needs to be done. Each task must not exceed 2 hours – 1 hour is better than 2 hours.
  2. Create a test scheme on how to test the full project, and part of the project.
  3. When you are run into problems you can’t solve or just problems which takes a lot longer to fix than expected, then call for assitance – remember who can help you!

Remember

  1. Many requests on a page = slower page, therefore try to elminate the amount of requests. Meaning that JavaScript and stylesheet needs to be loaded from as few files as possible.
  2. Images which is too large = slower page, therefore insure that all images is in the right size. This is of course the graphic designers job, but it’s better to check – just to be sure. Recommendation is 80% compression for a jpg image.
  3. Spriting of images/icons – check if it’s possible to sprite images and icons in one file. This lower the amount of requests, and can also lower the amount of Kilobytes used for images.

Optimising the day – elimination

Written by Peter Vejrum Terp on . Posted in Peters Blog

In this short article I will like to share how I have optimised my work day and at the same time limited the stress of my workday.

It’s all about elimination, not about working harder!!!

Many leaders talk about working harder and running faster. I think that is a bad way to increase the through put on a workday.

Here is some minor changes I have made to optimise my day:

  1. Unsubscribe the newsletters that you deletes everyday. I removed 15-30 min. of my mail reading by doiug this.
  2. Stop reading mails constantly. Limit the mail reading to one or two times a day (Still working on that one)
  3. Limit the meetings! Short agenda and a very limited time (5-15 min) – no time to all the talk about nothing.
  4. Bulk tasks! Example: You create a status report every day with som numbers and statistics, it takes 30min. to create it. If I only do it once a week and do all the numbers for all days at the same time, I can finish all the work for a whole week in only 1 hour. Why? Because when you bulk a task, then you elimiate a lot of “grease” (it takes time to start a task, write a mail, end a task and so on).
  5. Understand the ideas of the project/task. It might very well be that the “customer” want something, but when you start looking at the project, you experience that a very small part of the project (typical 20%) will take 80% of the time. Remove those 20% if possible, in most cases those 20% doesn’t give back the effort.
  6. Create a short priority list, and do follow it. Only 3 “Must do tasks” a day! The rest has to be a lower priority!
Hmm actually I’m still working on all those! Some of them is easier to get into than others. For me 2 and 5 is the hardest!

Facebook developing notes

Written by Peter Vejrum Terp on . Posted in Peters Blog

Today I have just started learning a little more about Facebook development, I thought that I would share my notes from what I have learned. The notes is actually just some bullet, but they might be useful.

Facebook development today short summary

  • Rest API, FBML, FBJS should no longer be used, they are considered “Legacy”
  • Facebook Connect and Facebook Canvas App is nearly the same today, and the boundaries is bluring out.
  • Facebook Canvas loads App in an iFrame
  • OAuth 2.0 used to connect your App to a Facebook session for data access, like getting the required permissons to retrieve data.
  • Graph API is used for accessing data
  • Platform Dialogs used to prompt for user actions, such as sending requests.
  • Social Plugins allow external sites to integrate Facebook functions and to use social data
  • Numereous SDKs allow fair freedom of choice for App development.
  • Its important to know, that the only constant is change in the case of Facebook, therefore follow Facebook Developers Blog, and follow other sources for whats going on Facebook. A lot of changes happens all the time.

Usefull links

Facebook Graph API

  • HTTP(S) URL access to any objects in the Social Graph
  • All available data returned as JSON objects
  • Access to objects: Users, Pages, Events, Groups, Applications, Status messages, Photos, Photo albums, Profile pictures, Videos, Notes and Checkins
  • Use this interface to get a better inside view of whats available in the graph api https://developers.facebook.com/tools/explorer/
  • SDK For CFML can be found here https://github.com/affinitiz/facebook-cf-sdk/
  • Do not use the LIMIT in the paging functions, use SINCE and FOLLOWING instead. Limit can sometimes make some funny results.

Facebook Apps

  • Canvas Apps (Uses the full available width of the Facebook site)
  • Tab Apps (Runs on a Facebook Page Tab, therefore not as wide and often utilise “Like” gating.
  • Read more about how OAuth is implemented in Facebook herehttp://www.sociallipstick.com/?p=239
Great online course

A very simple stored procedure in MS SQL Server

Written by Peter Vejrum Terp on . Posted in Peters Blog

Lately I have been working with Stored Procedures, I must admit that it’s not a thing that I previously have had lot of experience in. I thought that it might be the case for other developers out there as well. First very and very short “A stored procedure is a subroutine available to applications that access a relational database system”. If you want to know more about the definition of a Stored Procedure then take a look at Wikipedias definition In this short post, I will try to show how to create a really simple stored procedure.

CREATE PROCEDURE sp_getUser(@userId int) AS
BEGIN
SELECT username, email, userid
FROM [user]
WHERE userid=@userId
END

This is our simple stored procedure, it retrieves user information (username,email,userid) from the table “user”, where the userid is set in the procedure head.

Let’s have a look on how to call the procedure

DECLARE @userId int;
SET @userId = 2;
EXECUTE sp_getUser @userId;

First declare a variable @userId as an int, next set the @userId=2 (we want to retrieve information for the user with id = 2. The next part calss the procedure, where sp_getUser is the procedure we just made, and @userId is the parameter we send to the procedure. The result will be a recordset with username, email and userid for the given user. I hope this very simple example can help getting started with STORED PROCEDURES in MS SQL Server.

How to work better

Written by Peter Vejrum Terp on . Posted in Peters Blog

1. Do one thing at a time
2. Know the problem
3. Learn to listen
4. Learn to ask questions
5. Distinguish sense froem nonsense
6. Accept change as inevitable
7. Admit mistakes
8. Say it simple
9. Be calm
10. Smile

I don’t know who wrote the original text, I just saw it at the office, but there is some truth in the text.

Posts from my blog