TL;DR – Adapt or Become Manager
I’ve been working as a software developer for over 11 years, running a web development consulting business. I’ve had my share of success and failure. Along the way, I’ve been developing my own survival guide to doing what I do.
This is by no means The Perfect Silver Bullet for your career, but there might be some great gems or takeaways for you to figure out your own career plan.
In previous articles, I put together a list of the costs and benefits of Multi-Page Application design and the Single-Page Application patterns. Both approaches are used around the internet in hundreds of thousands of projects which support many desktop browser and mobile web devices.
Is there any middle ground between the two edges of web applications? Is there an approach that attempts to combine the strengths of each while also responding to the problems of both?
Despite not having yet entered Web 3.0, we are still exploring edges of web application development that bring us ever closer. Isomorphic application design is such an effort at closing this gap between MPA and SPA.
Popularized around the post-Web2.0 development era, the Single-Page Application (or SPA) is the complete client-side response to the MPA approach favored by most server-side developers.
In the same way that I tried to discuss the pros-cons of the MPA approach, let’s take the same angle to analyze if the SPA is right for your application.
Planning, developing and launching products has both never been easier and never been harder. The explosion of tools and platform eco-systems around the internet, have opened the doors for product developers everywhere. The problem is that it’s also easier then ever before to derail your product development efforts.
Keeping these tips in your arsenal will help to give you a better perspective when making product development choices.
Multi-Page Application (or MPA) Design has been a stable application pattern of web development since nearly the beginning of the world wide web itself. It is still a popular application approach of technology bases such as PHP / Django, Ruby on Rails and the ASP.Net stack, yet is under constant fire from some recent application design purists. Despite it’s popularity, they commonly argue that it is a pattern best left on the scrap heap of the World Wide Web.
WordPress as a product has come a super long way in the past several years. Long since moving on past a mere “blogging tool”, it is often a multimedia platform for many companies trying to stay connected with their audience.
As a product it has also been consistently improving. With each release, either stability is improved or a few features are added – most oftentimes both – which is a real feat in software engineering.
What is the hardest WordPress task?
But let’s get real here. The hardest thing about WordPress is NOT the software. The hardest problem is still getting a theme.
If you do any kind of research at all in product development, a common phrase spun by most of the online gurus is to “be different” in order for your product to stand a chance within the same marketplace that is swamped by other companies.
On the surface this passes as “good advice” but when it comes down to the meat and potatoes of actually building or launching your product, it’s nothing more than useless vague platitudes.