skysight-inc/HackerNews huggingface dataset:
Most don't train/fine-tune on your data, they stick it into a vector database and perform similarity search. The method is called Retrieval Augmented Generation.

This is the high level algorithm:

1) Sentence segmentation/text splitting. The data is indexed in disparate chunks so the user can look up the specific information they want.

2) The split sentences/text chunks are ran through a cheap LLM/specialized model, usually not state of the art but powerful/big enough to separate and associate the individual concepts in the latent space. Current models being davinci-003 and SentenceTransformers. The embeddings generation is usually the first step in an NLP deep learning model, so it's relatively cheap/lightweight. Essentially you take the first layer or two of a neural network and multiply the weight matrix against the input. This is the simplest type of embedding (see the original word2vec) algorithm. Transformer embeddings are a bit different but functionally they operate similarly.

3) The generated embedding vectors represent the input data in latent space, i.e. abstract representations. The most famous sentence in modern nature language processing being possibly King - Man + Woman = Queen.

4) The vector embeddings are stored somewhere, usually a database, but you can dump them in an excel file too if you want. You want to put it in a dictionary structure, where individual embedding -> original sentence chunk.

5) The user creates a query which is passed to the embeddings generator model and another vector embedding is generated (the query can be anything, so long it's natural language based since that's what the embeddings generator LLM was trained on). This query can also be created by an upstream LLM too, the specifics do not matter so long the sentence is mostly well-formed.

6) We obtain an answer by performing a similarity search (nearest neighbor in the vector latent space, using cosine/Euclidean distance/whatever metric). There are many approaches to do this, you can use kNN, you can use basic linear algebra and do n comparisons against all other vectors, or you can use a graph data structure (the currently preferred method for the fastest libraries).

7) You find the closest vector and the text chunk/sentences it represents and you take these sentences and the original query (the raw natural language text, not the generated embedding) and feed everything into a new LLM prompt. The LLM in this step is usually a state of the art chat model like GPT-4 or Llama 2, not the cheap model used for indexing and generating vectors. You pass a prompt like this:

Answer the following query: {original query text} with the given context: {text chunks, sentences}.

And that's it. Retrieval augmented generation has a fancy name and langchain's code feels opaque as hell like it was written by enterprise java people but the underlying algorithm is less than 30 lines of code with the standard ML and linear algebra libraries.
> My intuition let's me know that you can not get below O(n log n) (Lower limit for comparison based ordering)

That intuition should point at O(log n), shouldn't it?

In any case, it totally depends how your data is stored and how/what you want to look up.

If you already have some kind of id of your node in the graph you want to look up, you can get O(1) lookup and still call it a graph database. If you have to traverse the graph, then it depends on the structure of the graph and where your entry point is, etc.

I'm rather skeptical of graph databases. Whatever they can do, you can do with a relation database and datalog. (Think of datalog as SQL plus recursion, perhaps.) See https://en.wikipedia.org/wiki/Datalog
Note that by default this data stored by apps in iCloud is not end to end encrypted and is readable at any time by Apple and by extension FBI/DHS without a warrant or probable cause.
> Haggle over precise wordings of communications, minutes, resolutions.

> Advocate “caution.” Be “reasonable” and urge your fellow-conferees to be “reasonable” and avoid haste which might result in embarrassments or difficulties later on.

I do both of these things.

Do I want to destroy my organisation? No. I want to prevent miscommunication and haste from destroying it.

I dislike the popularity of this list for this reason.
Ones a stop start city/longhaul measure. The other is a different set of assumptions. ICE cars improve on long drive constant speed and EV do relatively better on stop start because of the from zero torque on electric motors.
That is very good and potentially precious,

but would it not have been better then

'A history_ of Neural Nets in Astronomy [and in general]'

?

Useful section of the title, informative important addendum for the public?

Otherwise you transform the original beyond its sense.

This is why we are asked not to editorialize in the guidelines.
> The world has non-text files that require version control support

Which is fine, but saying that git is rubbish because it doesn't handle binary files as you want it to is a bad usecase.

How version control would handle diffs between PDFs is not the same as photos, which is not the same as video. They have to be content aware for these sorts of things.
What are your thoughts about AI generated 3D assets that many, now startups, promise to sell to indie developers?

For me, it sounds like city models such as cars and buildings will be one of the easiest models to generate (from what I have seen in papers).

As an indie dev myself I'm counting on that I will be able to buy most 3D content for a fraction of time/cost in a couple of years. And I plan my development around this and ignore art assets for now.
I have experimented with them a bit. I've used GUD a bit with PDB, GDB, and LLDB, and vimspector with GDB, but Intellij and Visual Studio offer a lot more functionality, are far better documented, much more user friendly, and far less brittle. I really think it makes sense to just use programs that are more optimal for debugging.

There are a few exceptions: Common Lisp has a best-in-class debugger in Emacs thanks to João Távora, and same for Racket thanks to Greg Hendershott. I wish I could say GNU guile has a good debugging support in GNU emacs, but that is sadly not the case.
The most effective methodology is to implement one of the loosely agile based methodologies like SAFe Agile. Then hire consultants, none of whom have ever actually managed a software team, to make sure everyone follows the process down to the last letter. This decreases efficiency to the point that the organisation is no long able to do productive work, there is no ROI and the staff are all burned out from spending 20 hours a week in zoom meetings and filling in JIRA tickets.
That was a lovely comment to read - thanks for that. I've been trying to get into learning music lately, as a change from programming. I'd love to be as familiar with an instrument to be able to work as instinctively as you describe.
The case for waiting to ship your AI product
It is true that the reasons why phototrophy does not work in a too strong light are much more complex than a heat effect, but also the theory proposed in the paper quoted at your link is too simplistic to be convincing.

The primary pigment use to capture light in all phototrophic living beings which produce elemental oxygen is chlorophyll a, which is blue-green not green.

In the land plants, the blue-green color is masked by the more abundant green chlorophyll b, which is an accessory pigment that transfers the captured energy to chlorophyll a.

So if it is assumed that the color of the pigments has influence upon the regulation of the energy flux (as claimed in that paper) and it is not due to historical accidents, then any such theory must explain why when oxygenic photosynthesis has evolved first in Cyanobacteria, most likely in a terrestrial freshwater environment or in intertidal zones, the optimal color was blue-green, not green as claimed in that paper, then when the Cyanobacteria spread in the oceans in environments with lower light levels (where the luminous flux has even greater fluctuations that require regulation, according to the hypothesis from that paper) the algae have evolved to have accessory pigments that absorb most of the available light, and then, when going back to the continents and exposed to strong light, they have replaced the more efficient accessory pigments with a green pigment, which produces a lower amount of photoelectrons at a given illumination.

The latter fact is easy to understand as just a means to limit the fraction of captured energy versus total energy (in order to not produce more redox agents than can be used by the chemical syntheses that are limited in speed by other factors), but it does not make sense as a means to supposedly diminish the effect of light fluctuations, because these are much smaller in a more intense light flux, with much more photons per second.
Behold: https://git-scm.com/docs/git-daemon
You do need an AppleID but that doesn’t mean you have to turn on iCloud. I have a test iPad I erase once a week, and the last thing I can’t automate is going to the App Store app and signing in there rather than during Setup Assistant or from the Settings app. You’ll still get a prompt to go “finish signing in” or some such, but no document sync, no iMessage, no Photos, just access to apps.
I'm looking for something post-auto, not pre-auto. I'll definitely give it a look though.
It took me too long to realize this wasn’t real. Git does have some awkward commands I’m not even surprised anymore.
What you're saying makes no sense. Humans don't have "races". So there's nothing to compare in the first place.
Whilst reading The Man Behind the Microchip: Robert Noyce and the Invention of Silicon Valley, I was struck by the casual glassblowing. For some reason I assumed the machine-shop/engineer division of labor, but no. William Shockley was a glassblower. Gordon Moore was a glassblower. I wanna be a glassblower
> Python's laxness doesn't make it easy to define strict APIs or know when you're breaking them.

That is poppycock. Every time you make any change, you have to ask the questions:

1. Can the application use the API to tell the difference? (As in, tell whether the proposed change has been implemented or not?) (If this is not directly used by the API, what intermediate layers use this, which are connected to what APIs, and to which of those does the change matter, and how?)

2. Could an application so affected by the difference plausibly exist today, and would that application be doing something that is documented as valid? (Or that is not documented as valid only by neglect, and that should be valid the way it de facto works now?)

2. b) Do we have a test case for this (either way)?

This is not rocket science. Safe, high-level languages mostly make it easier, not harder, whether they are dynamic or not. You can do this. You pretty much have to do this. How can you not know if you're breaking an API; it's ridiculous.

Imagine if Intel said, oh, assembly language's laxness makes it hard for us to know when we're breaking the instruction set. Sorry your old Core 2 Duo stuff doesn't run on Core i9.
To me, --small gives much more information. I immediately assume that it means something is smaller than the default, memory makes immediate sense. --smol on the other hand could be an acronym or a technical word I just don't know, the likelihood of random internet slang actually being one of the first interpretations seems low for most engineers.

Let's turn this around. If the flag was called --cutesy-wootesy-fartsy, would you still argue it's approximately the same amount of information? If not, can you explicitly explain why not?
> Run 'git instaweb' for example and it will spin up a local CGI server and perl CGI script to give a very simple web UI:

~ $ git instaweb
fatal: git was built without support for git-instaweb (NO_PERL=YesPlease).
In fairness, the rate of change of any type of tool slows down over time as the problem domain becomes well understood.

It's like the Joel on Software article (which annoyingly I can't find at the moment) about how software is always pretty much done by about version 4. His example was office software, especially Excel, and sure enough if you loaded Excel 4 today you'd see it does fundamentally all the main things.

I suspect we'll see git last at least double the length of time as those other VCS tools.
To be fair, if you've seen a senior team member write a badly worded Jira ticket containing a large amount of possibly unnecessary
work, then foist it upon a junior (Or just describe what the want in a call and let the junior write it) because they knew it wouldn't stand up to scrutiny in Backlog Refinement, you would be a bit more in favour of that rule.
One question - in your case, how long does it take for you to start noticing its (good or bad) effect?

I've suffered from Longcovid since last year, and this seems to be something safe that I can try, with a possibility of positive result.
There’s only so many background / non-interactive tasks you need to run, and especially that you need to run now: with more Es you increase the parallelism but if everything goes idle quickly you’ve kinda wasted the silicon.

P cores are more relevant for interactive work which the user is waiting on, hence he sacrifice if efficiency.
That sounds great to me
This just reads like a basic description of every large organization out there with humans in them.
It isnt very hard. The easy (and probably best alt unless you are big enough to justify training your own LLM everytime your documents change) is to use vector search to find the most relevant parts of your documents (I use openai embeeder and pgvector for postgres) and then you feed that text to an LLM (could be GTP4 or Llama) and asks it to answer the question using the text you provide.
When self-hosting it it's possible use merkle tree to ensure the documents integrity (similar to how git works with its commit hashes).
So to forge one document it will require to change all document hashes after the disputed document making it impossible to cheat by the organization that is self-hosting it. This will be added into the project soon.

https://en.wikipedia.org/wiki/Merkle_tree

Alternatively I'm thinking about adding a third party AWS QLDB integration - QLDB allows to maintain an immutable, cryptographically verifiable log of data changes.
> Black vs white hat is "did you break this and then use it to <do something illegal>.

That is a very narrow interpretation of "black hat". I think mainstream take is that black hat includes many legal but ethically dubious actions. Maybe you would call it "grey hat", I don't know. But publishing vulnerability without a responsible disclosure can be considered unethical.

> But responsible vs irresponsible disclosure is not a question of "should this be disclosed at all?", which the security community as whole seems to have determined that the answer is "yes".

Yes, I don't know if you misread but by 'responsible disclosure' I meant 'tell ejmr about this before publishing'.

> The only option

No. If they were informed about this issue, after changing the schema EJMR could take down all preexisting posts made with the old schema and request public archives to remove them (and reindex new ones). It's not foolproof because many posts may happen to be archived independently but it would be something. And of course notify users.
Yeah that’s a feature.

Or instead of only half you can bring it whole with WSL2.
Thanks, please feel free to open an issue with your suggestion to improve the tool at https://github.com/docusealco/docuseal/issues
One could accomplish a part of your vision, today, by splitting commits into smaller commits. Then you have the relation between hunks of changes and text in the commit message on a smaller level. Then you can use branches with a non-trivial commit message in the merge commit to document the whole set of commits.

As far as I know changes to the Linux kernel are usally submitted as a series of patches, i.e. a sequence of commits. I.e. a branch, although it is usually not represented as git branch while submitting.
As if the only possible reward is money?
That's a good idea! will definitely add this feature to the project
And Chief Ethical AI back into the Sales Department.
So it looks like you're ready for a change ... What's next on the horizon?
Plus you can be free of all the preservatives.

This is the speech of a scaremonger: You might not be trying to scare folks, but you've certainly bought into it. Preservatives cut down on food waste and are an overall good for society. More folks would starve without these and more folks would wind up with foodborne illnesses.

I'll mention that salt and sugar are preservatives, we've just found better methods now. Are all of them good? Nope, but food preservation was never perfect. That doesn't make it worse now.
I don't believe there is a strong difference between engineering and management when it comes to an operation like this. I'd say there is a dependency on the two?

If America doesn't have the management capabilities, experience and maturity to get a plant going, it doesn't matter about the tech or the engineers, it's not going to workout. This includes having managers of a certain caliber which a large firm would trust with hundreds of millions of dollars to spend on getting factories running.

I completely understand what you mean by the way and sympathize with your view.

I've spent considerable amount of time in Japan and other parts of Asia for business, they have plenty of people with plant management experience who would be able to organize an operation like this. Japan, for example, has off shored a lot, but not everything. Not by a long shot.
Yep, support for SMS verification will be added eventually with ability to bring own Twilio credentials when self-hosting it.
Currently the documents are signed with PKCS#1 signature, signed documents can be verified at https://demo.docuseal.co/settings/esign (to ensure that they were produced by the tool and not altered/forged by some third party). Additionally I'm planning to add a merkle-based log of documents to ensure that documents were not altered by the party that is self-hosting the tool.
This instagram account makes some really neat stuff leaning into temporal inconsistencies

https://www.instagram.com/never_ever_never_land/
This is nice ! I like that you have kept the polyglot world in mind.

You should consider adding:
1) configurability in terms of name ( a templating engine might help )
2) generate functional build files
A GPT version of parser adventures would be awesome.
I don't fundamentally disagree with you, I just understand why, as a society we may choose a different thing.

One of the reasons my father died of cancer quickly is that he was convinced by a chiropractor/osteopath that he had trouble with his back which could be cured with manipulation.

He was not an idiot, but sick people will make bad choices.

The abstract world of "either I die or I try this experimental treatment" is far more blurry, and there lies the problem, in my very humble opinion.
BitTorrent got past the need for trackers relatively quickly and hasn't needed them for quite a while now
> I never read the git log.

Imho, you are missing out on a great source of insight. When I want to understand some piece of code, I usually start navigating the git log from git blame.
Even just one-line commit messages that refer to a ticket can help understanding tremendously.
Even the output of git blame itself is helpful. You can see which lines changed together in which order. You see, which colleague to ask questions.
A “best books to read” list full of the author’s own books, except for the subjects he hasn’t written one for yet.
The doc states it panics, maybe that's process termination, but either way it doesn't let you do the thing.
A pointer with an opt-in, less convenient, safe dereference... is still a pointer. You could add a `value` observer to unique_ptr or shared_ptr.

The entire point of optional is that you can swap it in for a raw or unique pointer and it'll be cheaper because no allocation. That's not the use case for an option type.
I'm in Norway, and you are correct. Vegetable rennet is more common - well, at least Tine and Synnøve both use it for their cheese products.
I migrated a project from clearcase to git at my first company and for all the hate I have for clearcase even I agree there was little point in switching to something else before. We had a bit of svn on other part of the company but that was it.

VCS don’t change that fast. All the tools you list before the advent of DVCS actually have a lot in common. I think git will be there for some time.
And not vegetation either
It can definitely work in text; visually a short word like "the" at the end of a line and again at the start of the next can be missed, or the way you can mix up the spelling of words and still be comirhpebnesle so long as the start and end are correct, or ASCII art limited to real words and sentences; conceptually with rhetorical language painting emotional states without necessarily making a single claim, and I'm sure all of us here have at some point had the experience of someone getting indignant about something we neither wrote nor even intended to imply.

In audio: Yani/Laurel, barber-pole effect, use of instruments to fake voices.
> I think the sky walks double a structural braces between the two sides

From one of the image captions: "The skybridges located at floors 13, 24, 35, and 45 are steel trusses that are integral components in the tower's structural system"
I do not understand why you are voted down. Well known dutch author has a novel with this as one of the main themes: https://www.amazon.com/Grand-Hotel-Europa-Leonard-Pfeijffer/...

I know a number of people that had their view on tourism change after reading this. Myself included.
> Btw the amount of damage done to the cults of DIE, ESG, climate, globalism, and statism since last November has been multiple times greater, and done completely on Elon's dime.

From the inside of a developing echo chamber, it sounds like a massive change in popular sentiment.
Skaffold a k8s deployment CLI tool, written in Go, configured with YAML. vs Scaffolder, a CLI tool written in go configured with YAML. Where's the confusion?
You already mentioned it
Highly recommend the book 'The Body Keeps The Score', which touches on a lot of what you're bringing up here. Thanks for sharing that.

https://www.besselvanderkolk.com/resources/the-body-keeps-th...
Epistemology – how do we know what we think we know
All are priced $39.95 per book. One book would get 2 months of gpt4 access. I don't see many technical books taking off anymore except for may be as reference books. It's much easier to learn any language with a LLM than with books (obviously anecdotal).
I feel like I'm missing something given the comments here and on reddit. Do people really not see the text in the enlarged image? (Even enlarging extra) A few are a tad less clear but nothing is unreadable. I'd be extremely impressed if people were not able to read Rio, Istanbul, or London. Is there some collective unspoken agreement going on, am I just an outlier, or am I not uncommon and just no one is commenting?
I think it's ridiculous how much dev time and money is spent in pursuit of this thing that a good chunk of users do not care about or actively despise.
Russia pulls 500 million tons of asbestos out of a single open pit mine per year.

https://www.icij.org/investigations/dangers-dust/russia-worl....

I'd be willing to bet that mine isn't terribly automated, and they're pulling serious amounts out.

The mine you mention in Australia sounds cool. It's not on this top 10 list, which has many other, seemingly larger, open pit Mines in places like Russia, etc. That again, are likely not very automated.

https://www.mining-technology.com/features/feature-top-ten-d...

It really depends on what resources you are talking about and where in the world. I agree with you for things like copper. I don't at all agree with you for things like diamonds, gold, most gems, rare earth metals, titanium, asbestos, etc.