Matt Armstrong Web Development

Let me start by saying: I’m a huge fan of the services that AWS has. Their documentation is some trickster god’s joke on developers. I already knew this but got to jump into it recently with some lambda work. Do they tell you everything they need to? No, because development in AWS is only fun if you have no clue why nothing is working! 1. Lambdas don’t have connectivity to the outside world without additional

Let’s start this off by saying: this plugin made me curse…a lot. I don’t know who made certain decisions from a development standpoint, but there are some incredibly questionable ones that I ran into. I’m documenting them here in case others have to develop any integrations for this. I’ll also say: I actually do really like the plugin and believe it’s incredibly useful as a front-end calendar display. It does what it says out of

A client reached out to me recently with an interesting problem. They wanted to: Register guests as new users (easy) Allow existing users to checkout as guests (less easy) The client already had code set up to connect these guest account purchases to the existing account based on billing email. The code worked, but only if guest checkout wasn’t enabled. They needed to get past the restriction of forced login by WordPress/WooCommerce when an existing

So, as I sit here discussing clients and things with my office mate, it occurred to me that one of the biggest reasons for broken and bad plugins is simply client ignorance.  When I say this, I don’t mean that code is something a client should be checking out; in fact, if the developer is decent, the client can report an issue and the dev will fix it. However, I run into issues constantly where clients