![]() In some cases, like for open source projects, this can be published as part of a repo to document the decisions made with reference to embedded or included technologies. Two solutions are starting to gain popularity in the software development world amongst companies like GitHub, Spotify, eBay, and CNCF:ġ) Architectural Decision Records (ADRs) andĪDRs are really just a record of what’s been decided. Thankfully, there’s a solution to help you plan the discovery, assessment, and selection of technologies within your product stacks. More time spent planning up-front, discussing the pros and cons of technology options, results in less risk to the project, and the business overall. The same can be said about selecting technology, whether it’s for a specific product or an entire platform. IBM said it best, back in the reign of Rational Rose: if you spend more time planning, you waste less time coding. But to productive development, planning must take a central role. Sure, pure innovation, such as in a hack-a-thon, has its place. ![]() But that doesn’t really work in a functional business environment. Part of the process, the part that gets creative juices flowing, is just doing. ![]() Many developers grew up programming on their own, oftentimes not taking the time to develop specifications prior to jumping into a project, building it. In an ideal world, wouldn't it be valuable for everyone to be on the same page when it comes to the technology decisions related to the products they are going to launch or support?Ī solid 10% of being an engineering manager is asking two people if they've talked to each other yet- Adrienne Porter Felt apf) February 4, 2020 ![]() Those decisions may be okay for the engineer working by themselves, perhaps on their own project, but most career software folks are part of larger teams, in larger organizations that include product managers, quality assurance, operations, and more. What developer hasn’t become so immersed in a coding project that has spanned 5 cups of coffee and several missed meetings? And during that solitary affair, many developers make technology decisions, such as platform or tool selection, in a silo. Even within development groups that have adopted agile methodologies, coding is often a solo effort. Let’s face it, roadblocks often make it challenging for software engineers to collaborate. ![]()
0 Comments
Leave a Reply. |