miraantabrez

Hypertune (https://www.hypertune.com) | ONSITE (London) | Senior Product Engineer

We're building the most flexible platform for feature flags, A/B testing, analytics and app configuration. See https://docs.hypertune.com for more details.

At the core of Hypertune is a visual, functional, statically-typed programming language with first-class citizens for analytics, A/B testing and AI “loops”.

Our UI lets users define their configuration logic in this language and our SDKs act as interpreters, evaluating the logic locally, synchronously, in memory.

As a senior product engineer, you'll work mainly in TypeScript and React.

If you're interested, please email miraan at hypertune dot com with your LinkedIn, CV or a link to a project you've built!

Hypertune (https://www.hypertune.com) | ONSITE (London) | Senior Product Engineer

We're building the most flexible and developer-friendly platform for feature flags, A/B testing, analytics and app configuration. See https://docs.hypertune.com for more details.

At the core of Hypertune is a visual, functional, statically-typed programming language with first-class citizens for analytics, A/B testing and machine learning loops.

Our UI lets users define their configuration logic in this language and our SDKs act as interpreters, evaluating the logic locally with zero network latency.

As a senior product engineer, you'll work mainly in TypeScript and React.

If you're interested, please email miraan at hypertune dot com with your LinkedIn, CV or a link to a project you've built!

Agreed that you lose the benefit of "instant updates" if it's always controlled by a PR.

But Git-style version control with history, diffs, branches and pull requests are pretty useful for feature flags and other "app configuration".

Version history and diffs are great for knowing what flag logic changed when + debugging what broke prod.

Branches let you test and preview flag logic changes in your own isolated branch (which you can point the SDK at) — this is a cleaner approach to having a few separate "environments" like development, staging, production which can drift from each other.

Branches are also great for refactoring the schema / structure of all your flags, e.g. deleting a bunch of flags in one go.

Pull requests and approvals are great for when you're making changes to sensitive flags. E.g. you can lock down specific flags.

Pull requests are also great for onboarding nontechnical team members like PMs or sales reps so they can safely make flag changes themselves but require approval from an engineer (at least while they learn to use the system). Empowering nontechnical people is also why a UI is important.

Branching and pull requests are also a great way to prevent conflicts / overwriting other team members flag changes.

So Git-style features are pretty useful, but you also want the UI and you only want to enforce pull requests for specific flags or team members — this is what we built at Hypertune.

This is one of the reasons we built type-safe feature flags at Hypertune. When a developer deprecates a flag, they get type errors everywhere it's still used. This fails the build so they're forced to remove all the flag references, and they get a nice IDE / compiler driven workflow to do that. Otherwise it's easy to leave flag usages around.

Hypertune (https://www.hypertune.com) | ONSITE (London) | Senior Full Stack Engineer

We're building the most flexible and developer-friendly platform for feature flags, A/B testing, analytics and app configuration. See https://docs.hypertune.com for more details.

At the core of Hypertune is a visual, functional, statically-typed programming language with first-class citizens for analytics, A/B testing and machine learning “loops”.

Our UI lets users define their configuration logic in this language and our SDKs act as interpreters, evaluating the logic locally with zero network latency.

As a senior full stack engineer, you'll work mainly in TypeScript and React.

If you're interested, please email miraan at hypertune dot com with your LinkedIn, CV or a link to a project you've built!

Hypertune (https://www.hypertune.com) | ONSITE (London) | Senior Product Engineer

We're building the most flexible and developer-friendly platform for feature flags, A/B testing and "application configuration". See https://docs.hypertune.com for more details.

At the core of Hypertune is a visual, functional, statically-typed programming language with first-class citizens for analytics, A/B testing and machine learning.

Our UI lets users define their configuration logic in this language and our SDKs act as interpreters, evaluating the logic locally on clients with zero network latency.

As a senior product engineer, you'll work mainly in React and TypeScript to craft a beautiful product that delights our users.

If you're interested, please email miraan at hypertune dot com with your LinkedIn, CV or a link to a project you've built.

One problem with calendly is sending links politely without seeming like the other person should bend to your schedule / do the scheduling.

So I‘ve usually said something like: “what’s the best time for you? You can also pick a time here if easier:”

But maybe there’s a product experience that can solve / prevent this problem.

We've run into this exact issue. We have state in Redux, Apollo and the URL and are looking to consolidate it all somewhere. It's surprising there's no standard solution for this yet. Yours looks very interesting — did you look for any libraries which do this for you? Or do you plan to open source yours?

This is the overlooked advantage of a schema (e.g. in GraphQL): it forces you to think about the data types and contract, and serves as a good way to align people working on different parts of the code. It also scales to other languages besides TypeScript which helps if you ever want to migrate your backend to something else or have clients in other languages (e.g. native mobile apps in Swift, Kotlin, etc).

Hypertune (https://hypertune.com) | Open source platform | UK, Europe, US, Canada | Full-time | Remote/Hybrid | Founding Full Stack Software Engineer | $125k+ | 1% to 2.5% equity

Hypertune is a type-safe code configuration platform. It can be used for feature flags, A/B testing and AI-powered optimization. It can also be used for configuring and optimizing in-app copy, pricing plans, business rules, etc.

At the core of Hypertune is a visual, functional, statically-typed, cross-platform, open-source programming language with first-class citizens for analytics, A/B testing and ML. It's designed for code configuration but has broader possible applications.

Our UI lets users define their configuration logic in this language and our SDKs act as interpreters, evaluating the logic locally on clients for zero latency.

As a founding engineer, you'll play a crucial role in shaping the product, company and culture.

Apply at https://forms.gle/vpjgbNJuVgYnWuLs7 or connect with me on LinkedIn or email me (email in profile).

This is on the roadmap. Under the hood, the UI is a functional programming language, a bit like the Dhall configuration language, but with primitives for A/B testing, event logging and ML. So we'll have a code interface too for GitOps workflows.

Yes it's designed for handling lists of any config objects, whether that's resources, cron jobs (e.g. email jobs with parameters for sender, body, etc), in-app onboarding guides, blog posts (for use as a CMS), etc. And thanks, glad you like the site.

Yes we provide SSO without a big SSO tax.

Sounds like a good use case! If you use the OpenAPI schema in your Hypertune project schema, this should just work. You'll get the nice CRUD UI for the CRDs, then you can use the GraphQL API to query them.

Hi, thanks for taking a look!

1) Quite easy - once you define your schema, you can share projects with any stakeholder (internal or external) to update the configuration logic from the UI themselves.

2) Granular permissions are built into the logic tree UI so you can control who has access to which subtrees. E.g. you could say you and your developers have access to the root. But a specific stakeholder only has access to a specific subtree to control newsletter layout, a list of user IDs, etc.

3) You can query the configuration via GraphQL. And we're working on a way to let you update your configuration logic via an API too.

ChatGPT is great when the time consuming bit is googling the details of libraries, APIs, languages, algorithms, etc, and wiring them together in the right way for a small bit of functionality or some boilerplate. But when the time consuming bit is thinking about the best way to solve a problem / introduce new abstractions in the context of a larger system, it seems less useful. Maybe this will improve with the context size.

Thanks, that's great to hear!

1) Yes, we plan to build SDKs in more languages. But you can still use the GraphQL endpoint today from any language / codebase with type-safety using GraphQL codegen tools.

2) Yes, the language is powerful enough for basic code and it sounds like your use case will work. We made the language total for safety reasons so you don't end up with any accidental infinite loops. It's actually pretty simple for us to make the language Turing-complete — we'd just need to allow recursive functions.

It'd be great to jump on a call to discuss your use case more! You can email me at miraan at hypertune.com or click the book demo link on the home page.

Wow had no idea you could narrow down React performance issues with just DevTools. Will need to do this soon as the app I'm working on is already lagging in certain places. How many of your performance issues would have just been avoided by using another framework e.g. SolidJS?

Yes, agree that visualizing algorithms with nice animations would help people understand them and be able to apply them!

Would definitely help people studying CS or preparing for interviews!