Forum - Recent Threads

This is how I compare Laplace Conjecture with AI Hype Conjecture

HKPhysicist — Sat, 08 Aug 2026 08:43:02 GMT

Laplace Conjecture: If you gave me a long enough rigid stick and a fulcrum, I were able to displace the Earth.

At that time, Laplace's Conjecture was believed to be very true by classical physics.

100 years later, his conjecture was disproved by a completely new space-time structure.

AI Big Hype Conjecture: If we could get enough processing power (resources, investment and finally, money of course), our data centres and their software would finally turn out to be omnipotent.

However, those AI big hype corps cannot even estimate a formula of their conjecture.

"Total Volume of Context Stored represents Intelligence and Skill"

This is another conjecture always boosted by AI Big Hype corps. Here is how a net buddy responds to the above conjecture (credit to him):

If a land-based continental creature (for instance, a chimpanzee) reads all the swimming tutorials which human have ever authored, does it imply that the chimpanzee could swim as well as the swimming trainers?

In the future, there are only 2 sets of people left - one set who knows AI and the other set who doesn't.

The implication of this statement is that - if you do not learn AI and pay money to buy AI services right now, you will belong to the 2nd set - the set of poor people.

This is how I respond to the above statement with these analogies:

After the invention of vehicle driven by combustion engine, people were divided into 2 sets - the one who could drive and another set of people who could not drive. As we know, professional drivers are usually considered as labours; while some very rich people might even do not need to drive a car.
so many similar analogies.

RE: This is how I compare Laplace Conjecture with AI Hype Conjecture

colporteur — Sat, 15 Aug 2026 00:18:03 GMT

It is not my intention to monopolize the topic but I just found this quote and it is so how I feel.

"Future shock is the shattering stress and disorientation that we induce in individuals by subjecting them to too much change in too short a time." quote by writer Alvin Toffler. It describes the psychological paralysis, anxiety, and disorientation people experience when the pace of technological and social change outstrips their ability to adapt. They is a picture of me next to this!

RE: This is how I compare Laplace Conjecture with AI Hype Conjecture

colporteur — Fri, 14 Aug 2026 23:56:22 GMT

K, I am more and more becoming a believer that if we do not learn AI we are at a disadvantage. Since joining ChatGPT Plus, I’ve had to confront many personal biases to maximize my effectiveness.

I refused to upgrade my big-button cell phone until finally it prevented me from doing what I wanted to do. The same for my AI subscription. I had reached a point that no AI or free AI limited, me.

I have 40 years of learning to apply when I use AI. I find it difficult to direct its actions toward my goals, as it asserts its own will. Microsoft unilaterally determines this approach, removing your choice.

My quest at the moment is to learn how to talk to AI. If you could follow my problem-solving chats with ChatGPT, you would find the response. STOP: Tell me how to tell you how I want our interaction to occur. Since getting a subscription, I have discovered there are personal settings that i am using more often.

Learning how to interact with AI appears to be a self-learning exercise. If you find someone willing to share their insight, it can make the interaction more fruitful. I wish I could still have my big button cell phone. That is not reasonable, but then again I liked wooden hockey sticks. You bring one of those into a dressing room today, no one will sit next to you.

Bt the way. Great topic. I only wish it was with a bunch of folks around a table drinking coffee and trying to solve world hunger.

P.S. I even used AI to proof this document so these are not my words. No that statement is not true. AI doesn't like my grammar or lack of spelling skills. My grade 10 teacher had the same AI issue.

RE: This is how I compare Laplace Conjecture with AI Hype Conjecture

kmikemoo — Mon, 10 Aug 2026 20:52:32 GMT

I think "AI" is such an ambiguous and ill-defined concept that it can succeed and fail at the same time. Those segments that fail will be defined as hype and those that succeed will just become part of what we do - like the "decision systems" of the 1980's.

RE: This is how I compare Laplace Conjecture with AI Hype Conjecture

DAB — Sun, 09 Aug 2026 19:42:10 GMT

You make the assumption that AI will succeed.

I have been following AI for nearly 50 years and in all of that time, it has yet to produce what I call a killer app.

Yes there are some fancy tools that people say are AI, but so far I have been underwhelmed.

There are far more things in the world that will work without AI then there are things that will be done by AI.

Until AI is verified and validated, it is a very dangerous piece of software. It is only when it gets you into trouble, not if.

When I see a useful product out of AI I will evaluate it, but it will have a high bar to reach before I am willing to pay money to use one.

RE: This is how I compare Laplace Conjecture with AI Hype Conjecture

robogary — Sun, 09 Aug 2026 11:51:40 GMT

In Star Trek III: The Search for Spock (1984), Scotty says, "The more they overthink the plumbing, the easier it is to stop up the drain."

RE: This is how I compare Laplace Conjecture with AI Hype Conjecture

manojroy123 — Sun, 09 Aug 2026 05:55:21 GMT

Very interesting article.

Which AI tool do you use for documentation?

prajaktaa — Sat, 11 Jul 2026 04:29:11 GMT

I am curious to know that which AI tool the community members are using to create or improve technical documentation.

Whether it is for the project documentation, API documentation any troubleshooting guides, or internal knowledge base articles, AI has become a helpful assistant for many professionals.

Some popular options include ChatGPT, Claude, Gemini, GitHub Copilot, Microsoft Copilot, and Perplexity, but each has its own strengths and limitations.

My questions are:

Which AI tool is easy to use for documentation?
What type of documentation do you create with it?
What do you like most about the tool?
Have you found any limitations or challenges?
Do you rely on AI-generated content as-is, or do you always review and edit it before publishing?

I'd love to hear about your workflow, practical experiences, and any tips or best practices you've discovered.

RE: Which AI tool do you use for documentation?

vmate — Tue, 04 Aug 2026 22:42:05 GMT

Well, your point about reflecting got to me. Indeed, my original response was significantly harsher than it should've been, although I didn't intend any of it towards you, but rather the, let's just say 'lack of pride in their work' of the people making these AI courses. My intention was getting to the point quickly and effectively for someone who'd just skim through these texts: do not use these guides, they are straight out misleading. At least by the end, we're both better off I guess: hopefully you know not to trust these oversimplified comparison tables the next time, and I learned to think a few more times about what I write, to make sure I don't come off as inconsiderate and offend someone I didn't mean to.

RE: Another China AI Company & her Open Source Models which shocks USA AI monopolies

HKPhysicist — Mon, 03 Aug 2026 14:34:14 GMT

Yes, never ever post any of your ground breaking ideas or contents to public webs or feed them to AI companies.

Publish to paper journals first.

Another China AI Company & her Open Source Models which shocks USA AI monopolies

HKPhysicist — Fri, 31 Jul 2026 19:34:14 GMT

Hello Friends,

I personally prefer open source software. Also, I heard that Moonshot AI's newest Kimi K3 model is at the same par as USA closed source company models such as Open AI, Anthropic, etc.

So let me introduce her to you and see whether you can find some applications in your own field.

https://github.com/MoonshotAI

Another goal of open source software is - to balance digital monopoly, to drag down their market price, and increase the marginal profit of hardware products. [emoticon:c28b2e4cc20f4ba28d1befdba6bed29c]

RE: Another China AI Company & her Open Source Models which shocks USA AI monopolies

cstanton — Sun, 02 Aug 2026 20:10:19 GMT

Looks like it's gaining traction: https://www.bbc.co.uk/news/articles/cy9w4q8pgp0o

I'm always cautious with ai sites because of the data they collect and retrain upon.

RE: Which AI tool do you use for documentation?

shabaz — Sun, 02 Aug 2026 16:35:37 GMT

It's free (open source) so the diagram source should always be usable if the site disappears. But I am interested in other options always, I would prefer more design control personally (I am quite picky about positioning of each element, etc!) hence I mostly (ab)use PowerPoint, but that's not efficient use of time.

A shortcut I've used a few times for reverse documentation: run all the test cases, capture the log output, and then run that through a parser to generate such ping-pong/message sequence diagrams, and use that as documentation : ) That's only possible if the logging has enough information in it of course.

For one project that was so useful, a customer saw me using the parser tool to troubleshoot their setup, and wanted it; so from then on we packaged it with the system, and the customer could turn on logging, and run the tool, and easily see what was going on (the diagram showed external inputs arriving into the system, then the few key functions that were executed internally to ripple through to state changes or a response back out, so they could easily see if things were abnormal or not). It was quite handy to see if things were overloaded (e.g. loads of incoming events) or weird state machine changes, etc. This was for the more tech-oriented users (the more normal way was to use third party tools to monitor the entire solution at once, not just one device).

RE: Which AI tool do you use for documentation?

BigG — Sun, 02 Aug 2026 15:40:11 GMT

Yep, I tried it although I believe the free option is a time limited trial. Pain.

I found https://sequencediagram.org/ to be very handy and works well with AI tools like Gemini/AntiGravity. I just tell it to review my code base and create a sequencediagram script of the sequence process and it does it. Then you just copy the script into the website and out pops a diagram which you can view/download. Very useful.

RE: Which AI tool do you use for documentation?

shabaz — Sun, 02 Aug 2026 15:29:22 GMT

Anyone tried Mermaid? It's an online diagram-drawing tool that accepts text-based input. I mention it because AI can be prompted to generate Mermaid output. Might not be correct always, but it can be useful to get an idea about a body of code that one might be new to.

Example screenshot, where the red box is my microcontroller.

To do this was quite simple:

1. Install AntiGravity CLI (or use whatever AI you wish; AntiGravity is the consumer way of accessing the functionality in Google Gemini).

2. I used Windows PowerShell. I went to the folder where my body of code was, and ran AntiGravity (by typing agy) and then just explained in text what I wanted:

If you were say using ChatGPT you could have uploaded the files, or perhaps simply provided the URL if the code was on GitHub, and so on.

3. The output was a file called ARCHITECTURE_DIAGRAMS.md

4. I copy-pasted the diagram from the .md file into the Mermaid website.

I can use the diagram to refresh myself about how the code is architected.

Personally I like drawing my own diagrams because I prefer reducing them for as much simplicity as I can manage, but it is still useful for a quick reference.

RE: Which AI tool do you use for documentation?

bradfordmiller — Sun, 02 Aug 2026 13:08:23 GMT

I think it depends on what you are building and documenting. One does not normally implement a compiler and then "discover" what language it compiles. One invents the language first and then writes the compiler.

System engineering starts with requirements, not implementations.

Design generally should put the human user first, and designs around the user goals and interactions. Then people can worry about how to build that.

Lower level things like API documentation should at least start with a design so multiple teams can implement concurrently. It can always be adjusted as issues arise (hey we need to include a FOO in the argument list for these functions because ...). Better editors and implementation languages allow making such changes easy (who-calls).

RE: Which AI tool do you use for documentation?

dang74 — Sat, 01 Aug 2026 22:21:11 GMT

Thanks. I like how the last row shows what each tool is "best for." It's a good way to end the table.

RE: Which AI tool do you use for documentation?

colporteur — Sat, 01 Aug 2026 20:36:38 GMT

My ire over the dialog has diminished. I'm chuckling to myself as I post this response. I did some reflection before responding. As I get older I find that seems to be more important than just replying.

I went to a very good friend of mine with a problem I was struggling with. He listened attentively asking probing questions to fully understand the issue. After a few moments he said, "I have the answer you are looking for." He then waited before saying, "I just can't tell you."

Our friendship has grown over the years. We still laugh over that conversation. It took me ten years to respond. "I would never have listened to you, if you did give me an answer." His response, "I knew that so I wasn't going to give you an answer anyway."

"I appreciate that you didn't intend it as a personal attack. My concern isn't your technical disagreement—it's the language you chose.

Calling the table 'horrible,' comparing it to astrology, and later referring to AI guides as 'completely useless trash' is dismissive rather than constructive.

The sources you later provided were far more persuasive than the original wording. That's the distinction I was trying to make."

I confess I didn't write the above prose. After reflecting on your response, I thought maybe it's just me. The reply is an AI's response to the question, "What is an object of an apology?"I also provided the dialog we've had, along with some of my thoughts. I posted the AI response because it reflected my values.

RE: Which AI tool do you use for documentation?

colporteur — Sat, 01 Aug 2026 19:26:44 GMT

I started my technology career in 1981. Entering a site required a sign-in and sign-out. Every action taken on the site or work on the equipment was written in a site logbook. If the was an incident, the log book was the first thing ceased by authorities.

4X4 drawings show system interconnect were the norm. On training course you were given a blank schematic. By the end of the course you would have used up half your colour pencils making notation. Green for receive and red for transmit.

The lessons learned in those 18 years never left me. Every job I took after that, I carried a notebook. I typically start a project with what I call the "Napkin Drawing." The doodles sometimes on a napkin that flush out an idea. I find it really hard to discard the napkin even after the CAD's are done. Maybe I will miss something I had on the napkin. KiCAD'ing a schematic is time well invested.

Up to this point only time has been invested. I have a scope of work, a component list and a way to estimate time. If at this point it never gets built, time can't be returned. I also discovered once mothballed it take time to recover the knowledge that got me to this point. The older I get, the harder it is to recover.

I find sharing project experiences on this site a great way to document.

RE: Which AI tool do you use for documentation?

HKPhysicist — Sat, 01 Aug 2026 16:12:55 GMT

Me Too Movement.

I am also a minority in 2030. I even feel vomiting when it comes to designing hardware with AI or designing hardware software with AI.

Real world hardware design, AI, are actually different domains.

As far as I know, the most complicated robotic actions shown on video are actually fine-tuned for many months before they are shown on the TV stage. From this viewpoint, they are just a remote controlled toys with more degrees of freedom.

I had Japanese made remote controlled F1 when I was a boy. At that time, we called them remote controlled toys, not AI. 😁

RE: Another China AI Company & her Open Source Models which shocks USA AI monopolies

HKPhysicist — Sat, 01 Aug 2026 07:08:07 GMT

I am still learning.

I have found their software which is free to download.

Browse to https://www.moonshot.ai/

On the top menu, click [Download]. There is a list of software for Desktop. 😁

It is their public forum. 😊

https://forum.moonshot.ai/

RE: Another China AI Company & her Open Source Models which shocks USA AI monopolies

cstanton — Fri, 31 Jul 2026 21:49:56 GMT

Do you have examples of configurations and tooling to get it up and running?

RE: Which AI tool do you use for documentation?

skruglewicz — Mon, 13 Jul 2026 18:40:43 GMT

I have taken course on udemy.com for LLMs and Agentic AI. I've used every Model and agentic tool available. I use them for Brainstorming Embedded projects using various languages and a wide verify of Evaluation kits. Leaning on AI for design, brainstorming, and vibe coding is a highly effective workflow for me. It is especially useful when prototyping or mapping out the logic for embedded hardware platforms —you can nail down the architecture and flow conceptually before getting bogged down in the syntax.

Currently, I use Gemini exclusively for Design, Brainstorming and vibe coding.

I have not generated documentation from AI yet . The thread here is interesting and I'm open to checking out the possibilities of using the tools mentioned in the thread.

RE: Which AI tool do you use for documentation?

BigG — Mon, 13 Jul 2026 14:11:28 GMT

Gemini has no problem creating Doxygen style documents. Works really well. No doubt Claude and chatGPT could do similar.

https://www.doxygen.nl/

RE: Which AI tool do you use for documentation?

prajaktaa — Mon, 13 Jul 2026 03:41:34 GMT

I really like your point of view. I agree that documentation should start from the beginning of a project instead of being written only after everything is finished. It also helps explain why certain design decisions were made, not just what the final result is.

I don't think AI should make important engineering decisions either. For me, AI is more useful after the planning stage. It can help organize notes, improve writing, create summaries, or make documentation easier to read, while the engineer still makes all the important decisions.

I think AI works best as a helper, not as a replacement for the engineer.