3 ms·
> Many more people know how to invert a binary tree than know how to go from an empty text file to a non-trivial mobile app distributed in an App Store. As som
by csa 2y ago
> Many more people know how to invert a binary tree than know how to go from an empty text file to a non-trivial mobile app distributed in an App Store.
As someone who can do both but values the latter skills much more, I wonder about what these “low level questions” actually optimize for selection at some companies.
Part of me says that many companies want to select for willingness to “play the game” / conform rather than actually code deliverable product. In fact, being able to go from blank page to decent app in an app store might be considered a contra-indicator of a good applicant — easier for them to bail and do their own thing or be a hired gun.
Most orgs I’ve seen need a relatively small percentage of their devs to be creators and builders, but a large percentage need to be good maintainers and tweakers of existing code. These are vastly different skill sets and personalities, imho.
Thoughts on this?
And what sort of company / department do you work at that needs/wants a lot kf true builders?
- breadsniffer 2y agoInteresting. How many companies need people to build things from the ground up vs maintainers/janitors of complex systems? I think the type of interview (leetcode vs system design) might depend on what category the job fits into.
- csa 2y ago> How many companies need people to build things from the ground up vs maintainers/janitors of complex systems? In my experience, a good growth company will have at least the three following stages that can yield a healthy ROI with good builders: 1. Initial product (start up stage). 2. Secondary products and upsells. 3. Internal tools, iterative, and often in perpetuity for the life of the company. I am not sure the “builders” should ever be more than about 5-10% of the programmers except in early stage 1.