Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. If all you do in your tech career is:

If all you do in your tech career is:

Scheduled Pinned Locked Moved Uncategorized
16 Posts 10 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • gnomon@mastodon.socialG gnomon@mastodon.social

    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@mastodon.socialG This user is from outside of this forum
    gnomon@mastodon.socialG This user is from outside of this forum
    gnomon@mastodon.social
    wrote last edited by
    #2

    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.

    1 Reply Last reply
    0
    • gnomon@mastodon.socialG gnomon@mastodon.social

      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.

      K This user is from outside of this forum
      K This user is from outside of this forum
      kkarhan@jorts.horse
      wrote last edited by
      #3

      @gnomon sadly all 3 are avtively discouraged in so many cases...

      1 Reply Last reply
      0
      • gnomon@mastodon.socialG gnomon@mastodon.social

        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.

        aimaz@mstdn.socialA This user is from outside of this forum
        aimaz@mstdn.socialA This user is from outside of this forum
        aimaz@mstdn.social
        wrote last edited by
        #4

        @gnomon also, sometimes finding the answer to “how did this ever work?”

        1 Reply Last reply
        0
        • gnomon@mastodon.socialG gnomon@mastodon.social

          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.

          glennmg@mas.toG This user is from outside of this forum
          glennmg@mas.toG This user is from outside of this forum
          glennmg@mas.to
          wrote last edited by
          #5

          @gnomon
          Excellent lessons to take to heart in or out of tech.

          1 Reply Last reply
          0
          • gnomon@mastodon.socialG gnomon@mastodon.social

            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.

            scherzog@mastodon.gamedev.placeS This user is from outside of this forum
            scherzog@mastodon.gamedev.placeS This user is from outside of this forum
            scherzog@mastodon.gamedev.place
            wrote last edited by
            #6

            @gnomon This is the kind of post that makes me wish I could star it more than once -.-

            gnomon@mastodon.socialG 1 Reply Last reply
            0
            • R relay@relay.infosec.exchange shared this topic
            • gnomon@mastodon.socialG gnomon@mastodon.social

              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.

              hoagie@jawns.clubH This user is from outside of this forum
              hoagie@jawns.clubH This user is from outside of this forum
              hoagie@jawns.club
              wrote last edited by
              #7

              @gnomon #3 is something that I have been praised for in multiple annual reviews by many levels at the company

              gnomon@mastodon.socialG 1 Reply Last reply
              0
              • scherzog@mastodon.gamedev.placeS scherzog@mastodon.gamedev.place

                @gnomon This is the kind of post that makes me wish I could star it more than once -.-

                gnomon@mastodon.socialG This user is from outside of this forum
                gnomon@mastodon.socialG This user is from outside of this forum
                gnomon@mastodon.social
                wrote last edited by
                #8

                @scherzog ❤️

                1 Reply Last reply
                0
                • hoagie@jawns.clubH hoagie@jawns.club

                  @gnomon #3 is something that I have been praised for in multiple annual reviews by many levels at the company

                  gnomon@mastodon.socialG This user is from outside of this forum
                  gnomon@mastodon.socialG This user is from outside of this forum
                  gnomon@mastodon.social
                  wrote last edited by
                  #9

                  @hoagie that is a damn fine accomplishment.

                  1 Reply Last reply
                  0
                  • gnomon@mastodon.socialG gnomon@mastodon.social

                    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.

                    chrisamaphone@hci.socialC This user is from outside of this forum
                    chrisamaphone@hci.socialC This user is from outside of this forum
                    chrisamaphone@hci.social
                    wrote last edited by
                    #10

                    @gnomon strong agree ❤️. so, do you know of any companies that are prioritizing hiring and retaining people who are good at this?

                    1 Reply Last reply
                    0
                    • gnomon@mastodon.socialG gnomon@mastodon.social

                      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.

                      stenpett@mstdn.gamesS This user is from outside of this forum
                      stenpett@mstdn.gamesS This user is from outside of this forum
                      stenpett@mstdn.games
                      wrote last edited by
                      #11

                      @gnomon I'm happy to say, all three are commonplace where I work. Especially number three

                      gnomon@mastodon.socialG 1 Reply Last reply
                      0
                      • stenpett@mstdn.gamesS stenpett@mstdn.games

                        @gnomon I'm happy to say, all three are commonplace where I work. Especially number three

                        gnomon@mastodon.socialG This user is from outside of this forum
                        gnomon@mastodon.socialG This user is from outside of this forum
                        gnomon@mastodon.social
                        wrote last edited by
                        #12

                        @stenpett that's fantastic. Well worth some pride.

                        1 Reply Last reply
                        0
                        • gnomon@mastodon.socialG gnomon@mastodon.social

                          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.

                          jmax@mastodon.socialJ This user is from outside of this forum
                          jmax@mastodon.socialJ This user is from outside of this forum
                          jmax@mastodon.social
                          wrote last edited by
                          #13

                          @gnomon - You ask a high standard. I will do my best.

                          1 Reply Last reply
                          0
                          • R relay@relay.mycrowd.ca shared this topic
                          • gnomon@mastodon.socialG gnomon@mastodon.social

                            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.

                            b4ux1t3@hachyderm.ioB This user is from outside of this forum
                            b4ux1t3@hachyderm.ioB This user is from outside of this forum
                            b4ux1t3@hachyderm.io
                            wrote last edited by
                            #14

                            @gnomon see, I keep trying to do that and the CEO keeps foaming at the mouth and screaming “AI” like a pterodactyl.

                            gnomon@mastodon.socialG 1 Reply Last reply
                            0
                            • b4ux1t3@hachyderm.ioB b4ux1t3@hachyderm.io

                              @gnomon see, I keep trying to do that and the CEO keeps foaming at the mouth and screaming “AI” like a pterodactyl.

                              gnomon@mastodon.socialG This user is from outside of this forum
                              gnomon@mastodon.socialG This user is from outside of this forum
                              gnomon@mastodon.social
                              wrote last edited by
                              #15

                              @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@hachyderm.ioB 1 Reply Last reply
                              0
                              • gnomon@mastodon.socialG gnomon@mastodon.social

                                @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@hachyderm.ioB This user is from outside of this forum
                                b4ux1t3@hachyderm.ioB This user is from outside of this forum
                                b4ux1t3@hachyderm.io
                                wrote last edited by
                                #16

                                @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. 😉

                                1 Reply Last reply
                                0
                                Reply
                                • Reply as topic
                                Log in to reply
                                • Oldest to Newest
                                • Newest to Oldest
                                • Most Votes


                                • Login

                                • Login or register to search.
                                • First post
                                  Last post
                                0
                                • Categories
                                • Recent
                                • Tags
                                • Popular
                                • World
                                • Users
                                • Groups