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

I'm trying to envision the application of a mesh like this. These could be examples?

- interconnected nodes need to share data (like images)

- interconnected nodes are acting as a collective array of sensors (eg. geolocation)

- interconnected mesh nodes provide redundant pathways back to the central node

- interconnected mesh nodes provide spatial diversity in case of interference or jamming

- nodes are mobile (eg. drone or vehicle) and mesh provides alternative connectivity based on node location and RF attenuation (also provides longer range with mesh connectivity)

I admit that AI generated writing is a little strange unedited. Putting that output into a writer's voice with personal experience is always going to help to humanize it and make it more readable.

But the reality is that AI is just the next phase of borrowing and rehashing of older materials and concepts--just like reading an encyclopedia or Wikipedia article and then putting those rehashed words into an essay.

My suggestion is that as long as you enjoy what you're reading or learning, it's probably not worth getting upset about provenance. Anything truly new and innovative can't come from AI anyway--and innovation is very rare.

There is nothing new under the sun.

https://youtube.com/playlist?list=PL6D54D1C7DAE31B36&si=Kw3J...

or "The History of English" series:

https://youtube.com/playlist?list=PLV50II2XzmY-9GLZWAuieOp27...

In the second series, there is a weather report in Frisian that vaguely sounds like English.

1. Antennas are designed to either transmit or receive RF.

2. The antenna is like water spigot for RF energy. If you design the antenna right, you can maximize the amount of RF energy you can get through it. This is equivalent to minimizing the impedance.

3. But, antennas are resonant. In other words the amount of RF that gets through can be maximum at one frequency (or a small range or bandwidth of frequencies), but very bad outside of that range.

4. Antenna designers try all kinds of tricks and techniques--including shapes, elements, delays, etc.--to try to get the antenna to have a broader resonance. An analogy might be the design of a musical instrument like the saxophone.

5. The VSWR the author mentions is a way of charting the resonance of the antenna with respect to frequency, ie. the bandwidth of the antenna.

6. Typical antennas (like a rod or something) have a bandwidth of maybe 5-10% of the center frequency.

7. Fancier antennas like a discone have a fractional bandwidth of up to 10:1.

8. An antenna like the one described by the author claimed to be 100:1.

9. But...even though the antenna may have broad bandwidth...the other factor antenna designers care about is gain (or loss). And this just complicates the design process even more.

Now, what I find most interesting about the author's comments is their suggestion that people continue to reinvent the wheel and then patent it. I too have seen this happen (not necessarily patents, but with other "technology inventions") over the years. I used to work in radio direction finding and every five or ten years someone would claim to have a new way of locating signals--but it's always just the same ideas over and over again. In other words, physics is physics.

I think that citizen developers will be a thing--but not in the way you might be thinking.

More people will be enabled (and empowered) to "build" quick-and-dirty solutions to personal problems by just talking to their phone: "I need way to track my food by telling you what I ate and then you telling me how much I have left for today. And suggest what my next meal should be."

In the current paradigm--which is rapidly disappearing--that requires a UI app that makes you type things in, select from a list, open the app to see what your totals are, etc. And it's a paid subscription. In 6 months, that type of app can be ancient history. No more subscription.

So it's not about "writing apps for SaaS subscribers." It's about not needing to subscribe to apps at all. That's the disruption that's taking place.

Crappy code, maintenance, support, etc.--no longer even a factor. If the user doesn't like performance, they just say "fix ___" and it's fixed.

What subscription apps can't be replaced in this disruption? Tell me what you think.

https://youtu.be/Z0YdJNeNXLE?si=dGsAp-ojT_TDrJNX

The power is in the marketplace. As long as people are free to make rational choices about price and consumption, the miracle of capitalism will prevail.

Don't like big oil? Don't use a lot of gasoline. Angry about Silicon Valley? Stop using social media. Egg and beef prices ticking you off? You know what to do. Is the cost of housing too high? Form cooperatives, move to another location, etc.

This works for social and political issues as well where free choice is still available.

Be the change that you want to see happen in a capitalist free market system.

Using the latest completed U.S. Census metro-area estimates I could verify — population change from July 1, 2023 to July 1, 2024 — the 5 fastest-growing U.S. metro areas by percentage growth were:

1. Ocala, Florida — 4.0%

2. Panama City–Panama City Beach, Florida — 3.8%

3. Myrtle Beach–Conway–North Myrtle Beach, South Carolina — 3.8%

4. Lakeland–Winter Haven, Florida — 3.5%

5. Provo–Orem–Lehi, Utah — 3.0%

One wrinkle: Daphne–Fairhope–Foley, Alabama also grew 3.0%, so it was effectively tied with Provo–Orem–Lehi on growth rate, though Census ranked Provo 5th and Daphne 6th.

But these are the things you need to consider first when choosing an area to work in for developing a product and ultimately a business:

1. What do you know really well? These are things that come from your personal experiences. Note: this is generally not about software or coding skills--it's about everything else in the world.

2. What are the problems or valuable opportunities in the areas you know well? Where there are serious problems, there are opportunities for valuable solutions.

3. Timing. What's happening in the world and how do the changes open doors for new solutions?

4. Market and Value. How many people suffer with the problems you are trying to solve? How well do you understand them? How much money will they spend for a solution? How many of these people have you spoken with: 25, 50, 100?

5. Who is competing in your market? What can you learn from them? How does your solution compare?

It's best to consider several problems and conceptual solutions before settling on one. Talk with people, build small prototypes, figure out if you truly understand the requirements.

If you do all of these things, you will have a much better shot at bringing forward a viable product and business idea.

There are some really good books out there on this whole process. Good luck.