Trying New Technologies
Practice · Chapter 17
Why try new tech
Section titled “Why try new tech”- Good architects care about their craft and enjoy experimenting.
- You need not be an early adopter in production, but you must understand trending technologies.
- More technologies known = more tools available; you can pick the ideal one per job and articulate why one solution beats another — the antidote to the law of the instrument.
Go beyond awareness — try it out
Section titled “Go beyond awareness — try it out”- Being merely aware is not enough; get hands-on to understand deeply.
- Try new tech at work or on your own time — many are free, and paid products often offer free trial licenses.
- Build a proof of concept (POC): a prototype solving a real or contrived problem to test feasibility.
- Hands-on use forms real opinions on applicability, ease of use, advantages, and disadvantages — so when the moment comes to adopt it, you can give an informed recommendation.
Citations
Section titled “Citations”- Software Architect’s Handbook (Packt, 2018), Ch.17 “Trying new technologies”, p. 1176.