Attention: This article was published over 11 years ago, and the information provided may be aged or outdated. While some topics are evergreen, technology moves fast, so please keep that in mind as you read the post.For JavaScript development, there are more build tools than you know what to do with. The non-verbal utterance category contains the two most popular ones, …
Client: A large federal government agency Industry: Federal Government Services: DevSecOps Platform Engineering, CI/CD Architecture, Cloud Migration, Application Security Integration Outcome: A unified CI/CD platform supporting 400 to 500 applications across four technology stacks, with time-to-deployment reduced by more than 30% and thousands of engineering hours saved annually. Large federal agencies rarely run one technology stack. Java teams, JavaScript and …
In my last post, Implementing GitHub OAuth with NextAuth.js, we set up a standard single sign on flow with GitHub OAuth in NextAuth.js. This article assumes that you have followed along with that article already, and have your own version of that project locally. If not, but you already have a Next.js project, then you can follow along here just the same.
Last time, we set up a very basic dashboard to demonstrate displaying a signed-in user’s name, avatar, and some usage data from the GitHub API. Since then, NextAuth.js has evolved into Auth.js, but the GitHub implementation remains largely the same. However, if you haven’t upgraded your Next.js projects in a while, I would recommend doing so first.
In this post, we’ll pick up where we left off: upgrading your project’s dependencies, then decomposing your components into a scalable library using atomic design principles (atoms, molecules, organisms, templates, and pages). From there, we’ll install and configure Storybook for Next.js and Tailwind, write your first component stories in Component Story Format 3, and set up shared fixtures so you can preview and test components without depending on live GitHub API calls.
Learn how enterprise teams use AI coding tools with guardrails, governance, and workflow structure to improve speed without sacrificing code quality or control.
Many organizations are experimenting with AI coding tools, but fewer are measuring or achieving consistent, repeatable results from enterprise AI-assisted development in practice. The difference is not the tools. It is how engineering teams operationalize them day to day.
These observations are drawn from internal engineering roundtables and hands-on client work, where teams are actively working through how AI fits into production development workflows today.
In this post, I’ll walk through a few key reminders that helped me while making the transition from Java to JavaScript, especially while working with React and React Native.