In the May issue of Hacker Monthly my piece Why you should never ask permission to clean up code (which has received over a quarter-of-a-million views to-date) was published and I’m extremely grateful to the Hacker Monthly team for their consideration.

I highly recommend picking up a subscription to Hacker Monthly (if you don’t already have one shame on you).

“Can I take some time to clean up this code? It is horrendous.” The answer should always be yes to this question. However, often times we find ourselves up against walls in the form of budgets, time, due dates and expectation and so the typical “powers that be” at companies often veto the request. My advice to you, dear developer, is to never ask for permission for things you know are vital to your work.

You know your work environment better than I do so perhaps you can ask this question and immediately have the full support of your team. Sad to say that many aren’t so fortunate. They’ll ask their boss if they can take some time to clean up their code, make it efficient and extensible and, while the boss may recognize the need for such tasks, ultimately the boss will simply say “maybe we can do that later”.

Why is this the typical reaction? Because bosses don’t have to read, edit and support the code.

This is folly and every developer knows it. Bosses, (if you’re reading this) putting off a few hours worth of code clean-up now will only turn into many hours or days in the future. So by allowing your developers time to do this much needed code maintenance you’re actually saving your company money. But don’t worry – they’re not going to ask you for permission anymore. They’re just going to do it.

This is pretty great and something I’ve never seen before. The ColorADD System is a system of ‘codes’ that can be used to identify colors for people that are color blind. By knowing each color’s specific code, as well as a particular syntax, the person can discern just about any color in the spectrum.

/via Colour Lovers.

The script isn’t anything special mind you, all it does it “watch” any Flickr feed for new entries. To be more precise, my server runs this script every 15 minutes and checks for new photos, when there is one, it creates a TinyURL and posts it to Twitter (like this).

But I wanted this to work for Pownce.

I immediately dove head first into Pownce’s API only to find out that the API didn’t allow posting anything. I thought my Powncing days were over until, out of some crazy stroke of coincidence, I read an article on TechCrunch that said Pownce was due to release a new version of their API the very next day. Turns out, I didn’t even have to wait that long and the Pownce wiki was updated to include documentation for version 2 of their API.

Without blinking an eye I finished my script, grabbed myself an app_key, and Pownced the script (you’ll need to be logged in, and be my Pownce friend to see this Pownce message). Once I figured out that I couldn’t Pownce a file to the general public, I knew I had to find some time to write this post.

Since then I read that Dave Winer also enjoys the way Pownce shows links to Flickr photos and that he is running a similar script. So I thought I’d put this out for everyone to use.

Powncer!

Enough beating around the bush, you can download the script here which includes an XML parser for ripping through Flickr’s RSS feed. You’ll need to edit the first few lines of powncer.php for it to work, so this isn’t your run-of-the-mill plug-and-play type script, unfortunately, but for the PHP savvy of you, you should be able to get it up and running pretty easily. If you need help getting it setup, just ask in the comments.

I run this script here on cdevroe.com every 15 minutes using cron. You may run it however you’d like.