Insights, perspectives, and stories on software, business, and innovation.
As a developer these days it's important to move with the times. In our day jobs here at DP towers, we uses all sorts of different technologies and aim to find the best fit for our clients projects - some use "traditional" server based languages like PHP (both with and without it's associated frameworks like Laravel, CodeIgniter and friends). We build and integrate with REST APIs, GraphQL, MariaDB, MongoDB and whatever "the next big thing" ends up turning out to be.
However, I can't help but feel a little like our industry is hell bent on using "the next big thing" without and real consideration of it's suitability for a solving a particular problem. I think this applies, in spades, within the front end development space.
In the good (bad) old days, we had a server side language like PHP, RoR, Python etc (does anyone remember ColdFusion!? that one really is a blast from the past) which was used for rendering dynamically generated HTML content and shipping that to the browser. On the frontend we had Javascript which, believe it or not, we were discouraged from using for any key areas of functionality, largely due to browser support
Published“I have been working with the team at Dev Partners for the last 3 years and we have always been impressed with the speed in which they act on things for us, along with the honest open communication we have between us. The team are a valuable and vital part of our supply chain and we look forward to continuing to work together for many years to come.”
If clunky systems are slowing you down, let’s talk. No sales patter. No corporate waffle. Just a straightforward conversation about fixing the stuff that wastes your time.
Two normal blokes who happen to be good at untangling messy systems. We’ll talk to you like humans, not consultants, and help you find the simplest way forward.
We’ll reply within one working day. No spam. No waffle.