DIY PC meddling

One of the kids managed to break his laptop screen a while ago, its an Acer netbook. I was tempted to bin it but decided to investigate replacing the screen. The damage is not very clear from the pic, it was the internal structure that broke not the face of the screen, most of the marks you see are kid slime. (you know, sweets, snot, that sort of thing). I should have a taken a photo before I disconnected it, but there you go…

looking at this, replacing it didn’t look to bad.

And looking here (laptop-power.co.uk – link removed by request), replacements aren’t very expensive. Of course you can only get glossy now rather then the easy to see matt ones originally fitted.

Anyway the screen came on time/quickly and painlessly, it was well packed, undamaged and fitted. All good things.

Following the vid, it was pretty straightforward, took under an hour and actually worked when I turned it back on. All good things. And I didn’t have any spare screws or connectors or anything. Another good thing.

I find this informational side of the internet incredibly useful. Have you taken a punt on something that you wouldn’t have considered without successful internet research?

cheers

simon

My Worst Electronic Device Ever

Is my motorola droid/millstone.

here it is alongside the Crackberry it was meant to replace.

In fact it has been completely rubbish.

• The sideways form factor is very inconvenient
• the on screen keyboard is laughably unusable
• which is fine because the bundled Android email client is an embarrassment, Trades descriptions inspectors are currently  investigating whether calling it an email client is illegally misleading.
• The physical keyboard is so flat (so it will slide under) you cant really type on it, its not contoured like the BB.
• It weighs a ton
• The battery takes 3+ hrs to charge and lasts 20 mins (ok – exaggeration, but it wont last 24 hrs, unless I put it in flight mode when its lasts 3 days, or in the Netherlands where it also lasts 48 hrs plus, not in the UK or CH though.
• Android OS is ok, browser and email are appalling, but better alternatives are available in the marketplace.
• the millstone screen could be good, but as it ignores about 80% of inputs and misinterprets the other 20 its is useless. Its too small and won’t zoom reliably.
• The touchscream (sic) is now so totally fooked that it is unusable even by someone as calm and mild mannered as me. It has been given a 2 foot drop in an attempt to fix it, but is heading for a 4 foot drop/window lob any day now
• The music player is bearable, but close to impossible to manage a few hundred tracks.

Overall this pile of pants has put me totally off Motorola and touchscreens, I’m willing to give Android another chance, mainly cos there isn’t any real alternative. I want more control than Apple will permit, and Windows is too risky, and all the others have folded, or are about to fold I think.

I have bought a Blackberry which is a great physical device, but the software is complete rubbish. Turns out you can’t use a blackberry for anything other than phone and text without a specific blackberry data plan. The email app for example can only connect to a blackberry provider, or some web ones with a bit of messing. Far short of the ease of pointing Android at any POP or IMAP box. So the BB turns out to be a really dumb appliance. Especially when their servers go down eh?

Now RIM are struggling at the moment, and I can see why, not everyone wants to subscribe to a monthly plan to use basic services. Seems to me they could quickly and easily boost interest by porting Android to their devices. I bet given a few pointers the community would do if for them for free. Their form factor is a winner, but their software makes them a loser.

Motorola are about to release a BB form factor Android phone, but given my 12+ months of utter disappointment with the millstone I have no plans to buy anything of theirs again.

Have you got a good touch screen phone?

cheers

Simon

People or Process?

I’ve worked in quite a few different departments in quite a few different organisations, some were good, some not so.

But I have finally worked out what the fundamental difference between the good and the bad is.

The bad places to work focus on process, and believe if the process is ‘correct’ any ‘resource’ can perform it in an acceptable way to an acceptable standard. As long as Resource1 fills out the requirements template, Resource2, 3 or 4, or 1 can complete the design docs, and any resource can code it. Once its coded another resource can test and release it, job done. All resource can now be reassigned, sacked or outsourced – youpee.

The good places to work value people and recognise that individual skills and experience are the vital ingredients to a projects success or failure. Need to understand what the user Jo needs? ask Harry, he used to work in the biz he will be able to understand and translate it. Need a good design, get Harry to collaborate with Debs, she has architected loads of systems that all worked well. Need it coding? get Jack he knows whatever language Harry and Debs agreed will be best, He can help Harry write the code. Oh and while we are at it, why not get Jo the user involved frequently to make sure it is heading the way she expects?

All people, all social, all rewarding work, for everyone involved. But more importantly the collaboration means you don’t have to follow the ridiculous outdated, completely discredited, waterfall implicit in the faceless soulless bad co approach. So even the user Jo wins with people based development as she gets early access to shape and start using the system, and she learns a bit about trade offs.

Of course one of these represents all that was bad about 1970’s waterfall, and one represents all that is good about Agile approaches. Seeing IT people still doing waterfall is nearly as sad as seeing users retyping from one screen or printout to another. What’s doubly depressing is these two go hand in hand, in the same sad companies.

The other thing is, if you are, like me, trying to charge a premium over less experienced developers, process based places are scary. As they believe process is key, your experience and track record aren’t important or valuable to them. So, you will struggle to get anything over the general rate, and if you get a good rate you can expect an early chop. (After a painful period of being pulled back by ‘the lowest common denominator’).

Why are cos still trying to do waterfall? It looks easer to project manage. Once you have those requirements, someone can make up a guess of how long it will take and it can be programmed into the department workflow. Of course the unknown unknowns will have a bigger impact than the known requirements, so savvy PMs will at least double the guess. But a doubled guess is still a guess. You can still guess using a more agile approach, but maybe it would be better to totally revolutionise the project management and just work a prioritised list to time/cost constraints. But the inexperienced theorists in charge didnt cover that at college.

What do you think is the key difference between good places and bad places to work?

cheers

Simon