_cfl0

Joined 3 years ago

Karma

Submissions

Member since

Feb 17

View on Hacker News

Recent submissions

Comment · 3 years ago

I built haystack - natural language search engine for workplace technical knowledge.

I've been a software engineer for a few years now,

A few weeks ago I was scrolling through confluence pages trying to find ssh connection details to our jenkins second integration machine for 40 minutes straight, later I discovered my co-worker slack'ed me the ssh connection string *two months ago*.

A week later I started working on haystack - a search engine for workplace apps.. It enables you to search slack, confluence, jira, teams, sharepoint, github, and email in one place.

It supports natural language queries so a query like: "how to connect to integ2 machine?" yields:

  ssh -i private.pem [email protected]

Privacy?

haystack is self hosted and stores user data locally, it has a completely client-side version, and a a self-hosted docker container version - only you have access to internal docs, I didn't want to deal with security compliance headaches caused from storing user data in the cloud + I don’t want your internal docs/messages.

Rolled it out to my co-workers a week ago and they thought it's a hit, so I'm planning on releasing it publicly on March 2023.

*Early access*

More technical details are available on github, code released on March 23’:

<https://github.com/haystackoss/haystack>

If you want to try it out before March 2023 - Available here <https://haystack.it>

Comment · 4 years ago

Sure, read docs.nabaz.io (CI solution w/ storage over mongodb)

Comment · 4 years ago

You aren't interrupted, you choose when to alt+tab to see your test results.

Comment · 4 years ago

Main difference is that crystalball still runs all the tests, but runs the recently failed ones first.

Nabaz selects a small subset of affected tests, reducing CPU usage, and more importantly improving speed drastically!

Comment · 4 years ago

10.

Comment · 4 years ago

Nx is even clealry different. It isn’t run on every code change, but on commits.

You can’t use it live, And also the analysis granularity is just way too wide compared to this.

Comment · 4 years ago

Right.. Because out of a 100 tests it will run close to that number. when you change code most of the time only a handful of tests or less need to run.

Comment · 4 years ago

Had what since forever? Does jest analyze the changes you make and compare them to code coverage? (hint: no)

The key innovation piece here is the speed that the extreme selectively enables you.