• 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle
  • As much as technologists like us wish we could prioritize efficiency and use the latest and flashiest tools all the time, that’s just not practical. When you say you want each company to have an objective set of technical requirements when choosing a toolset, you also have to have a set of practical requirements. What is the cost of friction of adding a new tech stack to the company?

    Adding electron means just learning electron. Adding Tauri means learning Tauri and Rust.

    It’s like the saying goes, “the best camera is the one you have with you”. It’s true with any business decision.


  • If I’m a company and want to bring something to production quickly, what should i choose:

    1. A relatively new tool that has seen barely any production use and thus could have a bunch of unanticipated problems. Also nobody uses it so every new engineer you bring onto the project has to learn something entirely new before they can start really contributing. You also have no idea how long it will be supported by its developers into the long term future.

    2. A battle hardened, production tested tool that has a huge community, has been around for a long time, and that a lot more developers already know how to use.

    Sure #2 might be slower by a few fractions of a second, but if I’m in charge of the business i know which option I’m going to choose 100% of the time.