Posts Tagged ‘Work’

What to do when Audacity won’t let you export/save as (blank dialog box).

Tuesday, May 20th, 2008

It would logically follow that if I’ve had this problem others must also have had it or be having it on a regular basis now. Unfortunately I don’t know how to trigger the problem and so I’m unable to provide you with a picture.

Versions: Caught in 1.3.4 and 1.3.5, haven’t tested anything else.

Symptoms: CPU usage climbs to 100% and when you click ‘export’ or ’save as’ you get a standard export/save dialog box but without a path or any files/directories shown. It refuses to let you search or manually input a path.

Possible related problem: I had this problem last immediately after the same project had got stuck while loading the audio into the memory. The issues might be related but I can’t see any reason to suspect that myself.

Solution: It’s not that hard but it took me a little while to work it out. Make a small edit and save, this seems to work every time. If it doesn’t then save and restart Audacity.

What doesn’t work: I tried all the normal tricks.

  • # killall audacity
  • # killall -9 audacity
  • Moving the files around
  • Renaming them
  • Manually comparing the .aup with other .aup’s and trying to fix.

Diagnosis: Bug, probably a stomach one. I honestly can’t see where the problem is, I’ve tried looking for it but don’t have the time to do full strace’s and all the rest of that fun stuff. Let’s hope the audacity team manage to find it and fix it. After all, Audacity is a brilliant tool even if it does lack a few things.

Kind regards, Robert.

Contracting

Wednesday, April 16th, 2008

I’m going to pass on a few things I’ve learnt over the years. I can hardly call myself a veteran contractor but I’ve certainly done quite a bit of it. I’ve made mistakes, I’ve accidentally done absolutely the right thing and then only realised afterwards how right what I’d done was.

Communicate

When working for someone you absolutely definitely must talk to them. Talk before you get the contract, talk while you’re working, talk when you’re finished. Many coders are the ’strong and silent’ type, this may work in bars but it doesn’t work on the Internet. People want to know what you’re doing, they want to be able to discuss aspects of the work, they like to feel that they’re paying someone who listens to them. I recently worked for one person in a situation where we exchanged just over a hundred emails before the funds even went into escrow, but this was good because we now both know exactly what is wanted and needed. Remember that it’s their money, they have a right to feel that it’s going to be well spent.

If you communicate well with people it often leads to follow-up jobs and good ratings on contract sites.

Be Positive

Use `I’m sure I can` instead of `I think I may`. Never lie. If you think you can’t do something admit it, but try to be positive. Make some friends who you can turn to and ask questions, if you’re contacted via email or a website then it’s rare you’ll have a time deadline which is shorter than the time you can ask someone in. IRC is an excellent resource for this, but don’t forget to google it.

Your time and experience are worth money

This is one that I have real problems with myself. I hate charging 70USD for something that’s maybe twenty minutes work for me. What you have to remember is that you’re giving them a bargain, they’re paying 70USD to have the work done in practically no time at all; if they didn’t pay you then they’d have to learn themselves, that could take year and hundreds or even thousands of dollars to get to your standard. They’re paying for you to learn (retrospectively) and for you to be as brilliant as you are.

Remember, your time and knowledge is worth what they’ll pay. If you think it isn’t then there’s always someone else willing to do it for more. If they come back to you then they obviously feel that they’ve had a good and worthwhile deal.

Suit your language to your client

If you wanted your car repaired and the mechanic first went into lengthy explanation as to what was wrong and what you’d have to do to make sure it didn’t happen again you wouldn’t mind much, on one condition. Presuming you don’t know anything about mechanics you don’t want to be told a lot of seemingly interesting stuff that makes absolutely no sense because he’s used words like ‘drive-shaft’ and ‘piston control’. What you want to know is that you shouldn’t turn right too sharply because the car is getting a bit old.

Apply this to your clients. If they know what you’re talking about you can give them some details, never but never make them feel stupid or try to show off. Never patronise, chances are if they own a multi-million dollar website they’ve heard the word script before and don’t need to be told that it’s ‘a part of the page that makes it work’. Keep a little bit of mysticism about your work, `script` has quite a technical air to it.

Don’t cook the goose

I’m guilty of this. It could be called over-communication, but cooking the goose sounds better to me. Never tell your employer how you’re going to fix something before they employ you. ‘I’m just going to edit this file to make this value correct so that it no longer causes your this problem.’ Google is as much their friend as yours, it’ll tell them all they need to know and all you need them not to know. They end up paying nothing for your expertise and doing their work themselves. Try to keep the balance between informing and losing.

In conclusion

These are the best tips that come to mind, there are certainly many more things that I’ve learnt and I would expect many more things to learn. Please feel free to comment here and add to my advice.

Contract work has it’s ups and downs, being your own boss is great as long as you know you’re definitely going to have work. At this point in time I’m not really having many problems getting contracts, but I can remember the days when I bid on a hundred and sometimes got one. I had to learn the hard way, please learn from my mistakes instead of your own.

Kind regards, Robert.

An excuse for a lack of blogging.

Thursday, February 28th, 2008

I’ve been ill. I hate being ill, especially when you can’t even get out of bed most days. I hate the fatigue after the illness. In general, I dislike being ill and all that goes with it. I had tonsillitis as a part of glandular fever.

Well, that’s that, I’m at least partially well now. The unfortunate fact is that I seem to be one of the few people who get a post-illness fatigue from glandular fever, either that or I’m just lazier than normal.

I’ve recently become involved in yet another business. It’s certainly very comfortable and they provide good training, nice perks and a very reasonable wage. They also are open to new people so get in contact with me if you’re interested.

In general I’m getting by in life, my next trip to the States is being planned. I could use some advice there, especially on an inexpensive way to get to Amsterdam airport from Norwich. I love swimming, but not in that cold conditions! One of the annoying sides of my local airport is that it doesn’t seem to provide many flights to anywhere, and those it does are rather expensive. To annoy me more I find the website for it is both badly designed and dysfunctional.

For those of you who know what ‘Project X’ or ‘That Project’ is, it’s now named ‘Footman’ and is coming on reasonably well. In fact I hope to have a working demo soon for internal testing.

V8d Org IRC will be moving to InspIRCd from UnrealIRCd. This move will take place over a set time (probably a day) which is yet to be confirmed. We will attempt to prevent any disruption, but some will be inevitable.

I think this should get everyone up to date with my life; if you have any questions, do comment.

Kind regards, Robert.