Category: Articles (Page 152 of 258)

Personal opinions and how-to’s that I’ve written both here and as contributions to other blogs.

Getting Started with Fixing WordPress Bugs

July 21, 2015 / Tom / 0 Comments

It’s one thing to have a local copy of the latest version of WordPress installed on your system – don’t get me wrong, it’s really cool to be able to see some of the new features – but it’s another thing to want to get involved in contributing to the codebase.

Sure, it’s completely possible to get started by trying to implement your own desired feature, but the likelihood that it’s going to be merged into core is very, very small. Those type of decisions have a process through which they undergo before being merged. Plus, that’s taking on a lot if you’re just getting started with contributing code to WordPress.

But what about trying to fix WordPress bugs? That is, what if you were to want to try to take your chances with fixing some of the existing problems with the software?

That’s a bit easier.

WordPress and Subversion: How To Check Out The Latest Code

July 20, 2015 / Tom / 0 Comments

There’s a lot going on as it relates to working with WordPress right now: People are discussing things ranging from dependency manage (via tools such as Composer) and talking about the up and coming REST API (which is really exciting).

I’ve also recently read that the object-oriented programming approach is just now making its way to WordPress development. Personally, I don’t fully agree with that, but I do think that there are some advanced topics that are making there way over such as inversion of control, dependency injection containers, and so on.

All of those are important things to be discussed, shared, and taught to others, for sure. But sometimes, I think that we forget that there are some basic things about WordPress that those who are just getting involved need to learn before getting into those topics.

These things include how to grab a copy of the latest version of WordPress from the trunk (let alone explaining what “trunk” – or source control – even is), how to get started with working on your first set of issues, and so on.

WordPress Trunk

This is something that I think those involved in WordPress development could do a better job of teaching. To be clear, I think some do a fantastic job. Some are also very quiet – and that’s fine, not everyone cares to blog and many people are heads down on important work.

But as much as we want people to be involved in open source, I think we should make sure people are educated as well as possible to get involved and have a clear understanding of what to do.

Opting not to share information doesn’t mean you’re greedy; however, as I’ve been thinking about the wide range of topics that exist for those who are trying to get involved in WordPress or who are looking to up their game as it relates to object-oriented programming, I thought it might be worth sharing some shorter articles on how to get started with some of these topics.

The Obligations of Learning a New Programming Language

July 15, 2015 / Tom / 0 Comments

One of the challenges that we – as programmers – are constantly faced with is learning a new programming language or whatever the latest and greatest technologies that are available (and using the term ‘greatest’ is just for the sake of the cliché phrase).

Then again, a lot of us get into this field for that exact reason, don’t we? I mean, we enjoy learning new technologies, applying them within the context of programming and problem solving, and then doing it again.

But after even just a few years in the business, it can get a little exhausting. This doesn’t mean it’s any less rewarding, but it does mean that when something else comes along – especially from the likes of larger players like Facebook, Twitter, or a similar company – other people are going to want to use them in their projects because the other company uses them and then we’re tasked with learning them.

For what it’s worth, I don’t consider it a bad thing, but it does contribute to the amount of time that goes into a project. This particular idea is something that’s better suited for a business-related post so I digress, for now.

But there’s another side to this:

A segment of the programming culture claims that we should be keeping our skills sharp by learning something new each year or so in order to make sure that we’re still relevant, to make sure that we’re still able to keep up with those coming up behind us, and generally able to keep up with the direction the web and/or software is headed.

And I don’t necessarily disagree with this, but if you’re in a position where you’re raising a family, or you’re in a position where you’re a little bit older and have obligations and responsibilities outside of your work such that you can’t spend as much time at a computer as you used to do (and I know that feel!), then this comes off as a very intimidating and frustrating demand on our time.

So why do we do it to ourselves?

Role Models in Software Development

July 13, 2015 / Tom / 0 Comments

As adults, some times I think it comes off as weird to talk about looking for “role models” as we usually look for people who are like mentors, advisors, influencers, etc. But for the purpose of this post, just assume that I’m talking about someone who influences us, or someone who’s further down the road than we are and from whom we can learn.

In so many other areas in our lives, especially when we’re younger, we often look for (or are told to look for) role models – you know, those people to whom we can look up and aspire to be like one day. Sometimes it’s in music, sometimes it’s in sports, sometimes it’s in writing, and in other times it’s in other areas.

Maybe this is a bit of a cynical stance, but sometimes I think it’s hard to find someone that’s worth looking up to for inspiration regardless of the arena.

But then I remember that when we look up to people, we often look up to people for what it is that they do versus who they are. For example, perhaps a person conducts their personal life in ways that you don’t agree, but they may conduct their professional life in ways that’s inspiring.

I think it’s important to divorce the two so that we know what it is to which we’re being inspired.

Red Flags in Business (For Self-Employment)

July 8, 2015 / Tom / 0 Comments

I realize that the majority of what I write here has to do with WordPress development and topics that are tangential to that (like my opinions on certain issues around the software). But one thing that I rarely talk about is how things are going with respect to running a business that’s built on top of said software.

Right now, in technology, it’s hip to be a part of a startup, to aim to be something that’s emulating what’s happening in Silicon Valley, or that’s trying to create the next big thing by bootstrapping your business or by accepting some type of capital.

And all of that is completely fine. For whatever it’s worth, I think it’s really neat reading how others approach building a business and developing their product or service whatever it may be. My story simply isn’t like that – it’s not the kind you’re going to see on Product Hunt, Hacker News, or any of those other types of sites.

All of that’s okay with me. It’s not – nor has it ever been – what I’ve aimed to do with Pressware.

In short, Pressware would be classified as a bootstrapped company (that’s undergone a few name changes since the LLC was formed – a story for another time) and out of which I work in order to help provide solutions for other people using WordPress.

Pressware

That’s it all there is to it.

Anyway, I thought it might be interesting – if anything – to begin sharing my experience as to what it’s like running a business based around WordPress and how I deal with some of the challenges that it presents outside of development.

I don’t know if any of this will be helpful to those who are working within a larger company, running their own business, or serving as a contractor in any other type of industry, but who knows?

Some of the posts that I’ve written in the past that I thought were boring and almost never published ended up becoming those that resulted in interest and genuine discussion. (This is also why I think other people need to speak up and contribute to the blogosphere. :)

With said that, one of the things that I’ve had to learn how to handle as the years have passed is handling red flags as they come up.