Wednesday, July 01, 2009

Michael Jacksons death

You've probably heard that Michael Jackson died recently, but you haven't heard how. I hear two different stories:
1. His nose fell in his mouth and he choked on it
2. He bent down to pick up a small child and his head fell off

I'm wondering which one is true ...

Thursday, June 04, 2009

Trafikzoner


Många undrar vilken trafikzon de bor i när de ska kolla i försäkringstabeller

Sunday, May 03, 2009

Malmö-Sjöborakan


View Larger Map
Malmö (Statoil Derbyvägen)
>Mölleberga
>Klågerup
>Hyby
>Vissmarlöv
>Häckeberga
>Dörröd
>Stenberget
>Blentarp
>Sövde
>Sövdeborg
>Väg 984
>och slutligen vänster mot Sjöbo på väg 13
(här kan du gazza jävlar)

Friday, March 20, 2009

Helmet visor fog

So who drives a motorcycle and hasn't had problems with a foggy visor ? I thought I should sum up the best solutions here. It's all about reducing the surface tension of the minuscule waterdrops which the fog is made of. When this surface tension is reduced, the fogging effect is reduced.

1. Shaving cream: apply a thin layer of shaving cream to the inside of the visor. Be sure that you don't push it into the vents. Wipe clean with a dry cloth. It's actually possible to get a clean visor, without smudges. Use the inside of a sweats
hirt (soft). Works, but when standing still the damp builds up to an oil-like film in parts of the visor. The damp dries quickly when driving away. Not as bad as fog, but still. This is still a good solution for glasses, even though it creates a slight lens flare effect. Works in speeds from 30 km/h upwards.

2. Dish washing liquid: apply to inside of visor and let it dry. Wipe clean with dry cloth. Should be as effective as the shaving cream. Haven't tried it myself.

3. Pinlock: damp absorbing plastic that you need to screw on to your visor. Seems like a more permanent solution. You need to drill two holes in your 100€ visor which can scare some people. Check out the WebBikeWorld review for this piece of kit.

4. Fog City or ProGrip visor inserts. See the WebBikeWorld review. Some say that damp builds up like an oil film when breathing heavily (read: not perfect, might as well stick with shaving cream)

5. Respro Foggy Mask: Neoprene breath guard, comes recommended. Just bought a couple of these babies. I hope this saves me the trouble of using butter on my glasses.

6. There are a number of other sprays, impregnated cloths, etc, of which a small number work more or less. Try on your glasses before you buy ;)
Picture: Respro Foggy mask

Tuesday, February 24, 2009

Sunday, February 15, 2009

True Love


cannot be expressed in words .. Saeco12 , member of sporthoj.com shows you what true love is:

Thursday, February 12, 2009

Linux: Apache and SVN with mod_dav and mod_dav_svn

This shows Apache2 and SVN with basic authentication. Digest didn't work for me. If you have it working with Digest authentication, please comment on this post.

The following lines need to be enabled in /etc/httpd/conf/httpd.conf:

LoadModule dav_module modules/mod_dav.so
LoadModule dav_svn_module modules/mod_dav_svn.so


Then the following section needs to be created:

Now you need to create the /etc/svn-auth file and add users to it with:
htpasswd -c /etc/svn-auth

Restart Apache, and you should be able to browse your repository

Sunday, February 08, 2009

Install frame sliders Yamaha FZ6 S2


Installing frame sliders seems just a bit more tricky than assembling something from IKEA.
the bolts are steel, the frame is aluminium, you don't want to tighten it too hard. You might want to apply some locking agent so the engine doesn't fall off because the vibration loosened the bolts. I'm planning on taking some screenshots of the bike and manual, write down some figures for torque tightening, locking agent, and so on.

First of all, go get a torque wrench, and Loctite locking agent Loctite 242 Blue which specifically should resist vibration or Loctite 222 blue ( Loctite® 222 Low strength threadlocker for fasteners up to M36. Allows disassembly with normal tools. Approvals; P1 NSF Reg. No.: 123002 Thread size: up to M 36 Strength: low; Functional strength (average at 22°C): 6 hours breakloose torque determined in accordance with DIN 54454: 6 Nm)

... (Nagging wife, gotta go)
UNDER CONSTRUCTION

Friday, November 21, 2008

VMware tools Linux - Inapropriate build environment

So in Debian one needs to fiddle a bit with the system to be able to install VMware tools. Usually people get compilation errors saying that the compiler has the wrong version, and that for building the modules you need gcc-4.1.3 (error : Inapropriate build environment), and here's how you fix it:

/usr/bin/gcc is a link. Check out what it points at before you proceed:
$>ls -al /usr/bin/gcc
rename the link to something appropriate. Mine points at the latest gcc-4.3.2
%>mv /usr/bin/gcc /usr/bin/gcc.old
remove it, and recreate it:
$>rm /usr/bin/gcc ;
$>ln -s /usr/bin/gcc-4.1.3 /usr/bin/gcc

NOTE: change the gcc link back when you're done

rerun the configuration perl script /usr/bin/vmware-config-tools.pl, and everything should work (provided that you have downloaded the kernel header files, fixed that awful problem with the file that made everything break ... hmm, I can see that I didn't really prepare for writing a howto. However, I got things running with VMware Workstation 6.5.1, and VMware tools on kernel 2.6.26-1 so if you have any questions, I'd be happy to answer them

To get the guest OS to stretch and fit the window, run vmware-user script. A good idea would be to save your session after you run this script, or to run it as an init daemon.

Thursday, September 11, 2008

Tuesday, January 08, 2008

10 commendments of IT

Thou shalt not have any other programming languages/OS before Java/Linux
Thou shalt not make unto thee any golden image, since there is no such thing
Thou shalt not use the name of the root in vain
Remember the backup day, to keep it holy
Honour thy sysadmin and warez supplier
Thou shalt not kill -9
Thou shalt not commit cyber-adultry
Thou shalt not steal media online
Thou shalt not play with false negatives when tuning your spam filter
Thou shalt not covet every new CPU model and GFX card

Tuesday, October 09, 2007

Working


.. or more like defragmenting.. I would have killed for a 30 minute nap

Wednesday, March 21, 2007

any single software development model would be perfect

but they are not. IMHO each and every software development has issues. Of course there is no such thing as a "fits all" model, but it would be nice to set up some kind of general guideline for how a modern software project should be run.

For starters, most of us know that the Waterfall model (look it up on Wikipedia) is flawd by design, but it has one great thing: the focus on the requirements specification. Let me explain what i mean: let's say i'm a contractor, I'm trying to set up the definition of what i need do deliver before the project is considered as finished, so I can get paid. A good requirements specification would do exactly that. Working with iterations on requirements as with some agile models doesn't allow you to know exactly when you're done. Imagine the customer being pissed off because he considers that you didn't fulfill your contractual obligations, he/she probably will stop all payments until the issues are resolved.

What I'm suggesting is just as programming, use concepts from different models, and create something new, a bit more generic, but with extension capabilities.
For instance i would choose to have some solid requirement specifications, with the possibility of having sets of requirements specifications, such as "base functionality" and "extra goodies".

After that It would be nice to do some design - also a concept "less agile" according to some people. In a presentation of TDD I've heard the phrase "We're doing 'just-in-time design'". Good for them, but I like to have a structure to work with, even if the need for redesign appears in a later stage. "Just-in-time" design might be good for people with tons of experience, because they already know what the application structure should look like, and what the pitfalls are.

Speaking of test driven development .. A very nice concept, only where do you stop when designing your tests ? The combinations could be endless, how much time do you spend on it? should you be designing strict tests for business logic, and less strict test - or no tests - for the rest of the application ?

Productivity and reliability often have less priority than cost, but where do you draw the line ?

... to be continued after lunch
Scrum seems to be having a try at this general method approach, and specifies some really good aspects, such as the backlog, and the burn-down chart, but having 3 types of backlogs brings the classical time vs cost issue to my attention. How much time is needed to maintain these 3 backlogs ? wouldn't a classical requirements document and a simple backlog be enough ? (or better) There is nothing about testing mentioned in Scrum.

http://en.wikipedia.org/wiki/Feature_Driven_Development is another method that attempts to combine "a number of industry-recognized best practices into a cohesive whole" as cited from Wikipedia, but I think it's a bit loosely specified.

to be continued