lbhdc

I have really liked fq for binary visualization.

It also gets used for more than just ticket lifecycles. They are doing a lot of data analysis, and project management stuff.

I don't think that means saas is dead. There is a strong preference to buy instead of building if there is something worth buying.

https://www.anthropic.com/careers/jobs

For example, if I am having a complex part machined, I probably need some electronics to drive that things. Having a supplier for electronic parts, circuit board printing, plastic molding for housing those electronics would be needed to finish the job.

On the home page when I search for something like `Southeast` it shows 0 shops, but if I actually select it I get 223. This was confusing and made me unsure of how many relevant hits I would find.

It would be really nice if you could search in smaller geographic areas. State boundaries would be really nice to start. As you continue having city / intra-state regions would also be huge for the cases where you want to go in person to these places.

In the space I was in (ads) users were highly mistrustful of the data. They felt everything was kind of fuzzy (eg how well are you measuring unique users and their actions).

They would end up using multiple vendors (and we would have to spend a lot of time comparing and contrasting results). They really really want "apples to apples" comparisons.

At the end of the day they were trying to answer, does what I am spending my money on give me the results the business needs? To your point there is a lot of nuanced data, but their bosses definitely only cared about the top line, did it move the needle.

I think it often comes down to who is responsible for making decisions with that data. If a product or business person is the one driving a feature, and looking for adoption, the engineers likely aren't going to be invested in building out sophisticated metrics. They get the metrics they are responsible for from their cloud provider (resource use/latency/scale).

I think that problem is compounded by the perception that these integrations are going to tank your products perf (may hurt the metrics engineers care about).

I think all of those dynamics change in really big companies with thousands of engineers. Then you can often end up in a situation where engineers are now required to maximize product metrics, and need visibility into their small slice of the pie.

So, I think its largely incentive, which is why I see all of the metrics vendors targeting product and sales people in small/mid sized companies.

The image itself isn't the same image that the app gets deployed in, but is a portable dev environment with everything needed to build and run my apps baked in.

This comes with some nice side effects like being able to instantly spin up clean work environments on my laptop, someone elses, or a remote vm.

Isn't Omarchy just config files for a bunch of existing, stable programs? Why wait?

Why would I want to host my site on Nostr? What does it do better than the competition?

As a side note, your demo isn't viewable without the extension. Trusting a new browser extension has a high level of friction. It would be nice if your site gave some hint of why a user might want to jump through those hoops.

Looking at the official repos, it looks like much of it hasn't been worked on in years.

What is the status of the project? Is there a fork that has taken over development, or is it a mostly dead curiosity?