Threads for kaylindris

  1. 1
    kaylindris avatar kaylindris 1 year ago | link | on: Who's hiring? Q3Y2021

    Company: Union AI

    Company site: https://union.ai/

    Position(s):

    • Principal Backend Engineer
    • Staff Technical Writer

    Location:

    • ONSITE - Seattle
    • REMOTE also, we have teammates across and around the world.

    Description: We’re the core and principal contributors to flyte.org, an open-source orchestration platform. We’re looking for senior talent to contribute to both open-source and to work on proprietary products.

    Tech stack: golang, python on the backend, Typescript/React on the frontend

    Contact: Send me a message, or https://boards.greenhouse.io/unionai

    1. 2
      kb avatar kb 6 years ago | link | on: What are some of your favorite newer best practices?

      • Forcing constraint validation into the database; I’ve written more about this here, https://kev.inburke.com/kevin/faster-correct-database-queries/

      • Using secretbox for two-way encryption; happy to say I’ve merged documentation examples for both a Node library and the Go standard library

      • Using hub fork / hub pull-request to open pull requests (instead of using the browser or my gitopen tool)

      • Preparing/running database statements when you start your app instead of always parsing them when queries run

      • Spending more time with programming languages that have good standard libraries and make it easy to benchmark (not Node)

      • Merging PR’s as a single commit, I’ve probably merged ~300-400 pull requests this year and maybe 3 had more than one commit in them

      • Always merging branches on HEAD, so commits are linear.

      • Purposely duplicating blocks of code until it gets painful to do so / the abstraction is more obvious

      • I’d probably use GRPC for a new project, or at least protobufs for sending messages between servers.

      1. 6
        peterhorne avatar peterhorne 6 years ago | link

        Duplicating code until I’m more confident of the appropriate abstraction is something I’ve been doing more lately and I’ve found it really satisfying and interesting every time the eventual refactoring takes a different direction from my initial expectations.

        I’ve been tempted to try single commit PR’s for a while but have always refrained due to a fear of loosing useful information. On reflection, I can’t think of a single time this year where the individual commits have been useful so I could save a small amount of time and effort squashing rather than organising commits before submitting a PR.

        1. 3
          kaylindris avatar kaylindris 6 years ago | link

          Speaking of single commits, kinda related, my former VP of engineering used to commit at the end of the day… and if the work wasn’t done or ready to be committed, he would just git reset –hard. He would redo all the work the next day, do it way faster, and often find better ways of doing it.