Issue: 2018 - January/February

Rod focuses on what matters

In another of his articles on Angular, Paul dives into global configurations and shows you how to access your Angular applications from any component or service class.

Sahil teaches you how to organize and automate your work using one of the new features in SharePoint: Extensions.

Kevin learns the hard way how to estimate a process’ duration and he uses a clever bit of code to figure it out.

If you ever thought you’d like to develop the Next Big Thing, you’ll need Q’s advice about how to get started and what to do before you start writing code.

If HTTPS or HTTP over TLS and registering certificates has got you down, you’ll want to read Rick’s take on this required technology. He’ll show you how to keep your website safe and introduce you to some useful new technologies.

Miguel Castro argues that microservices are not merely tiny services but a holistic architectural approach that shapes how services, their callers, and clients interact to deliver robust, scalable applications. He emphasizes thinking in terms of architecture and boundaries, not just technology, advocating a holistic decomposition that foregrounds characteristics such as redundancy, isolation, dependency checking, service discovery, easy client access via an API gateway, ...and design-for-failure practices. Using a practical e-commerce example, Castro shows how client composition and fault tolerance must influence service boundaries and infrastructure, while acknowledging real-world trade-offs and the value of balancing theory with implementation realities.See More

In Apple’s new releases, there are a ton of new features to play with—even the AppStore has changed. Jason shows you how all of this impacts your development chores.

Continuous Integration might seem like a lot of cooks stirring the same pot, but Geoff shows us how it’s more like a community of mentors.

Ted Neward argues that fear, while a natural and sometimes protective emotion, is not the enemy of success—our relationship with fear is. He urges programmers to name and illuminate their fears, reframing risk as a necessary driver of growth, and to deliberately analyze when and how to take risks (e.g., pursuing a promotion or a key demo). By judging timing, embracing potential failure as a learning opportunity, and adopting a growth mindset, we can move from paralysis t...o productive action and continual improvement in our craft.See More