I received an email via my website tonight. It came from a person facing failure. What do you do when your startup fails? His reaction was fantastic.
If your developer goes AWOL, you better have a plan B. Here's a list of folks I have on speed dial if I need help. You might want to save this list too.
Over the last day or two, a lot of conversation has been going on – some on a recent post I wrote, some on our Advanced WordPress facebook group, and some on this great article by Brian Krogsgard at Post Status. In the end, if you don’t like the breaking changes that come with Advanced …
Sometimes you have no idea until it's too late that the reason your web developer went AWOL was you. Here's the flawed logic you may be believing. If so, stop. Please.
In the case of ACF I feel like they've made two common mistakes related to backward compatibility that we could all learn from.
It's something I never thought about when I first started using WordPress. But today I appreciate it more than ever. It's a tool that helps me change lives.
The second post in my AWOL series gives you three tips that can help you (if you're worried about developers going AWOL), even before you start.
If your developer or web designer goes AWOL, here are the five steps I recommend you take. After all, you don't want to repeat the situation again, right?
"Think before you speak." Another way to say the same thing, when it comes to blogging, is to plan before you write.
We don't talk about it a lot but as the WordPress ecosystem matures, we should start thinking about product families. It will help everyone.