4 ms·
"Fast forward many years and many shipped products and I certainly don't feel that way. In the broadest sense I think I've learned to embrace ignorance in softw
by diminium 14y ago
"Fast forward many years and many shipped products and I certainly don't feel that way. In the broadest sense I think I've learned to embrace ignorance in software development"
So embrace ignorance? I could always go back to that but I'm wondering at what point do we grow? Things were much easier when I was ignorant of stuff and just pushed forward.
I did that for quite a long time. It created products but none of them were superior or great with most of them ended up being average.
I'm trying to climb that wall from just creating average things into creating something greater. I'm not sure how without being overwhelmed.
- mbenjaminsmith 14y agoWow, missed this one. I no way did I equate "embrace ignorance" with "embrace mediocrity". You misunderstand me. What I mean is that you have to write code in such as way that you don't have to understand previously created parts. They should be designed in a way that they just work -- they are easy to use and use without error.
- diminium 14y ago"They should be designed in a way that they just work -- they are easy to use and use without error." But how do you learn how to do that? For example, making an API. API's, once released into the wild, should never be changed (unless your hugely popular like Facebook). Public changes breaks code. I look at some of the most popular API's. They look easy but I don't know how they got to that point. They had an infinite amount of choices yet they choose that particular way of doing it.