Atomic Spin

article thumbnail

How to Avoid Stakeholder Gridlock on Your Software Project

Atomic Spin

Have you ever been to a meeting that involved a dozen or more people, that constantly went too far into the weeds, that couldn’t come to a consensus, and that left you feeling like nothing was accomplished? It was horrible, right? You probably never want to have that experience again. This kind of frustrating situation can quickly become the theme of a software project when too many stakeholders are involved and nobody has clear decision-making power.

article thumbnail

Want to be a Better Consultant? Learn to Work Strategically

Atomic Spin

Looking to level up your consulting skills? One thing I’ve observed among our more senior Atoms is a mastery of approaching work strategically. What Do I Mean by Strategy? As consultants, we juggle a lot of different concerns and goals. At a high level, our goals are things like: Deliver quality software Hit budgets and timelines Provide a great experience for our clients Once we get down into the details of actually creating software, however, these goals get a lot more complex and nebulo

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

How We Built a Scrappy Curriculum Editor using VSCode, TypeScript, and AWS Lambda

Atomic Spin

Great apps aren’t stuck in the mud. They change with the times. They float like oak leaves along a wide river of user expectations, business requirements, fashion trends, and platform changes. To keep floating, leaves apps need a watchful team of developers to walk the muddy banks nudging them back toward fast water whenever they beach on rocks or swirl into murmuring whirlpools of chat bots.

Lambda 40
article thumbnail

How TypeScript Shaped our Entire Codebase for the Better

Atomic Spin

Over the last year and a half, I’ve had the pleasure of working on a web app built in TypeScript. I came to Atomic with no web development experience at all. On my first couple of projects, I spent most of my time working on small, relatively isolated pieces of functionality for various applications: a bit of UI development here, some Rails model changes there.

article thumbnail

A “Grand Unified Theory” of Agile

Atomic Spin

Okay, that’s a bit grandiose, I admit. But I often see tweets or posts about how people don’t “get” capital-A Agile. Tweets like this and this point out common faults. Everything they say is technically correct but not especially useful. Pointing out all of the not-get-its in the wild won’t make people “get it” better, so these sentiments are useless.

Agile 52
article thumbnail

Villainous Personas – Anticipating the Users You Don’t Want

Atomic Spin

You know and use personas for a majority of your projects, but I’m here to tell you that you may have missed a category of user. A very important one. A not-so-friendly one. Users Who Mean Harm Let’s pretend you’ve created a beautifully functioning and user-friendly app. It’s living and breathing in the world when, BAM! An unfriendly, nay malicious, user begins threatening your ecosystem by attempting to scam your users or utilize your service for wrongdoing.

article thumbnail

A Guide to Evaluating Closed- and Open-Source Libraries

Atomic Spin

Picking the right libraries for your project is important. The wrong ones can create long-term headaches and introduce technical debt that will eventually be very expensive to correct. When making your choice, there are a few important things to think about, and a few common things to avoid. Considerations for Closed-Source Libraries Libraries are either open-source or proprietary, and there are different considerations for both.