Visual and Code

"When you do things right, people won't be sure you've done anything at all"

Clone Windows 7 drive

leave a comment »

I’ve just changed my system drive to a faster, but smaller, SSD. This would normally not be a problem using Clonezilla or similar, but the fact that the new disk was smaller than the original made the whole thing a bit trickier. What I finally did, and what seems to work.

A) Re-size the partition to clone.

  1. Download and install EASEUS Partition Master 8.0.1 Home Edition, which is free (as in beer).
  2. Change the size of my C: (win sys) disk, so that it could fit on the new one.
  3. Don’t forget to File -> Apply the changes made in 2.
B) Clone the partition
  1. Download and install EASEUS Todo Backup Free 2.5.1. For some reason I found this tool better for doing cloning than Partition Master.
  2. I copied the C: partition to the empty space on the new disk, using sector by sector copy.
C) Make disk bootable
  1. (Don’t know if needed) made sure the new drive was bootable using bcdboot  (Very easy)
D) Switch drive letters
  1. Open regedit onto HKEY_LOCAL_MACHINE/SYSTEM/MountedDevices
  2. Changed \Dos\devices\C: to a temp letter, say X:
  3. Changed the new disk to have C:
  4. Changed X: back to something nice, like M:
E) Change boot order in BIOs

 

What happened now was that Windows booted up using the new disk, but, still using the old disk as system disk. To change this, the boot entry that I copied from the old disk must be edited. Looking at the boot entries using bcdedit, it said the system now booted from M:, although BIOs booted from “C:”

 

F) Change boot entry
  1. Changed the partition in the boot entry to point to the new disk (Not as hard as it may look). Using BCDEdit. Google for a better tutorial.
  2. Something in the lines of
    bcdedit /set {current} device partiton=C:
    bcdedit /set {current} device ospartiton=C:
Restart, and it worked!

Written by pethol

2011 July 14 at 10:04 am

Posted in Uncategorized

When adpoting, do it often

leave a comment »

A web page or a computer program can be seen as a complex adaptive system. Such systems have large boundaries, large edges or surfaces, with many contact points to the surrounding world. Through these points of contact the system interacts with the world. It gets input and it outputs output.

When changing a web page significantly, the number of visitors may drop, or visitors have trouble navigating. Or when an application is changed, users have to learn new, or maybe their old settings isn’t valid any longer. If it’s a library the users may have to change their code and re-compile.

When the system being the web page or program changes — the surrounding world (also systems) will have to change, adjust, to the new surface and interactions. Sometimes changes become large and cumbersome, for instance in the case of changing API’s in a well used code library. In these cases people tend to make these changes seldom and well thought through, and carefully weighting the value of changing against the cost of adapting. The effect being that more small changes will pile up in a big one, which will make the decision to go ahead harder… You get the point.

Instead of trying to do big changes seldom, one must do small changes often. Make the cost of migration small. Make the cognitive load smaller for the visitors of the changed page. The complex adaptive system should adapt, not be revolutionized. It’s the effect of the changes that are important.

The intuitive reaction to changes that require adoption is to do them seldom. Where we’re heading, where agile is pointing us, is to do it the other way around.

Written by pethol

2011 April 13 at 3:24 pm

Posted in Development

Creativity

leave a comment »

Just home from a workshop with Realize. Great fun, and really inspirational. These guys (and girls?) knows their stuff. They prove that one really can be methodical about being creative and having ideas.

This is not correlated with my previous write-up. But, as always, stuff seems to come in clusters.

Written by pethol

2011 March 7 at 8:22 pm

Posted in Creativity

Idea generation methods

with one comment

Here’s a little write-up that I did for some friends regarind design/idea/creativity methods. WARNING — it’s pasted from and OpenOffice document into the editor, so layout etc is probably off by a mile or two.

Creativity methods

Idea generation methods and other creativity methods are invented to support the generation and developing of ideas; either for coming up with totally novel things, or for exploring and expanding on already existing.

Creativity methods are almost like any other method. Like other methods they need to be defined in terms of input and expected output, how they are performed and what they are suitable for.

Example

For example lets take the well know Six Thinking Hats. This method is used for investigating a specific idea and can be suitable when the members of the group is locked in a mode of thinking; ‘Positive Jen is having a hard time being full out rational about her pet idea’. The method is performed by using six hats that the participants put one, one at a time. The different hats symbolizes different modes of thinking, and a participant wearing one hat may only comment using that mode. For example the Red hat symbolizes Intuition and gut feeling, and the Blue hat symbolized rational, logical thinking. One participant using the Red hat might say “Wearing the Red hat, I feel the idea is heavy because …”. After a minute or two the participants changes hats, and typical a session last all from 5 to 15min plus setup and explanation. The method works by forcing people to use a way of looking at the idea, and by allowing for other opinions and judgments than the person would normally do or feel comfortable doing in that group. What we expect to get from this method is a set of new perspectives and insights about the idea, and perhaps some new ones. Probably – but not necessarily – quite close to the original one.

For this method we can define the necessary parameters.

Time 5-15min

Input An idea to scrutinize.

Expected output A set of insight, possibly new ideas.

When One idea that needs exploring, and need new perspectives.

How to Each person, in turn, puts on a hat and makes statements using the thinking mode of the hat …

Hats Red …, Blue …, …

Rational …

Setup

Before a group starts a method, it decides for how long it should go on. It is important to remember that taking longer time for each step in a method does not make the result better. Instead of putting more effort into thinking and deliberating, one should put effort into doing the method thoroughly; doing what is prescribed in a true manner. Some methods also need a certain tempo or sense of urgency to work well. Normally one will not produce more or more useful output from the method only because it’s done for a longer time. Therefore, to keep the method efficient, only do it under the predetermined fixed time. A moderator is good for this.

Naturally, it is also good to before hand decide how the result should be documented. By post-it’s, by each one taking notes, by a secretary or some other way.

Something about Ideas

New spun ideas are fragile things. They get trampled down by even the slightest negative words. When dealing with fresh ideas, during the diverging phase, one must only be positive about them.

The first shape of the idea is typically not what is later realized. It’s the idea that one laughs at when heard, that someone else makes great success with a year later. That is also one reason why an idea must not be cut down prematurely. Since the idea at first is somewhat plastic, it can be developed in different directions.

Ideas are about having two thoughts at the same time, and the incentive to take care of it. That is why it is so fruitful to a creative process to add new influences, experiences, artifacts, etc. To spur, evoke, and provoke. Adding stuff to the process, seemingly irrelevant, but novel to ones current chain of thoughts non the less.

The creative process

To be able to use idea generation and other creative methods, one must have an understanding of the process involved when going from problem to final idea.

One first start somewhere whit a seed. This can be a problem, a wished-for situation (less useful), an initial idea, an initial product or something similar. From this seed is many new ideas are then created. This is called diverging. At this time it is crucial not to be negative towards any idea – yours as well as someone else – but to use positive thinking about most and all.

When one have many enough ideas, or the time has run out, it is time to see if these ideas can be further developed and cross pollinated. This stage is called transformation, during which the goal is not to create totally new ideas, but to improve existing ones. This allows for some exploration of the ideas before the slashing and burning during the last phase. When an idea is first born, during time limited methods, it can be quite unfinished and needs more love before it is discarded or hailed.

When time for that is up, or no new things emerge, it is time decide for one or a few ones to implement or test. This is of course called convergence. It is only in this last phase one really allows oneself to be critical and negative to an idea.

Some Methods

6-3-5

Time 20-30min

Input A problem description.

Expected output At least 6×3 new ideas.

When To spawn many new ideas. To write ideas already in the mental loop.

How to 6 comes from six persons participating, each writing down 3 ideas. For doing this, they have 5 minutes. 6-3-5. After that, each persons ideas are sent to the next person, who extends and improves – or write a new one – for each of the ideas. Each paper will be sent around 5 times.

Rational Although this method may not be as spontaneous and lively as other methods, it attempts to force each participant to expand every other idea – no slacking. And sometimes a little solitude and sovereignty is needed.

Reference Missing :-(

Search for Visual Inconsistencies and Error Analysis

Time 10-20min

Input A product.

Expected Output Domain understanding and problems onto which to innovate.

When When there already is a product for the problem, or a similar problem.

How to Try the product. Try to find the mistakes made, what is bad and what is missing. Look for errors both in the external and internal. That is, both in the visual appearance and in the models and concepts.

Rational What is hard to get right, might be what you can deliver in a better way. Maybe that part of the product, made in a better way, can be a product in itself.

Reference Design Methods, Jones, J.C.

Extreme Characters (with personal twist)

Time 15-30min

Input A product or problem.

Expected Output Three distinct and unique product ideas or concepts (one for each extreme character).

When Either there is a need for a product; “we need a navigation app for a tablet”, or there is a platform or product in place, such as mobile phone or mp3 player.

How to Each participant writes down three “extreme characters”. To ease the process, these should be well know the rest of the participants, such as movie stars or figures from comics or alike. Then the groups selects three of these to work with.

For each of the characters, list what makes up their character, what defines them, and what their goals are (Don’t spend to mush time here though).

Now take the product/problem and specify what a product would look like, if made only for that character. E.g. In a navigation app for Homer Simpsons, all the donuts and beer places between home and the nuclear plant, are pre-marked on the map, and has an extremely simple user interface. Hopefully there is at least one takeaway from each character which is the new ideas.

Rational A solution made to fit everyone, is not a very good for anyone specific. By limiting the scope of the design, it can easier be made to fit the target group.

Reference http://studiolab.io.tudelft.nl/vormtheorie1/gems/00DjajDISInte.pdf

Five Whys

Time 10-15min

Input Some ideas or problems.

Expected Output Reasons to why the ideas are as they are, or what the root cause of the problem is.

When This can be used either to find the root cause of a problem, or to learn more about an idea. Can be used to find why the idea was invented and what the core of the poodle is.

How to Ask someone in the group why something is, repeat 4 times more.

Rational .

Reference .

If anybody got an iPhone: http://itunes.apple.com/us/app/ideo-method-cards/id340233007?mt=8

Written by pethol

2011 March 2 at 9:26 pm

Posted in Uncategorized

Hacked “micro-IDE” for image functions in C#/.NET

leave a comment »

Screenshot of prototype micro-IDE for image functions.

Written by pethol

2009 December 12 at 9:36 pm

Posted in Uncategorized

Tagged with , , ,

Windows Problem Reporting window

leave a comment »

This unsizeable window suddenly showed up. I don’t have good feeling about this.

Windows Problem Reporting screendump.

Written by pethol

2009 January 12 at 7:18 pm

Posted in Uncategorized

Tagged with

World Usability Day

leave a comment »

“Today is World Usability Day

In Usability

Welcome message by Bill Gates – “It’s about making our world work better. It’s about ‘Making Life Easy’ and user friendly. Technology today is too hard to use. A cell phone should be as easy to access as a doorknob. In order to humanize a world that uses technology as an infrastructure for education, healthcare, transportation, government, communication, entertainment, work and other areas, we must develop these technologies in a wa

Yeah, and a doorknob could be as easy as a door handle.. geez, these Yankees..

Written by pethol

2008 November 14 at 12:08 pm

Posted in Uncategorized

OODA Loop

leave a comment »

I talked (ok, IM:ed) with Anders last friday, just before I got on vacation, and for some reason we started talking about PAD (Pen and Paper Aided Design). I googled the phrase, and to my dispare, I got my own post as the top hit. Ok, hoped the idea was a little more spread.

Anyhow we also got talking about product development and complexity, and I sphew out a lot of stuff. But I realized that everbody should read about the OODA Loop by John boyd. I saw “Generation Kill” s01ep02 today and I thought I heard the “Godfather” say something like ” .. and I can quote Boyd ..”. You wish! :-) I wonder how many of the marines that understand Boyd. But anyhow, it’s good stuff for most of us.

Also, do listen to Uffie! Thats not a recommendation, it’s a must! Of course, it’s her on the Justice album on the song “Tthee pparty” or whatever it’s called.

Wood print Japan stff

Written by pethol

2008 July 22 at 10:05 pm

Posted in Uncategorized

To much to fast to tired

leave a comment »

Little to much, to fast, to tired.

Little to much, to fast, to tired.

I created a new project – and namepace – today. I moved some files from another namespace into the new project, and changed their namespace. Apparently it was a little to much, a little to fast, and possibly I was a little to tired :-)

Written by pethol

2008 July 11 at 4:33 pm

Posted in Development

Book (manga!) recommendation

with one comment

Me and Samme kinda started like this sort of book club. And in this book club, we don’t read the same book at the same time. We kind of just share them. So we finally got aroud (me) and bought a couple of books. Naturally we bought one book from the recommendation list of Jeff Atwood (www.codinghorror.com), namly .. og wait, it’s not on the reading list, but mentioned in one of his posts.. “Facts and Fallacies of Software Engineering” by Robert L. Glass. I’ve only started very mildly on it, but it seams really great, and will help me settle some arguments with non CS people.

Down hill view

The other one I saw on a post on Presentation Zen, anpther great blog. This one is called “The Adventures of Johnny Bunko. A fast read peace of ok drawn manga, but a great little book! REally liked it, and so did Samme. The 6 tips that johnny recieves in the book about ‘careering’ is not the american business type of tips, but rather genereal and abstract. I have this idea, that I’m going to pick each one of those, and in a zen-quizy way make a post about software development based for each one. Let’s see how that turns out in the next post, and the tip “There is no plan”. Facinating, is it not?! ;)

Johnny Bunko can be bought for us in Sweden from Bokus, and thats were I got ours from. The price is in pair with amazon or whatever.

Written by pethol

2008 June 17 at 10:12 pm

Posted in Development, Friends, Stuff

Follow

Get every new post delivered to your Inbox.