I’ll tell you a secret that no one else is really going to. It’s hard. Getting into web / WordPress developement is really hard. Whether you dive right in or start by spending 4 years in university studying computer science, the start is especially hard.
I started with WordPress back in 2007 (2.2.2), so that’s almost 8 years ago. I was young and used it purely as a blogging platform. I don’t remember it much as I have an awful memory and I was young & reckless, but it was pretty fun. WordPress was a pretty exciting thing back then and whilst it still is continuing to excite me everyday, it was especially ‘fresh’ back in 2007 (at least to me).
But I didn’t really know what I was doing. I had a theme, I think it was called Chameleon. I learnt a bit of CSS and managed to change the colors to green and black. That was exciting. I learnt enough HTML that I could add a logo – also very exciting. It was really damn hard though.
It’s no secret that almost everywhere in the world has its own local WordPress group. That in itself is really awesome, and on Meetup alone there are over 650 dedicated WordPress meetup groups.
So there’s really no reason not to be involved in your local community, if you happen to love WordPress, Open Source and/or PHP.
I’m naturally an idiot so this took me a while to get a good understanding of. Even now I still mess it up, but I feel like I can at least grasp the basic requirements of being a good contributor on GitHub – so let me share them with you!
Coding in public is pretty scary. Not just for contributors, but for project maintainers too. Everything is being watched and recorded and saved forever – there’s no (easy) erasing of mistakes, which leads to a lot of pressure on everyone involved.
So take a step back, realise that this is open-source software, and relax. GitHub is the proverbial playground for an open-source project, where things can discussed and tried – don’t be afraid!
I’m not going to preach to you, but I’m going to ask to consider that if you’re a developer or have interested in development at all, should you be coding more?
You don’t have to be building complex solutions to even more complex problems, solving all the world’s problems with your beautiful code. No, it doesn’t have to like that.
But writers tend to try and write everyday, just to keep that creativity and energy inside of them alive, so shouldn’t the same apply to developers or ‘coders’?
Over the past few years, the concept of Freemium Software seems to have been given a lot more attention than it has in the past. Sure, the phrase was only coined 8 years ago (yeah, I looked it up), but it has existed for decades.
However, with the emergence of free web software and libraries like WordPress & jQuery, freemium software has recently found a place in developers’ hearts.
Especially in the world of gaming, both online (Facebook) and mobile (iPhone / Android), freemium software has started to become the norm, with content producers finding that it’s more profitable to give a little bit for free and charge a lot for the extras.
If you keep an eye on WooThemes people, you may have seen the Blogging for Benjamin competition that took place last year.
Basically, a few of us Woo people are going to try write a blog post, every day, for the next month. It sounds crazy – it sounds improbable, but it’s true.
We’d all love to blog more often but tend to be pretty lazy, so we figured an internal competition to see who could keep it up for a month, would force us to fight through the laziness and blog daily.
It’s going to be called Blogging for Hippo, in honour of the impending WooCommerce 2.3 release – Handsome Hippo.
There’s a quote, a Greek proverb, that came to my attention a few months ago and never left for a moment.
A society grows great when old men plant trees whose shade they know they shall never sit in.
So I wrote about it. Have a read!
It’s been just about 3 months since I started working in a customer-facing position at WooThemes, helping customers with their WordPress and WooCommerce problems. In that time, I learnt a few things about people, relationships, happiness and open-source software.
Read the Article on Medium
Captain Theme started over 2 years ago. As I’ve grown as a web developer, so too has Captain Theme.
In the 18 months I haven’t given it the time it deserved. Themes and plugins went un-updated and I’m sorry for that.
I’m back to give it another go and I feel I’ve got a lot more to bring to the table this time around. I’ve already released a new plugin this month, Captain Admin. It’s a premium plugin being sold over at CodeCanyon for $18. I feel it offers a pretty cool set of tools to customise the WordPress admin!
There’s also Captain Team, another new plugin I’ve just released. You should check it out too!
The site has just been given it’s 4th (or maybe 5th?) make-over. I’m happy with how it’s turned out. It’s originally based on James Koster’s Highwind – an awesome free WordPress theme, customised to suit the purpose of the Captain Theme site. So what is the purpose? Really just to provide an easy way to access documentation, support and see the plugins I’ve put together over the years, all in one place.
At the moment I’m working on something pretty special. It’s going to be two things:
I spent a lot of time trying to decide whether or not I should release it as a premium plugin. I decided to head in the same direction as some of the big guys like WooCommerce, Easy Digital Downloads and WP Job Manager and take the free route. I still need to put food on the table though so I will be offering some premium add-ons for a small price too.
I’ll post more about it soon. For now, back to coding!
A post I made a month ago on a site I help run, Android Australia.
I have to make this quick. I don’t have much time. I have to write this post. It has to be edited. Feature images have to be made and formatting has to be done. It has to be posted. Then people have to find out about it. We’ll post it on our page on Facebook. Then on our personal Facebook accounts. Time for Twitter. Don’t forget to add hashtags. Retweet on personal twitter. Over to Google+. We’ll post it on the page there, with tags of course, and then probably on our personal Google+ accounts there, for those in our circles to see. We’ll then have to +1, tweet and like the post, before going into standby to reply to comments/messages relating to the post.