Habits of Expert Software Designers
141–148 of 148 posts
Re: Habits of Expert Software Designers
#142Re: Habits of Expert Software Designers
#143Earlier quoted context omitted.
Take Galois proof of the insolvablity of the quintic. To understand it you first need to understand group theory and then field theory and obviously how these relate to the rational numbers and the ring of polynomials over the rationals. Next you need to understand field extensions and then you can start to make sense of galois groups. Then you need to understand the concept of solvability for groups and prove it’s e…
On the other hand, if you are VI Arnold, you can teach an honest version to motivated high school students in a relatively short timespan, https://amzn.com/1402021860
Re: Habits of Expert Software Designers
#144Earlier quoted context omitted.
The thing is, you can be very good at something without understanding it.
Define 'something'. As it stands, it's too broad.
Just ask them why they pick that certain color and you won't find rational behind it. They just...did, their hand just move to that color, paint it, and it looks good—the results of tons of practices over the years. Not to mention some artist didn't even have proper art education, not to mention art theory. Why and how it happened to be the same combination as in the color harmony theory is surely hard to explain.
Re: Habits of Expert Software Designers
#145How on earth is content this shallow drifting to the top of HN? Is any "non expert" software designer walking away from this enlightened in some way?
This article is adapted from the book “Software Design Decoded: 66 Ways Experts Think“ I imagine the idea is that if you want to go further, you buy the book.
Re: Habits of Expert Software Designers
#146Earlier quoted context omitted.
> That means we don't really understand it. I wonder if other physicists shared the sentiment.
I hope so. I've always thought the quintessence of science is pushing back the boundaries of ignorance. To advance we must first understand the true outline of our incomprehension. In that light, I don't think Feynman's remark is a negative sentiment at all. To know what what you do not know, etc. (c.f. confucious 2:17, rumsfeld 2:02)
I always seek clarity, and quite often 'complex' science is just about that, you get to see differently, eurekas. And when there's no eureka, to me then something is wrong, and the science has been accepted at face value which is also wrong.
Re: Habits of Expert Software Designers
#147Earlier quoted context omitted.
Define 'something'. As it stands, it's too broad.
I can think of example in other field: Art. Some people just great at using/picking color. They just pick the color they want quickly and paint without thinking about perfect harmony color scheme theory at all, yet their art always result in great color combination. Just ask them why they pick that certain color and you won't find rational behind it. They just...did, their hand just move to that color, paint it, and…
Re: Habits of Expert Software Designers
#148Earlier quoted context omitted.
I can think of example in other field: Art. Some people just great at using/picking color. They just pick the color they want quickly and paint without thinking about perfect harmony color scheme theory at all, yet their art always result in great color combination. Just ask them why they pick that certain color and you won't find rational behind it. They just...did, their hand just move to that color, paint it, and…
It sounds like you are describing intuition. I think there are occasional savants born with this, but for the majority of experts that subconscious decision mechanism is honed after years and years of work.
The trouble is you can't teach the intuition.