Posted on 03/16/2025 6:24:41 PM PDT by SeekAndFind
Yeah yeah… I bet your car gets 40 rods to the hogs head too! ;)
Thanks! Will check it out.
a bunch of quirks, that cannot simply be deduced by using AI
Or God, for that matter. ;-D
It’s called “Job Security”. ;)
“I like you and I like your insightful posts, “
Thank you.
“so don’t take this personally.”
I am emotionally detached on this site. Several trolls can attest to that!
“That program is idiotic. “
GEMINI:
It’s unlikely your prime number program was “idiotic,” but it might have been inefficient or have room for improvement. Here’s a breakdown of common issues and how to address them:
Potential Inefficiencies and How to Improve:
* Naive Iteration:
* A basic approach checks divisibility by every number up to n-1. This is slow.
* Improvement: The provided code uses the square root optimization. Checking divisibility up to the square root of n is sufficient. If a number has a divisor greater than its square root, it must also have a divisor smaller than its square root.
* Checking Even Numbers:
* After 2, no other even number is prime. You might have been checking even numbers unnecessarily.
* Improvement: You can optimize by checking only odd numbers after 2.
* Lack of Pre-computed Primes:
* For finding many primes, storing previously found primes and only checking divisibility against them can be much faster.
* Improvement: Implement the Sieve of Eratosthenes, which efficiently finds all primes up to a given limit.
* Inefficient Sieve of Eratosthenes:
* Even the Sieve of Eratosthenes can be implemented poorly.
* Improvement: make sure that the outer loop of the sieve only iterates up to the square root of the upper bound.
* Premature Optimization:
* Sometimes, focusing on micro-optimizations can make the code harder to read and maintain without significant performance gains.
* Improvement: Prioritize clear, correct code first. Profile your code to identify actual bottlenecks before making complex optimizations.
* Incorrect Logic:
* The most “idiotic” error would be a fundamental logic flaw that causes the program to produce incorrect results.
* Improvement: Thoroughly test your code with various inputs, including edge cases.
Example of an Improved Approach (Sieve of Eratosthenes):
def sieve_of_eratosthenes(limit):
primes = [True] * (limit + 1)
primes[0] = primes[1] = False
for p in range(2, int(limit**0.5) + 1):
if primes[p]:
for i in range(p * p, limit + 1, p):
primes[i] = False
return [p for p in range(limit + 1) if primes[p]]
# Find and print the first 100 prime numbers
primes = sieve_of_eratosthenes(542) #542 is slightly higher than the 100th prime.
print(primes[0:100])
Key Improvements in the Sieve:
* It avoids repeated division checks.
* It efficiently marks multiples of primes as non-prime.
In summary, “idiotic” is a harsh word. Focus on understanding where your program could be improved and learn from the process. Prime number generation is a classic problem with many interesting optimization techniques.
I am fully aware that most of the processing at that “AI Islands” is for trading the models.
TRAINING!
I corrected that in the preview once and it changed it back again!
Then, good sir, you will also know that training an AI to be aware of and accommodate quirks is no small feat. Also, representing a business model that is non-trivial is a daunting task in an of itself, and finally, that there is a division of labor between training an AI and creating a good prompt. I've personally found that finding the balance is an art that must be practiced to be mastered.
BFL
“Then, good sir, you will also know that training an AI to be aware of and accommodate quirks is no small feat. “
Sometimes quirks should be eliminated, no accomodated.
“Also, representing a business model that is non-trivial is a daunting task in an of itself,”
Amen! Implementing an AI model may be a good time to improve the business model.
Absolutely....when possible. In our case, it doesn't lend itself well to simplification. We're communicating with 50 states and 2 territories, and one federal agency, and they all want their own format.... and we don't get to vote.
Of course! Yet sometimes code is so incredibly outdated (like your wife's COBOL code) that it doesn't make sense. Still, I certainly agree. Quirks are, to my eye, bugs by another name.
“(like your wife’s COBOL code)”
Not my ex’s. She was hired to update their system as needed and fix a few bugs by a guy that knew nothing about programming.
Neither did my ex.
She bought a book on COBOL and impressed him in the interview.
The Preferences menu is pretty flexible. I prefer speed in furlongs per fortnight. 😊
“I prefer speed in furlongs per fortnight.”
GEMINI
The use of “furlongs per fortnight” is generally not a serious preference, especially in the context of a modern video game like Fortnite. Instead, it’s primarily used as a humorous or satirical way to express speed. Here’s a breakdown of why:
* Obscurity and Antiquity:
* Both “furlong” and “fortnight” are relatively archaic units of measurement. A furlong is a unit of length primarily used in horse racing, and a fortnight is a unit of time meaning two weeks. Their use in everyday calculations is rare.
* This obscurity makes their combined use seem comically impractical.
* The “FFF” System:
* There’s a concept known as the “FFF system,” which uses furlongs, firkins (a unit of volume/mass), and fortnights as base units. This system is largely a humorous thought experiment, highlighting the absurdity of using such units in modern contexts.
* Engineering Humor:
* The phrase is sometimes used in engineering circles as a form of inside joke, often to satirize the use of inconsistent or overly complex units of measurement.
* Internet Culture:
* Like many things, the phrase has gained traction online as a meme, with people using it to express exaggerated or nonsensical speeds.
In essence, when someone uses “furlongs per fortnight,” they’re likely:
* Being intentionally humorous.
* Referencing the absurdity of archaic units.
* Participating in an internet meme.
It is highly unlikely that anyone seriously prefers to use that unit of measurement in regular calculations, especially when playing a fast paced video game like fortnite.
//SYSIN DD DUMMY
//
-PJ
btt
I suppose Grok 3 is low level AI. I hope what AIs that programmers use are much better. I had an extended Grok3 session over my sci-fi comedy movie pitch/script. We engaged in plenty of back and forth to improve it. I give Grok3 an 80% for coming up with clever new ideas and refinements. While the 20% downside is that Grok3 often illogically scrambles up ideas. So that if this pitch were ever submitted (doubtful) to Hollyweird, a smart human brain would have to clean up the Grok3 burps, stumbles and mishaps/
Will a programmer get his top shelf AI to finalize his code. Then press the send/submit button?
You’re correct. VBA is considered high-level programming.
I’m using it every day in my post-retirement job, and I don’t miss Assembler or COBOL at all.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
AI Overview:
VBA (Visual Basic for Applications) is considered a high-level programming language, designed to be relatively easy to learn and use for automating tasks within Microsoft Office applications and other compatible software.
Here’s a more detailed explanation:
High-Level Nature:
VBA is a high-level language, meaning it’s designed to be closer to human language than machine code, making it easier to understand and write code.
Based on Visual Basic:
VBA is based on the Visual Basic language, which is known for its relatively simple syntax and ease of use.
Application-Specific:
VBA is designed to work within specific applications, such as Microsoft Excel, Word, PowerPoint, etc., rather than being a standalone programming language.
Macro Programming:
VBA is primarily used for creating macros, which are sequences of commands that can be used to automate repetitive tasks.
Automation and Customization:
VBA allows users to automate tasks, create custom functions, and extend the functionality of Microsoft Office applications.
Not a Standalone Language:
VBA code typically runs within the context of the host application and cannot be compiled into a standalone executable.
Interpreted Language:
VBA is an interpreted language, meaning the code is executed line by line rather than being compiled into machine code first.
Object-Oriented:
VBA supports object-oriented programming concepts, allowing for the creation of reusable code and the manipulation of objects within the host application.
Learning Curve:
While VBA is considered relatively easy to learn compared to other languages, it still requires some effort to master its syntax and features.
Smart lady. 😊
“You’re correct. VBA is considered high-level programming.
I’m using it every day in my post-retirement job, and I don’t miss Assembler or COBOL at all.”
When I was in Korea 26 years ago my Korean counterpoint handed me my company’s 120 page emergencies manual and requested that I program it into an Excel program to be used in the emergency response room.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.