Make Something Every Day – Coding 001

Today, I was more gentle with myself. I pulled “coding”. Now I definitely don’t have any coding projects all set up and ready to go. But I am interested in how to automate my workflow for blogging on Hive. The process for wordpress is straightforward and handled by lots of different clients. I currently post … Continue reading Make Something Every Day – Coding 001 →

Today, I was more gentle with myself. I pulled “coding”. Now I definitely don’t have any coding projects all set up and ready to go. But I am interested in how to automate my workflow for blogging on Hive. The process for wordpress is straightforward and handled by lots of different clients. I currently post straight to a draft post on my wordpress.com having given draftsapp my credentials a long time ago. I’d like to be able to compose in one place and then click one button to send it to wordpress and another to send it to hive. I don’t want to be copying and pasting or doing something so automatic that it reduces my flexibility.

So today, I’ve poked around in the developers documentation for Hive. That makes it sound very efficient. Of course what I’ve actually done is googled stuff and then decided I needed to set up my own testnet and then realised I didn’t and wondered what I did need to install and then started going through the examples on the development portal and realised I’d forgotten how node.js works exactly and you know, it dawned on me that I’d started in the middle with the bit about posting rather than starting at the beginning and working my way through methodically, so no wonder…! Once I did that, I found the example for Hivesigner and by that time, either because this did what I wanted, or just because I’d looked at so much that wasn’t and so was getting my javascript-reading-eyes back, I understood mostly how it works and felt able to have a go.

Anyway, long story short, because yesterday what I really learned was that I don’t have to present something here for approval or be thinking of the audience at all, I’m writing for myself… long story short, I posted a little test post on the tuttleclub blog which I haven’t really used since I used it as an experiment in setting up a second account.

It wasn’t really a fail, because I did make something. I think I need to spend some time, not only reviewing what I’ve done, but also planning what I might do next. I’ve got lots of ideas in my head, but if I’m going to continue with this approach, they really need to be committed somewhere so that I can pick them up when I need them. So that I’d have something to start with yesterday morning (or today for that matter) without having to think almost from first principles.

In the case of podcasting, what’s notable is that I don’t have lots of audio clips stashed away, in the way that I have bits of writing, film or photography all ready to pick apart and put back together in a new form. Or if I do have a stash, it feels old and stale and a lot of work to breathe new life into it. I also feel like I’ve done the mumbling, bumbling improvised ramble character to death. It was so 2005 for me and, man, that was sixteen years ago – a different world and definitely a different me. And I’m not really interested in two-hander interviews either. There’s a new form of podcast out there that will excite me but I don’t quite know what it is yet. And making it will take more than a day’s sprint.