3 ms·
That’s a fair point, and I get where you're coming from. By “highly valuable,” I meant consistently making a meaningful impact—whether that’s through solving ke
by Userrr 1y ago
That’s a fair point, and I get where you're coming from. By “highly valuable,” I meant consistently making a meaningful impact—whether that’s through solving key problems, improving processes, or just being someone others can rely on. But yeah, you're right—sometimes doing more than the norm can backfire in certain environments. I guess the goal is to be valuable and strategic—knowing when to push and when to hold back depending on the culture.
- dsq 1y agoRight, so when discussing a high productivity role, havig mastery of both the structure (such as a DB) and of the tools to investigate the structure (text manipulation, SQL querying) are key. In my experience most developers like to skip knowing about the data.
- Userrr 1y agoYeah, exactly—that deep understanding of both the structure and the tools makes all the difference. It’s surprising how often people overlook the data itself, even though it’s usually where the real insights (and problems) are hiding. Mastery there really separates someone who’s just coding from someone who’s solving.