drittich

https://prql-lang.org/ might be an answer for this. As a cross-database pipelined language, it would allow RAG to be intermixed with the query, and the syntax may(?) be more reliable to generate

You mean the children grow up loving the GPT more than their parents?

I think this is just in the short-term. In the long term GPTs will retain our personality while making the message more understandable - which I think is the most important thing. Although McLuhan would disagree. Benefits, though, might include AI making cross-cultural translation so you can converse with someone with a different language and very different experiences and still understand each other. I think that's good? Maybe?

That article makes a helpful distinction, thanks!

Thanks, I probably won't bother then - I have no ability with plants and I don't think that's likely to change. It was just my stomach that made me write that :)

They don't seem that hard to grow, i.e., partial sun seems OK. I might give it a shot...

Mangosteen is great! In Ontario I can find it readily at Asian grocery stores like T&T or Nations.

Another one I would love to see on more grocery shelves is cardoon.

https://www.thespruceeats.com/how-to-clean-cardoons-2394986

This is very upsetting. Just for clarification, is the "I" in your comment referring to you or Lee Sun-kyun?

I am troubled by the word belief, not just in the title, but in the comments here. Unit tests should not be doctrine, there is a time and a place. And, I feel that more often than not they are warranted.

We can argue about what granularity they should be, talk about functional programming, debate whether they should hit the database or not, but IMO all of those things miss the point. For me, in order of priority, unit tests provide the following benefits:

1) Make me write better, more decoupled code

2) Serve as documentation as to the intent of the code, and provide some expected use cases

3) Validate the code works as expected, (especially when "refactoring", which is basically how I write all my code even from the start)

4) Help you when deleting code by exposing unexpected dependencies

You can argue against all of those points, and I often will, myself. It depends on the scale, importance, and lifetime of the project as to whether I will write unit tests. But, as soon as I think someone else will work on the code, I will almost always provide unit tests. In that scenario, they:

- Provide a way to quickly validate setup and installation was correct and the application functions

- Signal that the code was "curated" in some way. Someone cared enough to setup the test environment and write some tests, and that gives me a certain comfort in proceeding to work on the code.

- Provide a gateway into understanding why the application exists, and what some of the implementation details are.

So, thinking about the advantages I've outlined above, for me it would be very hard to say I don't "believe" in unit tests. I just don't always use them.

The proper way would be a bookmarklet that renders a list of bookmarklets.

I built dozens of web sites using JScript server-side...

That's really interesting. To me, an idea like that alone would have been enough to make Claude Shannon memorable.

This sounds a lot like software developers, except replace decade with 6 months.

“Any sufficiently advanced technology is indistinguishable from magic”

And if you just have tens of thousands, straight up SQL can work pretty well, too.

Note you can also just use pretty much any SQL db, which is not fast but can be good enough. I typically get my results in about 250 ms. If your app is already using SQL it's nice to not introduce a new dependency.

Oh, that's cool! Will definitely give that a try, thanks.

I do think it's pretty consistent in extraction times. I probably just need to clean it :)

I have a Mazzer Mini grinder that's pretty old and I suspect it is the weak link in the chain (paired with Rocket espresso machine). Is there an easy way to tell if the grinder is doing its job well, e.g., some reliable way to examine the grain size?

Does this mean we might theoretically find rock in asteroids that contains evidence of life from planets that existed before earth did? Fossils, even?

It's surprising to me that you describe creativity as a simple thing. How were you defining and measuring it?

And a cant-even library.

Pretty much correct, IMO. Really, the first build (and usually the only one, unfortunately) IS the process of estimating. I try to POC as much as possible to make sure I know where the landmines are. Just this week, I blew by one of my own recent estimates because I assumed I could pretty easily determine the output column names and data types for any arbitrary SQL Server stored procedure using a SQL query. Many implementation hours and attempts later, I realized my folly, and I am not new to SQL.

I'm still left wondering whether the code is correct, in that an employee that is paid weekly does not require passing probation to get paid. Is that the correct logic, or is it the (very common) error of forgetting an extra set of parentheses when using OR?

Given that there would probably be more complexity in the real code I would create separate functions expressing the rules for each employee type.

After using for a day or so, some thoughts:

* Very happy with the output. This is my favourite code search now.

* Can you update the cache GUID in the URL before the answer is fully rendered? Rendering can take a long time to finish and I often have what I need before it's done and want to share.

* The copy to clipboard button often fails to register clicks. I find myself clicking all over it and long clicking to try to get it to register.

* It's not clear to me what constitutes a "session". It would be nice to be able to both define a new session whenever I want, and to share an entire session with one URL.

* It would be nice to be able to name sessions.

* On my monitor the top right corner is empty (above SOURCES), and thus the content in the scrollable question textarea is forced to scroll more than it should if it extended full width.

* Under SOURCES, one of the URLS had a green plus sign at the end of it. It's not clear what that means.

* A thought: A lot of my questions are for the same domain (language/framework/hosting context, etc.). It would be nice to be able to save domain information and be able to select it, so it would automatically get added to each question instead of having to type it out over and over. Maybe this gets tied to a session.

Thanks for a great product!

>the URL transforms into a unique permalink once the answer finishes generating.

This is non-obvious, but great! It would be nice to have a share button to copy the URL. The querystring param cache= makes me think the permalink may not be forever. Do you plan to keep the cache indefinitely?

Your response implies that the comment is about the similarity of how dead someone is in each circumstance and then you take a position apparently opposite to the comment's author. To me, it stretches credulity that the comment was about that - my reading of it is that there are serious & interesting ethical/legal/existential questions at play with AI-induced death that we need to be grappling with. In this way, they are not the "same". Legally, who is to blame? How do we define "intent"? Are we OK with this becoming more normal? Putting lifespan issues aside, would you rather die of "natural causes", or because an AI device killed you?

>If I were writing software like you describe I’d want an explicitly zone-agnostic date(time) to represent it.

I would love to see this as a data type (CalendarDate) baked into languages & databases which would prevent you from applying timezone conversions to it.

I think the Clooney film is excellent, and can be enjoyed without knowing anything about Lem's book. And it just might be enough to make you want to dig in to the source material.