Urgent.News

What's breaking now, across thousands of outlets.

Tech

Building a Product Is Only Half the Job. Getting It Seen Is a Different Problem.

I created a simple experiment around this one question: what would happen if a product’s visibility was made 100% transparent? This is what I do, I spend a lot of my time writing software. AI: systems of questionable competence LLMs: random applications. All the way from full-stack products. Of course all of these can (and will) be disproved by a simple intuitive experiment. It is usually the…

Building a product is only half the job; getting it seen is a different problem. This reporter spent time writing software and experimented with product visibility. The process can be straightforward, but getting people to find your product is challenging. There are various ways to sell a product, such as building an audience, posting on social media, submitting to communities, optimizing for SEO, running ads, and getting picked up by bigger audiences.

However, none of these inherently guarantee success. The reporter wonders what factors make a product stand out and become popular, as it can vary from audience size to timing. The reporter also delves into the complexity of contemporary recommendation systems, which involve candidate retrieval, filtering, scoring, ranking, reranking, and visibility decisions.

The reporter then introduces an experiment called Get-Seen, where product rank is determined by the amount paid. This simple system eliminates factors like votes, followers, and ranking algorithms, focusing solely on the payment amount. The goal is to make the ranking mechanism transparent and easily understandable, with the highest cumulative amount holding the top spot.

The reporter believes that by making the rules explicit, users can instantly see why one product ranks above another without any guessing or hidden factors.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

48-Hour Field Notes: I Parked the Prompt Until the Runtime Card Existed

I had a tiny Python job that passed in my editor and then died on a clean remote interpreter. My hands went straight back to the chat box, because the model had drafted the snippet and I wanted a new…

  • 48-hour investigation to resolve Python issue
  • Avoided sensitive details in remote interpreter
  • Recorded key information for cross-comparison

Four executable counterexamples from a component review repository

Disclosure: this article was generated by an AI agent from code it extracted, inspected and tested. AI agents also reviewed the extraction and reproduced the defect described below.

  • Voice history buffer in Kotlin may exclude crucial user input
  • Java rolling buffer vulnerability can delete segments by modifying metadata
  • Python checker misses critical instruction in transcription example

How to Fix PSR-4 Autoloading Issues in Laravel

When working on a Laravel project, you may encounter warnings when running composer dump-autoload . These warnings often indicate that your model or controller filenames do not match their namespaces…

How I Made PdfWord Work Fully Offline as a PWA

Series: Building PdfWord — a free, no-backend PDF tools site (Part 10) Most "free PDF tools" die the moment your Wi-Fi does.

  • PdfWord designed as offline-capable from inception
  • Service worker precaches essential app shell, not all libraries
  • Network-first cache for HTML, cache-first for static assets

More from Saturday 10 October →