Dell laptops in 8 colours

Nooooo they look so pretty.

I need to get another Dell Inspiron soon.

Last year I bought a DELL inspiron laptop, I had some initial problem with its LCD, but once I could convince the girl on the support line that there REALLY is a problem, and have them send a technician out to me, it was replaced quite quickly (and noisily - the whole office came around to see what's the screwing noise).

The repair tech told me that he's familiar with the issue and he's done a few similar repairs already (I wish the call centre could be a bit in touch with known problems with their hardware).

Anyway, ever since it was repaired I've had ZERO issues with my DELL (and I program, play WoW pretty much everyday on the thing).  I love it and I'm definitely going to get a DELL again.  (In fact I recommended my brother to get a DELL laptop last year and he did).

Now the choice of getting the perfect DELL laptop just got harder.  8 colours.  Damn...

Update

I wish it'd be easier to blog something about DELL.  Hello Dell are you listening?

Where's the DIGG/BLOG this button?

May be it's over in the Direct2Dell area

How do I write a cmdlet script?

I was a bit shocked at how "difficult" it was to find how to create a cmdlet script.  After all, it was pretty basic to write a cmd (or bat) file and just run it.

Anyway, here's the trick.

rename the file "myscript.ps1" (yes, that's right, .ps1 suffix, not .ps, nor .ps2, and 3 is two too far, 4 would be way out.  .ps1 it shall be).

I'm sure there's a story for this suffix, it would be nice to hear it.

Next, you need to sign your script so PS will allow it to run.  This is covered in numerous places, including the docs that came PS.

Update:

set-executionpolicy remotesigned

Will usually give you what you need - unchecked local execution but remote scripts (such as a remote-admin) must be signed.

get-help set-executionpolicy
get-help about_signing

Write this cmdlet

# filter directories, look for cs files.
$files = get-chilitem . -include *.cs -recurse
$regex = new-object -type System.Text.RegularExpressions.Regex "pattern"
foreach($file in $files){

$content = get-content $file
# run regex

if (regex.IsMatch(content)) {

#write-out
$file

}

}

#sorry for the lack of spacing - I'm typing code in a blog editor and pressing spaces is too much work

Few bits of update

1. Quit WoW (raiding too stressful, RL work taking up too much time)
2. Started playing LOTRO (no more raids this time)
3. Workload is heavy but I'm having fun again, which makes the experience quite a lot better.
4. I need more food (hmm, when is this not the case)
5. Sister came home from overseas
6. Changed ISP to TPG, mainly for the static IP address - I have an earlier rant about this one.
7. One of my fish died.  Now only 6 fish.  I'm really worried for the other small one.  But the tank is too small to get more fish.  Lina suggests that we get a bigger fish tank.  I think she's loving the idea.

Google-whacking techniques for naming your jira tickets.

Because JIRA search just sucks that bad.  We need extra help.

Here's an idea.  When you name a ticket for a task that you need to do in your project, pick a very unique name that you can always remember later.

For example, a web form:

Business Maintenance Form reloaded

or

There are two files here, please pick one and kill the other.

---

Then when you need to find the issue ticket again, it's simple to search for your 'keyword'.