2 ms·

> The value is knowing the right patterns and repeating them at the right time and place. And that discernment, at least in part, comes from understanding what

> The value is knowing the right patterns and repeating them at the right time and place. And that discernment, at least in part, comes from understanding what that code is really doing. I get 45 minutes face-to-face to develop an opinion as to whether or not a candidate can do the job well. I value candidates who’ve not only asked “what?” but have also asked “why?” I’ve no doubt my approach has filtered out people who would have done good work. I’ve certainly passed people through that didn’t work out for various reasons. But generally, my approach has served me well so far.

unity1001 4y ago
> comes from understanding what that code is really doing It does come from understanding the !business code! that is involved. Not the rarely important features of the underlying language that the stack, the framework or the models handle. Which makes that argument further moot - you should not be messing with how the models or the framework handle those data types. There is a reason why they were built and deployed.