If you’re a member of an Agile software team, you know that the routines of Agile can sometimes feel tedious. And it’s hard to know what to change. Do you need to change your meeting frequency? Can some routines be eliminated? Should you scrap Agile altogether? Rather than abandoning Agile, consider incorporating some simple design […]
Ember recently released a new set of features in what they’re calling the Octane edition. My teammate and I have started tinkering with new features to gain familiarity before upgrading our system to the new edition. One feature that has particularly caught my attention is angle bracket syntax—a new way of rendering Ember components that […]
If you’re working in an Ember app that’s been around for a while, you’ve probably wondered when to use get(this, ‘foo’) and when to use this.foo. You’re not alone.
Joining a project with an established codebase is tricky. There’s a significant amount of information to absorb, there may be new technologies to learn, and there’s usually a lot of code to read! These are five techniques I’ve used for finding sure footing in a codebase as a junior developer.
I’ve been working at Atomic for a little over a year now and, in that time, I’ve grown as a consultant, a software developer, and a person. Reflecting on year one, I realized three important lessons that I want to share with anybody entering their first job, regardless of the field.
I recently attended my first conference as a full-time developer. The conference was a great opportunity to grow my technical skills and hear what other people are doing in the industry. I also found that there was a fair bit of learning involved in navigating my first conference. Afterwards, I spent some time reflecting on […]
On my current project, I was tasked with implementing loading screens in our application. As it turns out, Ember has a built-in way of showing loading templates to the user! This built-in mechanism exists through what Ember calls substates. Let’s take a look at what these substates are and how you might use them.
There are compelling reasons to define your build definitions in code. While it may take some extra effort to make the switch, here are four great reasons to do so.
The Pipelines in Azure DevOps now support defining build configurations with YAML files. This is a huge advantage if your project is anything like my team’s and requires you to reproduce old builds.
You’re about to replace an old software system with a custom-built one that can do a whole lot more. Great! You’ll finally have software that truly fits the needs of your organization. You want to get the most out of this new system, but you’re not sure how. My first piece of advice? Get rid […]