402 karma · joined October 3, 2018
I'm not sure where modern smartwatches stand in terms of accurate readings but if I remember correctly it is still a minefield of inaccuracies. A watch for 50 dollars will _probably_ not do as well at reading your vitals as a watch for 200-500 dollars. Given Whoop markets itself as backed by science and seems to take the lead in studies on accurate heart rate readings[1].
Couple the above with great marketing and a decent kit of software and you have a difficult champion to dethrone. Hardware is expensive, marketing is difficult, a good app is hard to make, and putting together all three at once _while_ fighting a niche market is a struggle!
While 30/month can be difficult to swallow for someone that runs or swims as a casual hobby, someone that already pays hundreds a month for equipment, coaching, gym memberships, can have an easier time justifying it.
I would argue that at a given size, scale, and growth you would find yourself looping back to the "original pillars".
The example of Neartail[1] competing with Shopify is a prime example of this. Shopify has a large market cap, shareholders demanding profits, a large quantity of paying customers. Neartail has none of these, it may have paying customers and it may have some potential in the future but it is currently all within the sphere of control of a few individuals.
Obviously a lot of what I'm saying is self-inflicted, you don't _have_ to grow endlessly but if you _do_ you need many decision makers and domain knowledge simply starts to reach limits for individuals (even when using AI).
It's an obvious hyperbole but I think it stands to show that, in a similiar fashion, there is a reader (and by some aggregation readers plural) for everything you might think of writing.
How to get started with web development in 2025? What is ray-casting? How to emulate a piece of hardware in <language>? What I had for dinner tonight!
It may not be that everything is viral or a hit but you should find that most of the content you right will resonate with _someone_ and potentially help multiple _someones_.
Sometimes being satisfied with that 10-100 readers is all there is to it.
data:text/html,<body contenteditable style="line-height:1.5;font-size:22px;max-width:75ch">type here...
I use this _all_ the time for very quick note taking and writing that will later be copied elsewhere, think one to three sentences and then offload.On topic though, I wholeheartedly agree that this valuation seems rather... unrealistic. I do think "hype" is how we currently handle a lot of valuations, for the worse in my opinion.
Some of the codebases had tests, a good chunk of which could (and were) eliminated simply by using TSC as part of the build process. I think allowing the compiler and tooling like prettier to make choices for you leaves more space for you to think about the problem, not the myriad of problems _around_ it.
[1]: https://laravel.com/
[2]: https://livewire.laravel.com/
[3]: https://fluxui.dev/
If someone has more resources on the topic, I'd be very interested. There are many applications where sacrificing data freshness for a considerable uptick in performance is alluring.
[1]: https://www.slideshare.net/slideshow/the-apache-spark-file-f...
This kind of attitude reeks of the "you're using it wrong!" of the Linux world. Are you really telling me you are getting enough RSS feed requests to put a dent on your tech stack? Is your bandwidth overhead suffering that much (are you not caching?)? Make it painless and let's be thankful it isn't all web scrapers masquerading as users.
Mind-boggling problem to be angry about.
[1]: https://www.sciencedirect.com/science/article/pii/S135041772...
This just proves (to me) for the umpteenth time that AI can help us with our work immensely but company after company refuses to hire people who work well with it and instead focus on trying to employ it in a myriad of different unsuitable functions.