If all you do in your tech career is:
-
If all you do in your tech career is:
1. When something is slow, you look carefully at the output of a profiler or a query plan & make measured suggestions about what to improve;
2. When something breaks badly, you gently but insistently ask what & why until you truly know, then the next time similar work is needed you bring up how to avoid doing what broke last time; and
3. When someone lacks info, you make them feel good for learning instead of bad for not knowing;
You will do good work.
-
If all you do in your tech career is:
1. When something is slow, you look carefully at the output of a profiler or a query plan & make measured suggestions about what to improve;
2. When something breaks badly, you gently but insistently ask what & why until you truly know, then the next time similar work is needed you bring up how to avoid doing what broke last time; and
3. When someone lacks info, you make them feel good for learning instead of bad for not knowing;
You will do good work.
Of course you can aim higher. It doesn't feel like the glory days of early computerization where a week in the server closet can change the world, but there are still a million ways we can make things work better in the large and in the small.
But you can do a lot of good by doing the basics really well. People will thank you for it, sincerely, because it's more than many folks contribute. You can set a good example, you can hold out a helping hand; you can prove it's not a zero-sum game.
-
If all you do in your tech career is:
1. When something is slow, you look carefully at the output of a profiler or a query plan & make measured suggestions about what to improve;
2. When something breaks badly, you gently but insistently ask what & why until you truly know, then the next time similar work is needed you bring up how to avoid doing what broke last time; and
3. When someone lacks info, you make them feel good for learning instead of bad for not knowing;
You will do good work.
@gnomon sadly all 3 are avtively discouraged in so many cases...
-
If all you do in your tech career is:
1. When something is slow, you look carefully at the output of a profiler or a query plan & make measured suggestions about what to improve;
2. When something breaks badly, you gently but insistently ask what & why until you truly know, then the next time similar work is needed you bring up how to avoid doing what broke last time; and
3. When someone lacks info, you make them feel good for learning instead of bad for not knowing;
You will do good work.
@gnomon also, sometimes finding the answer to “how did this ever work?”
-
If all you do in your tech career is:
1. When something is slow, you look carefully at the output of a profiler or a query plan & make measured suggestions about what to improve;
2. When something breaks badly, you gently but insistently ask what & why until you truly know, then the next time similar work is needed you bring up how to avoid doing what broke last time; and
3. When someone lacks info, you make them feel good for learning instead of bad for not knowing;
You will do good work.
@gnomon
Excellent lessons to take to heart in or out of tech. -
If all you do in your tech career is:
1. When something is slow, you look carefully at the output of a profiler or a query plan & make measured suggestions about what to improve;
2. When something breaks badly, you gently but insistently ask what & why until you truly know, then the next time similar work is needed you bring up how to avoid doing what broke last time; and
3. When someone lacks info, you make them feel good for learning instead of bad for not knowing;
You will do good work.
@gnomon This is the kind of post that makes me wish I could star it more than once -.-
-
R relay@relay.infosec.exchange shared this topic
-
If all you do in your tech career is:
1. When something is slow, you look carefully at the output of a profiler or a query plan & make measured suggestions about what to improve;
2. When something breaks badly, you gently but insistently ask what & why until you truly know, then the next time similar work is needed you bring up how to avoid doing what broke last time; and
3. When someone lacks info, you make them feel good for learning instead of bad for not knowing;
You will do good work.
@gnomon #3 is something that I have been praised for in multiple annual reviews by many levels at the company
-
@gnomon This is the kind of post that makes me wish I could star it more than once -.-
-
@gnomon #3 is something that I have been praised for in multiple annual reviews by many levels at the company
@hoagie that is a damn fine accomplishment.
-
If all you do in your tech career is:
1. When something is slow, you look carefully at the output of a profiler or a query plan & make measured suggestions about what to improve;
2. When something breaks badly, you gently but insistently ask what & why until you truly know, then the next time similar work is needed you bring up how to avoid doing what broke last time; and
3. When someone lacks info, you make them feel good for learning instead of bad for not knowing;
You will do good work.
@gnomon strong agree
️. so, do you know of any companies that are prioritizing hiring and retaining people who are good at this? -
If all you do in your tech career is:
1. When something is slow, you look carefully at the output of a profiler or a query plan & make measured suggestions about what to improve;
2. When something breaks badly, you gently but insistently ask what & why until you truly know, then the next time similar work is needed you bring up how to avoid doing what broke last time; and
3. When someone lacks info, you make them feel good for learning instead of bad for not knowing;
You will do good work.
@gnomon I'm happy to say, all three are commonplace where I work. Especially number three
-
@gnomon I'm happy to say, all three are commonplace where I work. Especially number three
@stenpett that's fantastic. Well worth some pride.
-
If all you do in your tech career is:
1. When something is slow, you look carefully at the output of a profiler or a query plan & make measured suggestions about what to improve;
2. When something breaks badly, you gently but insistently ask what & why until you truly know, then the next time similar work is needed you bring up how to avoid doing what broke last time; and
3. When someone lacks info, you make them feel good for learning instead of bad for not knowing;
You will do good work.
@gnomon - You ask a high standard. I will do my best.
-
R relay@relay.mycrowd.ca shared this topic
-
If all you do in your tech career is:
1. When something is slow, you look carefully at the output of a profiler or a query plan & make measured suggestions about what to improve;
2. When something breaks badly, you gently but insistently ask what & why until you truly know, then the next time similar work is needed you bring up how to avoid doing what broke last time; and
3. When someone lacks info, you make them feel good for learning instead of bad for not knowing;
You will do good work.
@gnomon see, I keep trying to do that and the CEO keeps foaming at the mouth and screaming “AI” like a pterodactyl.
-
@gnomon see, I keep trying to do that and the CEO keeps foaming at the mouth and screaming “AI” like a pterodactyl.
@b4ux1t3 *three reply drafts aggressively redacted on the stern advice of my lawyer*
I hope that the eventuality of this problem solving itself happens quickly and does not negatively affect you in the process
-
@b4ux1t3 *three reply drafts aggressively redacted on the stern advice of my lawyer*
I hope that the eventuality of this problem solving itself happens quickly and does not negatively affect you in the process
@gnomon hehehehh. Oh it’s resolving itself alright. Right into the ground. But that’s okay, I figure I have a year or so of runway before I need to bounce, company is in a niche that’s hard to lose once you’re in it, but that won’t save it forever. Already looking for new things.
