gleb

Please make the video.

Checklists are extremely hard. Writing them requires the skill of the programmer and direct response copywriter, and few people have both. Ensuring that people actually use the checklists is brutally difficult. And creating systems to improve the checklists as they are used is even harder. I suspect checklists being so hard is the reason they're so rarely used.

o3 pro seems to be good with meta-prompting. Meaning, when you ask it to create a prompt for you. In particular it seems to be more concise than o3 when doing this.

Has anybody else noticed this?

Despite the confusing copy here and on the landing page, the tool appears to be a commit message linter not a generator. Which seems useful. In fact, I was thinking of building something like that for internal use. Thank you for sharing.

I think semantic versioning actually predates distributions. It just was not called "semantic versioning." It was called Unix shared library versioning.

Where do you get such a large variety of mangoes?

Yes I did. I even later tried to tell it to fix this, and was not successful.

Tried it. Seemed quite impressive. Two issues:

- it consistently uses word two instead of to

- forcing Google OAuth as the only way to sign up is not a good idea. That prevented me from signing up.

I'll try to explain, not in the spirit of being argumentative, but with the hope of being useful.

The comment you replied to was not questioning the value of integrated cabling. It was pointing out that the product description on the site does not make sense.

"Cloud computer" sounds like a server you rent from AWS. It's kind of like calling Rust "cloud compiler."

If you choose to use words that your audience doesn't understand, or even worse understands to mean the opposite of what you want them to mean, it's a good idea to explain these words immediately using conventional words with conventional meaning. The comments by throw0101a did that.

The product seems really cool, but there is no way I would've understood what it was from the website.

I wouldn't be dismissive of people telling you that the product description can be improved. My opinion is that the description of the product in this thread will outperform your site 10 to 1.

What's up with that dramatically different shape of the "Ratio of male-to-female death rates across ages for the U.S., other countries" graph between say Chile/US and South Korea?

Elixir/Phoenix does this by default. It is a good default.

Any plans to offer SQL based sources, like Carto?

I should have been more clear and said "using SQL only without R or python". This is for internal BI use, not for product development.

What are the best options for maps driven by data from SQL? So far the best I found is carto.com

Similar idea in Elixir, where the library itself handles the interactive bits: https://github.com/assert-value/assert_value_elixir

Which is exactly how this (Berkson's paradox) is often visualized.

That's because conventional store apples are coated with wax and organic ones are not. Wax often has bad, usually bitter, taste and unpleasant texture.

Organic apples are not coated with wax, so they taste better, but will dry up faster.

Exactly. This was called “paid inclusion“ and was offered by Yahoo, for example.

Thanks. The sidebar did not load the first time. But worked the second time. This is on iPad Pro 12.9 inches.

Neat! How do I save in the filled out PDF??

Unlikely. You make more money by breaking a beef into multiple cuts for different customers than grinding the whole thing and selling burgers only.

Wikipedia disagrees with you: “On February 15, during the power crisis, the state's Public Utility Commission required ERCOT to set the price to the $9,000 maximum. The commission reasoned that the trading prices for energy (as low as $1,200) were inconsistent with the supply scarcity.”

Your site does not seem to preserve scroll state correctly after clicking back on iPhone. Go to the homepage, scroll down to repos, tap on a repo, tap back, find yourself at the top of the homepage.

Which illustrates a general problem with these kind of libraries - you need to put in a lot of effort to make them work as well as normal old old web applications. Is the performance improvement actually there, and is it worth the extra bugs and effort?

Not to pick on you either. E.g. GitHub had broken back button behavior with their turbolinks for the longest time.