I'm surprised nobody thought of it before me but basically the LLM's are trained on the internet and I just had it spit back out everything.

It's running in parallel so I can validate it, which of course I'm using LLM's to do that.

Once it's ready I will put it on the market, but get this, my internet will be cheaper than the current internet. I'll probably just make it one cheaper, like if the current internet costs, for example, 7, I'll make my internet cost 6.

I did some consulting work there a long time ago building some software to manage inventory in one of their departments.

When we asked about their goals, like improve margins, they said "absolutely not, we will not increase beyond 14%". When we asked why, they said "the minute our customers think we are increasing margins, we will lose members, and membership is the goal."

"Tesla Cold Fusion (TM) will be powering all of our vehicles by 2031."

It would be nice to get to the feature level, meaning across files/classes/functions etc.

I was thinking any breakthrough in hardware (e.g. spintronics etc.), even if just partially effective, means all of this hardware would need to be replaced.

I bought my first new car in 1989, a Camaro with T-Tops and it cost me, $12,250.

> Cause and Effect: If Neuron A fires just a few milliseconds before Neuron B, the brain assumes A caused B. The synapse between them gets stronger.

A recent study from Stanford found that it's more complex than this rule, some synapses followed it, some did the opposite, etc.

He told me years ago that the majority in Iran were not aligned with the new regime, it was a minority of the population that were.

I always use the calculator.

But, because the numbers that get returned aren't always the right numbers, I try to approximate the answer in my head or with paper and pencil to kind of make sure it's in the ball park.

Also, sometimes it returns digits that don't actually exist, and it's pretty insistent that the digit is correct. If I catch it early I just re-run the equation but there is a special button where I can tell it that it used a digit that does not actually exist.

Sometimes, for complex ones, it tells me it's trying to calculate and provides some details about how it's going about it and keeps going and going and going, for those ones I just reboot the calculator.

It was a pretty healthy business, not just for the copy protection breaking but also the general tools software.

Funny story:

I was at their offices working on a project when they were getting ready to ship out the new version. Their warehouse was connected to the office building and they were producing all of the final copies and loading them on trucks to get sent to the distributors.

In the morning they gave the all clear for the first wave of trucks to leave, then about 4 hours later someone found a bug and they had to call all of the trucks back to the warehouse, unload, re-create new clean product etc.

They did this about 3 times before that version finally made it to the distributors.

It was actually a well designed and functional system, just too many bugs.

The article seems about 5 to 10 years late.

https://www.science.org/doi/10.1126/science.1243472

Is that true?

I know that cells in the brain have significant variability in DNA, but not really aware of what non-neuronal and non-brain cells in general typically have.

https://dl.acm.org/doi/epdf/10.1145/800195.805951

Quote:

"Unit test:

testing, outside of thesystem, of a part of the system thatmay have less than a complete function.

Component test:

testing, inside of the system, of parts that have been successfully unit tested.

Integration test: testing of new components to ensure that the system is growing functionally; in addition, retesting of successive system builds to ensure that they do not cause re-gression in the capabilities of the system.

Regression test: testing of the system for unpredictable system failure.

Scaffolding:

coding that replaces not - yet - completed functions..."

I was taught in the 80's about this by a woman that had worked at some company that was more formal about software dev than we were at the small company I worked for.