I recently found this info useful from this link, when I was repurposing an old disk for a temporary and experimental installation of windows.
Although it apparently changed a few years ago, I was surprised to find out yesterday that ebay has changed it selling fees to include postage and packing charges! That seemed pretty harsh to me… but well they don’t charge basic listing fees any more, so… However, after a little rash of recent sales I noticed that the final value fee had been charged on postage that the auction winner had actually collected in person!
Well, after getting ebay to ‘call be back’ I had a short and successful call in which they refunded me the small fee on postage as I described… and explained what I could do to prevent the problem recurring.
If a buyer collects from you, you need to ‘re-invoice‘ them inside of ebay. This will apparently provide options for refunding postage, and will also supposedly connect to Paypal and refund any amount if necessary.
Writing good error handling code is hard in any language, whether you have exception handling or not. When I’m thinking about what exception handling I need to implement in a given program, I first classify every exception I might catch into one of four buckets which I label fatal, boneheaded, vexing and exogenous.
Read Eric Lippert’s full post for ideas on classifying exception types for your circumstances, and thus whether or not you should attempt to handle such exceptions!
I finally seem to have fixed a problem that has apparently been with me for weeks since updating Windows 10, but I have not noticed! Basically, Outlook 2013 was failing to send emails from either of my accounts that used SMTP / Imap (but was working fine for a client email address using an Exchange server).
…and the Solar System is pretty Big too:
Thanks to the following post by Geoff King I finally managed to install Quicken 2004 onto my Windows 8.1 computer: The steps I took to run Quicken 2004 on Windows7 Professional Solved – Windows 7 Help Forums.
The picture was taken in my office a few weeks ago. It is not faked. The output of an automated build system (Team City) is reporting how many days there have been problems with the build for; and the number of days is 42.
When an individual makes the same mistakes repetitively, you might ask why they do so, why they don’t learn (and of course; ‘Why don’t they improve?’), and so on. When the same thing happens within a professional organisation, we need to ask why the business doesn’t learn, and why the business allows the individual to continue on that path. I think I have a couple of suggestions why this might be.
A very personal note this time. Last week I released a project that was pretty-much the largest single release that I’ve worked on for my current employer.
Like many systems, the history of this one is that as customer applications made their way through the relevant processes, the system recorded various information about the processes that happened and how they worked out. The system then used the presence or absence of those success / fail records to decide what needed to be done next.
A What? A Clock – ok, I get that! A ‘Moon Clock’ – what’s that? And why’s it tidal powered?
Thankfully, I am here to answer these questions for you 😉