Last Monday, I was happy to finally get the opportunity to contribute to a blog I've been a reader of for a long time: Simple Programmer. I talked a bit about my journey as a developer and how others can learn from from it. Looking for a guest contributor to your own blog? Don't hesitate to reach out. Now, let's get to the post:
A couple years ago, I wrote a post that was very popular with conference organizers called "10 Conference Talks I'd Love to Give". This was great for both myself and organizers because if they were looking for a specific talk that no one had submitted, this offered a wide selection.
I'm no stranger to public speaking, but a couple months ago when I came across the concept of Ignite talks, I was in for an interesting new challenge. If you haven't heard of Ignite Talks before, it's a format of public speaking where your entire talk is comprised of 20 slides, each 15 seconds in duration, which auto-advance underneath your talk for a total length of 5 minutes.
One of the benefits of WordPress is that it’s open source and improving every single day thanks to the WordPress community. Yet, few people know exactly what that process looks like. When you identify a bug in WordPress, where is that information reported? Who fixes it? And how does it get pushed out to over 28% of the web in the next WordPress Core release?
Verifying someone's identification on the web can be tough, but there are a few services that we trust to be the true source of someone's online presence. How can we use these services to verify someone's identity to prevent them from having to create yet another online account? That's where OAuth comes in.
As your website gets more popular, you may find that your server is getting more and more strained with the extra traffic load. There are many things you can do to take the strain off of an overworked web server, but this week, we’re going to look at load balancing.
Earlier this month I spoke at a conference where I gave a presentation titled Scoping Digital Projects as a Non-Developer (slides from my presentation available here). Despite my presentation’s qualifier of 'Non-Developer' in the title, the principles of estimating the scope of a project are the same no matter what role you fill within your organization. In this post I will be offering an overview of a generalized scoping process that I have successfully used in the past. Though it is possible to go far into detail for each of the steps in the process, that will be covered in a later post.
Open source software is taking the world by storm and by now, most of us use at least one open source tool every day. Joining the open source community for the first time can seem daunting. Even if you're not a developer, you can still help the community of software that powers our lives every day.
Technology news has been filled lately with case studies of companies and developers taking their code “serverless” and saving time and money in the process. This seems to go against all traditional logic. How can server-side code run without a server? The answer lies in the fact that serverless infrastructure isn’t running without a server as the name implies, but rather the infrastructure is abstracted away.