2 ms·
> Don’t > 7. Personally fix bugs and ship features. You have to write code to remain an effective tiebreaker... Should "write" be "read" here? I'm not sure I u
by wool_gather 7y ago
> Don’t
> 7. Personally fix bugs and ship features. You have to write code to remain an effective tiebreaker...
Should "write" be "read" here? I'm not sure I understand this point.
- kemitche 7y agoI read that bullet point as "Yes, you should still write code now and then, so that you're at least loosely familiar with the code base and challenges, but don't put yourself anywhere near the critical path for your product."