vallode

They are most likely referring to the overall size of the whole website including all generated HTML for posts, static content, styles etc.

Certain smartwatches offer a "pebble mode" feature like the Xiaomi band 9, you can get a keyring case for it and just attach it like that. I don't think it has automatic switching between exercise modes just tracking for steps etc.

A fan chiming in. I'm really happy someone someone is tackling this and it's looking good. One thing: can we get a demo instance just for initial snooping? A screenshot or two is fine but to get a feel for features it would be nice to have something (even heavily limited) we can just interact with?

I'm not sure how I feel about the take on "disappearing pillars". I think that knowledge and expertise in the different "pillars" the author describes has become easier to access, reducing the moat around the individual pillars and allowing greater overlap between professions. So while you might not need a "sales team", you do need "sales knowledge". Cloud solutions are amazing until they are not and you need "infra knowledge" to understand where you are going wrong and to evaluate potential solutions.

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).

The market for TODO list apps is 1 for every person in the world, everyone has a slightly different subjectivity and therefore has a slightly different optimal experience when it comes to TODO lists. Subjectivity is formed over time and through the course of events, therefore the market for TODO list apps is 1 for every person in the world for a given timeframe.

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.

I've had good success teaching markdown to a fair few non-techie people. At the end of the day it better serves as a machine-readable middleground between a user-facing WYSIWYG (markdown-powered) editor and the server responding to it.

Both the work done here and the quality of explanation, as well as the thoughtful challenges to the reader, are top notch. Thank you for sharing.

The difference here might be the rather huge gap between putting together a solid "blog post" and a solid "paper" on a subject. I agree these "types" of essays are difficult to challenge and given the sheer length of this post, it is also not accessible to _discuss_. I understand the desire to write about a topic extensively and how intimidating it might be to do so in a "scientific" way, this seems to be the middle ground. Maybe it's a seed for the author, or someone else, to develop further.

I believe the bounty is closed but they haven't announced the winner(s).

The abstract mentions the patients cholesterol level is 1000mg/dL which is at least 4 times more than the "highly dangerous" bracket. Evidence seems to show that xanthelasma (the nodules seen on this person) can have a link to a higher risk of atherosclerosis, which is linked to high cholesterol in the first place. This will not be "asymptomatic" for ever.

For what it's worth, I have a bookmarklet with these contents:

  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.

Do I understand correctly you chat wıth Claude as a form of social relief or are you talking about drinking beer and chatting with it about work/ideation etc. Either way, just curious!

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.

I could not disagree more, but I am obviously open to it being a personal preference. I've spent months updating JavaScript codebases that are between 3 and 5 years old, most of them written with vanilla JavaScript. A _few_ of them were written with TypeScript at least partially and those files were the least mentally taxing to upgrade.

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.