Let's talk about a guardrails in software. We all have certain objects, or pieces of state, that we don’t want anyone touching directly. But how do you enforce that? You can’t rely on a wiki page that says “Don’t update this field”, or a code
Ever onboarded to a well-established Angular app, updated a module, and cracked open its spec file… only to find it starts with a hundred lines of mock data? Suddenly your day kicks off with five hard flicks of the scroll wheel just to get down to the beforeEach. It feels
Let's talk about landmines today, and what one looks like in software. Before we focus our attention on test cases, a land mine is something that doesn't happen often, takes you by surprise, and when it does, you lose an arm, a leg, or in our
1. Tight coupling 2. Prolific use of any for (cntrl + alt + shift <insert name of property> to search entire codebase for where property is set) 3. And finally, no clearly defined patterns or practices (the practice isn't obvious, or really semi-apparent, I have to look for
The problem: Staying Motivated to Learn the Business You just got hired as a software developer for a toilet seat company (yes, somehow in 2025 the logistics are too complex to automate or outsource at this particular company...plus the job market is tough out there). You've confided
I’m a 7 year full stack developer, on most which jobs I’ve had, have had Angular as the front end codebase. One thing constant in my career is I’ve had a unique relationship with sort of the ‘ugly/unsexy’ side of software development, particularly the part that
This is Cort Angular, a brand new site by Cort that's just getting started. Things will be up and running here shortly, but you can subscribe in the meantime if you'd like to stay up to date and receive emails when new content is published!