Time Changes Everything
2015-08-13 09:13
309 查看

onE oF THE THingS I’ve been most entertained by as the years have gone by is observing what things have lasted and what haven’t. So many patterns, frameworks, paradigm changes, and algorithms—all argued for with passion by smart people, thinking of the long term, balancing all the known issues— have not warranted more than a yawn over the long haul. Why? What is his- tory trying to tell us?
pick a Worthy Challenge
This one is tricky for a software architect. Challenges or problems are given to us, so we don’t have the luxury of choosing, right? It’s not that simple. First of all, we often make the mistake of believing that we can’t influence what we are asked to do. Usually we can, but it gets us out of our comfort zone in the tech- nology space. There are dragons there when we don’t choose to do the right things. Time passes, we have worked diligently and hard solving the requested challenge, and in the end it doesn’t matter: we didn’t do what was really needed and our work is wasted. Over time, a good solution to the right challenge will probably outlast all others.
Simple Rules
We say it to ourselves: keep it simple, stupid. We say it, but we don’t do it. We don’t do it because we don’t have to. We are smart and we can handle some

complexity and easily justify it because it adds agility to our design, because it is more elegant to our aesthetic sensibilities, because we believe we can anticipate the future. Then time passes; you walk away from the project for a year or more. When you come back to it, you almost always wonder why you did what you did. If you had to do it all over again, you would probably do it differently. Time does this to us. It makes us look silly. It is good to realize this early, get over yourself, and really try to learn what simple means in the lens that only time can grind.
Be Happy with That old Stuff
Architects love to search for the “one true way”: the methodology or school of thought that provides the predictability we crave and the clear answers that always seem just out of reach. The problem is that whatever guiding light you have in one year will probably not match the guiding light you have in a couple of years, much less a decade later. As you look back, you will always be looking at designs that don’t match your current expectations. Learn to embrace that old stuff, and resist the temptation to think you should go back and “fix” it. Was the solution an appropriate one for the problem? Did it solve the needs of the problem? Keep these as your measure—you will be a lot happier.
Time Changes Everything
Philip NelsononE oF THE THingS I’ve been most entertained by as the years have gone by is observing what things have lasted and what haven’t. So many patterns, frameworks, paradigm changes, and algorithms—all argued for with passion by smart people, thinking of the long term, balancing all the known issues— have not warranted more than a yawn over the long haul. Why? What is his- tory trying to tell us?
pick a Worthy Challenge
This one is tricky for a software architect. Challenges or problems are given to us, so we don’t have the luxury of choosing, right? It’s not that simple. First of all, we often make the mistake of believing that we can’t influence what we are asked to do. Usually we can, but it gets us out of our comfort zone in the tech- nology space. There are dragons there when we don’t choose to do the right things. Time passes, we have worked diligently and hard solving the requested challenge, and in the end it doesn’t matter: we didn’t do what was really needed and our work is wasted. Over time, a good solution to the right challenge will probably outlast all others.
Simple Rules
We say it to ourselves: keep it simple, stupid. We say it, but we don’t do it. We don’t do it because we don’t have to. We are smart and we can handle some

complexity and easily justify it because it adds agility to our design, because it is more elegant to our aesthetic sensibilities, because we believe we can anticipate the future. Then time passes; you walk away from the project for a year or more. When you come back to it, you almost always wonder why you did what you did. If you had to do it all over again, you would probably do it differently. Time does this to us. It makes us look silly. It is good to realize this early, get over yourself, and really try to learn what simple means in the lens that only time can grind.
Be Happy with That old Stuff
Architects love to search for the “one true way”: the methodology or school of thought that provides the predictability we crave and the clear answers that always seem just out of reach. The problem is that whatever guiding light you have in one year will probably not match the guiding light you have in a couple of years, much less a decade later. As you look back, you will always be looking at designs that don’t match your current expectations. Learn to embrace that old stuff, and resist the temptation to think you should go back and “fix” it. Was the solution an appropriate one for the problem? Did it solve the needs of the problem? Keep these as your measure—you will be a lot happier.
相关文章推荐
- 普林斯顿大学公开课 算法1-8:并检查集合 高速查找
- Objective-C:继承、分类(Category、extension)、协议(protocol),个人理解,仅供参考
- [CodeForces 300C Beautiful Numbers]组合计数
- 如何在WIN7中关闭JAVA自动更新
- 深入理解计算机操作系统——第7章:静态链接
- C#-遍历datatable的几种方法
- onSaveInstanceState和onRestoreInstanceState触发的时机
- win10 qq登陆不了怎么办?Win10qq提示无法访问个人文件夹的解决办法
- Spring 学习笔记(一)
- hive cli启动报错
- javascript获取本机操作系统类型的方法
- javase的多线程断点下载
- leetcode_Jump Game
- linux 上传本机文件:curl、unzip
- IOS 单元测试
- android /linux休眠与唤醒(一)
- CSU 1598 最长公共前缀
- 大数据可以像股票一样交易了,贵阳、武汉先尝鲜
- Fixed Point Float Intro - Q (number format)
- 九月十月百度,迅雷,华为,阿里巴巴笔试面试六十题(第411~470题)