Dealing with technical debt is one of the greatest frustrations and demotivaters to development teams. Technical debt is accumulated through out the software development lifecycle. Over time, the code becomes less and less clean which results in making changes more and more difficult.
As a developer and technology manager, I like to set really high standards to ensure that code is easy to read (understandable), simple enough for the task, and commented well enough that almost anybody could understand what is going on.
I don’t think jQuery is dead at this point, but it’s growth seems to be slowing.
A product manager is the person responsible for the creation of a particular product for a company or organization.
As a software developer, and technology manager, I’ve had a lot of experience in the past with variable website traffic.
In the past, I’ve worked on business to consumer information websites, I’ve worked on payment gateways and even on a few ecommerce sites.
As humans, we use data every day. Sometimes when we use data it’s completely subconscious – we don’t even realize we’re doing it. When we count the number of emails in our inbox, we can predict just how busy our day is going to be.
Backend developers work primarily on the server side of development, typically any scripts, databases, or architecture. Code written by backend developers typically helps communicate database information to the browser or mobile app.
As a programmer, and technology manager I think it’s really important to use the right tools and technologies. There are times where I think jQuery is still really valuable but there are a lot of times where I don’t think it is valuable.
Over the years, I have been really blessed to work on a number of API developments and to be able to consume a lot of APIs as well whether the APIs were in finance, sales automation (salesforce), or other services. A lot of the APIs had really noticeable deficiencies which I feel really made using the API a lot more difficult than it had to be.
This blog article is really a look at years of experience with APIs and a first attempt to at trying to make them easier to use for the developer. It’s really important to take time upfront and design a great API because it has the potential to be a huge asset for the company, and also has the potential to also be the company’s greatest liability.
A public API will have to remain virtually the same basically forever, so you really only have one chance to get it right. This is because customers or other integrators typically won’t ever update. If your API doesn’t have versioning you’ll basically never be able to make breaking changes. As users use your API and as feedback is collected you should be evolving the API. Continue reading
Node.js uses an event driven model that makes it really efficient and really good for real-time applications. Paired with serverless computing it’s fantastic for a lot of modern use cases.
In this article, I will go through the best practices for becoming a better Node.js developer. Over the last two years or so, I’ve interviewed and hired a lot of developers for the startup I’m working at. Continue reading
In late 2014, AWS Lambda launched and has grown in widespread use since then. AWS lambda is a serverless computing technology which has been a game change for software development.
AWS Lambda is a service that makes it easy to build small scalable applications. Lambdas are small functions that are packaged up and sent to AWS. Using a framework like the serverless framework makes it fairly easy to work with and pretty efficient.
Lambda is event driven. It works by responding to events whether they be timed, API driven or responding to events within AWS. One of the most common examples of using lambda is to resize images that have been uploaded to an S3 bucket.
Lambda is stateless meaning that every time a function is triggered, it is a completely new environment.
There’s so many reasons to use AWS Lambda. It’s easy to get started with it, it’s massively flexible, it is very scalable and more. Continue reading
I’ve been programming for a long time, and I’ve tried a lot of editors over that time. As a developer, I believe that my editor is the most important tool I have. At least half of what I do is done in my editor, a really terrible editor can even lead to injuries. Having a bad editor that isn’t working with my workflow leads to a lot of stress and wasted time. I was happy with Visual Studio for the most part, it could do everything I needed as long as I stayed on the microsoft stack. I find VS Code to be different, very different. Continue reading
Most software projects need to talk to a database at some point – they usually do GET queries for data, update a field or create a record. In the past, people would write raw code that communicated with the database and built an object or some code representation of the data that they would manipulate. This lead to an incredible amount of duplicated code for every project that usually had some subtle bug that was present in all libraries. Continue reading
One of the most important parts of building scaleable systems quickly is to find work that others have done and use it as part of our system. Using packages others built and assembling it with your business rules and logic is a lot like putting together pieces of Lego but following your instructions.
One of my favourite parts of React is that there’s usually hundreds of small open source components that can be used and usually easily modified to suit my needs. For example, there’s dozens of really well done date/time pickers that usually require no effort to put into place. Continue reading
Design patterns have been around for a long time in software development. Design patterns are basically a standard approach to solving a problem that can be found constantly in software development. Patterns are typically used for creating reusable designs, and defining the interactions between different objects or subsystems. I like to think of design patterns as a structured approach to software development and a very good way of improving communication between software developers. Continue reading
Cloud computing is basically using servers whether they be for databases, storage, application or something else through the internet. There’s quite a few different cloud computer providers – they’re billing schemes are typically very similar to how you would pay for electricity or gas for you car. Continue reading
When building websites, it can be really challenging to debug what’s causing unexpected scrollbars.
In this post, I provide a very good solution for debugging scrollbars. Continue reading
Writing maintainable code can be challenging especially to newer developers, because they won’t have experience with coming back to code later or having to review somebody else’s changes. In this blog post, I provide 5 Tips on How to Write More Maintainable Code. Continue reading