4 ms·
1. The ability to develop a solution within the tight confines of the problem. 2. Being able to recognize a bad design and improve upon it. 3. Not wanting to
by bliti 13y ago
1. The ability to develop a solution within the tight confines of the problem.
2. Being able to recognize a bad design and improve upon it.
3. Not wanting to re-invent the wheel every time the code base stinks.
4. The understanding that no problems in general might be new, but some specific problems inside a particular situation might be.
5. The importance of listening and taking into account the solutions others provide.
6. Being able to deliver. I have met too many full stack rockstars whose code never works and is as tight-coupled as melted cheese to bread.