Conversation

I had an informal expertise extraction conversation yesterday, with a senior software engineer I respect. The preliminary takeaway for software design expertise is that experts *attempt to predict the direction of change* for their software requirements, and design accordingly.
6
87
Replying to and
IMHO this fits into a larger dichotomy of school vs work: in school we learn to solve problems that millions of other students have solved before us; a right answer is out there – you just have to figure it out, by yourself, without help. After undergrad, it's the opposite!
1
1
Replying to and
School: solve this problem set, once you get the right answer, you can forget about it and move on Work: everything's a moving target, nobody has any idea what the right answer is, and if you actually succeed in buildilng something useful, you'll be maintaining this forever
2
1
Replying to and
It seems totally possible. Say, have a whole bunch of simulations, where students come up with a solution for some problem, and then after each submission, they uncover new information — the client changes their mind, the API they used turns out to be flakey, etc.
1
Replying to
Let's add it to the list of things they don't teach in school :)
Quote Tweet
Things school usually doesn't teach: - nutrition - kindness - self-reliance - mindfulness - relationships - healthy habits - love of reading - money / finance - emotional control - long-term thinking - importance of writing Fortunately, it's never too late to learn.
1