![]() Over the years, my experience has been that there are always the same questions that need to be discussed and answered across the product team before you start discussing technical things. If you don't know your playground, you have no chance to argue technical decisions. Yes, I also like to discuss this kind of technical stuff.īut these discussions are useless at the beginning of building a new system, because you have to define your engineering playground first. In my role as Tech Lead and Software Architect, I've been involved with many new software initiatives with product teams.Īnd it's always the same traps that software development teams first fall into: The need to discuss these fancy technical and low-level architectural design topics. are these questions even relevant at the beginning of a software initiative? ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |