Skip to main content

· 8 min read
Josh Kaplan

With the adoption of new techniques comes the inevitable and inadvertent introduction of bad habits. Agile transformation is no exception. The countless frameworks, certifications, and literature (including articles like this one) describe a wide landscape with varying practices and differing opinions. This lack of clarity makes it hard for teams without practical experience to adopt Agile methods effectively and easy to misinterpret best practices. In this article, I describe some of the most common Agile misconceptions, why they are harmful to teams, and what you can do to recognize and fix them.

· 25 min read
Josh Kaplan
Note

This literature review was written as part of the course requirements for ESI 6891. This HAS NOT been peer reviewed and should not be considered a peer-reviewed publication.

I feel that this review needs further exploration and refinement beyond the scope of requirements as a course deliverable. However, I feel that until such time when it is further refined the content of the review may provide value in a self-published format. As such, I have chosen to publish it as-is on this site.

This was originally written in October 2022 and was first published on this site in August 2023.

· 7 min read
Josh Kaplan

This past week, I had a discussion with a student team about microservices. This is a topic I've wanted to write about for a while and given the immediate relevance to this team, I finally made it a priority.

The microservices architecture is a popular and growing trend in many technology organizations today. But its implementation is often met with unsurmountable challenges by unprepared teams. This article discusses some of the challenges of microservices and how to overcome them.

· 5 min read
Josh Kaplan

This article discusses some of the factors that contribute to project success and what you as an individual team member can do to influence that success. When I began writing this article, I intended it as a guide for my undergraduate senior design teams. As such, some of the examples below are aimed at that context.

· 6 min read
Josh Kaplan

As teams mature their DevOps capabilities one of the questions that inevitably arises is this: How do we achieve traceability between deployed versions and source code? Because at some point or another, we will encounter an issue in production that doesn't seem to make sense given the code the engineering team has on hand. The goal to know, with certainty, what version of the source code aligns with the deployed system is instrumental to enabling the team to solve the right problem.

· One min read
Josh Kaplan

Cracking the Coding Interview by Gayle Laakmann McDowell is a must have for anyone interviewing for software engineering jobs. Whether you are preparing to interview for your first internship or you are an experienced professional, this book is a comprehensive walkthrough to prepare you for the process.

The beginning of the book describes typical examples of the technical interview process and covers some core computer science theory. The second two-thirds or so of the book covers programming practice problems and knowledge questions followed by a detailed solutions section.

Going through the practices problems in the book is a great way to refresh old skills or identify knowledge gaps you need to focus on and give you the confidence you need to be ready for the interview process.