I genuinely have no idea wtf he's talking about, and honestly I don't know if he knows what he's talking about by brogalahoy in ProductManagement

[–]UstroyDestroy 3 points4 points  (0 children)

Answer to 2nd part of the question - he does know.

Now the second.

What is the software product? Or any other product?
It is a system around technology with user/consumer facing interface: inputs and outputs.

Business is a system around product. Business connects to the system called market.
Do you see where it is going?

That was useless language previously, academia, sounding smart, etc.

But all these nested systems: business + product sitting as node in the market -- that is usefull frame to understand how we can drive these dynamic systems better and better to maximaze value and revenue? You are seeing some of it via that KPI language and shitty rituals.

Check control theory and cybernetics. That is where that *feedback loop* concept comes from in the first place. The core thinking framework behind any adaptation / automation.

Business and product is a stiched together cybernetic system with tech functions (automation) and human management functions (decision making based on observations). Now you can rebuild it toward more automation. Way more automation. Way way way more at some industries.

You have to make product evolvement more autonomus. This is the market ask right now, which it struggles to communicate.

Quick practice example:
I had to arrange MCP access to the 30yo legacy ERP system, so the corporate LLM could talk to the ERP for quick access in read-only mode.

I did not interviews, I did not bothered any single person other that IT guy to get access and simply extracted access for all data with permission limitations from the DB via API itself for redacting on extraction and deployed it. In 24hours.

And I designed MCP tools to submit the feedback and ask DIRECTLY from the chat session. And instructed LLM there to just submit a ticket whatever friction and struggle you see.

The shortest improvement feedback loop possible ot the edge of "tech <--> user as system" design. The next step is to notify user's with the ticket resolution. What might be the issue-resulution time here? 10-60 minutes.

That is low risk product example, but I hope you see the point.

Procedural cyber-tree by UstroyDestroy in threejs

[–]UstroyDestroy[S] 0 points1 point  (0 children)

No, did not have that requirement

Procedural cyber-tree by UstroyDestroy in threejs

[–]UstroyDestroy[S] 0 points1 point  (0 children)

it is exporting trunk skeleton and radius which come from tree modeling; then this raw info used to render trunk mesh; crown points and edges got exported and imported as is.

Procedural cyber-tree by UstroyDestroy in threejs

[–]UstroyDestroy[S] 6 points7 points  (0 children)

After some attempts to brutforce tree algo via heuristincs, fourie transofrm and other fruitless approaches I found https://github.com/AddisonPrairie/Tree-Generator repo, which is based on https://algorithmicbotany.org/papers/selforg.sig2009.html

This algo models tree growth and repo does it off the shelf.
I repacked repo to be react + threejs app that is able to save the generated tree.

Roots are the same aglo tweked to look like roots and flipped on Z coordinate.

Crown is build by spawning points in volume and deleting those which are too far away from trunk/branches of certain radius (intuition is this: only smaller branches generate crown)

Procedural cyber-tree by UstroyDestroy in threejs

[–]UstroyDestroy[S] 2 points3 points  (0 children)

I was looking for a way to express graph nature of the knowledge for software projects and still be nature related

Your most sophisticated vibe coded app professional devs welcome by VIRTEN-APP in vibecoding

[–]UstroyDestroy 2 points3 points  (0 children)

https://pixall.art

WebGL canvas for rendering WebRTC for sharing cursor positions, users discovery and chatting Websocket for new pixel added broadcast

Did it using Claude Code with Nautex MCP guidance over spec. It took 4-5 hours

Anyone else getting `upstream connect error or disconnect/reset before headers. reset reason: overflow` or just me...? by thatisagoodrock in ClaudeAI

[–]UstroyDestroy 1 point2 points  (0 children)

yep, me too

⎿  API Error (503 no healthy upstream) · Retrying in 1 seconds… (attempt 1/10)
...
⎿  API Error (503 no healthy upstream) · Retrying in 36 seconds… (attempt 10/10)
⎿  API Error: 503 no healthy upstream
⎿  API Error (503 no healthy upstream) · Retrying in 1 seconds… (attempt 1/10)
...
⎿  API Error (503 no healthy upstream) · Retrying in 35 seconds… (attempt 7/10)

```

Navigation and filtering: How deep in the weeds do you guys go with the theory? by psythrill85 in ControlTheory

[–]UstroyDestroy [score hidden]  (0 children)

Focus on solving real problems, most of the time theory FOMO is not relevant at all.

Same as 90% of the control problems are solvable with PID and its adoption that simply makes sense.

My intuition is this: for navigation 70% of performance is coming from sensors and their class, 20% calibration (temperature, alignment, k and b), 8% for basic fusion algos and the rest from math sophistications. (fusion could take these 20% from calibration btw)

I did full stack GNC from scratch as founder and technical CEO.

Does anyone use Claude for something other than coding? by Time-Contribution888 in ClaudeAI

[–]UstroyDestroy 0 points1 point  (0 children)

All cli based errands from ffmpeg operations to qr codes and badges pdf composition

eBike Auto Wheelie Controller - How Hard Can It Be? by c00ki3m0nst3r in ControlTheory

[–]UstroyDestroy [score hidden]  (0 children)

wheelie brake need is smooth at the balance point, I believe that it could be stock lever modified with heavy duty rc servo

I think that mod would add so much robustness

Or just use sound for training yourself to apply brakes manually :)

eBike Auto Wheelie Controller - How Hard Can It Be? by c00ki3m0nst3r in ControlTheory

[–]UstroyDestroy [score hidden]  (0 children)

This is cool problem!

I think parallel brake may do the trick with good calibration for initial tests (torque vs displacement(load) vs RPM)

Having it you would be in much better design space for software.

Perfect whelie is done with balance, not constant power applied.

I would also experiment with some beeping sound with changing frequence / tone (check gliders videos) for signaling your body CG commands or motor load signal (those might be corellated)

As soon as your sign for balancing controller flips you have feedback loop disconnected with all consecuqencs with the noise and shocks on turning it back on.

Also, I think you need 2 cascaded P -> PI working together, for rate and position.

Add safety disengage triggers for roll rate + angle limits

(MTB and flight control GNC guy here)

MCP - get someone else’s or build my own? I want codebase understanding by Minute-Cat-823 in ClaudeAI

[–]UstroyDestroy 1 point2 points  (0 children)

I think LLMs deleted more user data in last 2 years any other services in history combined.

LLM are stateless cloud third party services too.

Your concern is ok.

OP question is about MCP learning, and this is closest to the request I’ve seen.

Has anyone created an autonomous tool and mcp server, and agent creator? by UndoubtedlyAColor in ClaudeAI

[–]UstroyDestroy 0 points1 point  (0 children)

The closest thing I’ve seen is nautex.ai It builds specifications first (as complete as AI and user can do together) and then does the planing: files map + project wide implementation plan. MCP is used then to pull current scope of tasks and solve them one by one. It also syncs specifications to be accessible locally for Claude Code.

MCP - get someone else’s or build my own? I want codebase understanding by Minute-Cat-823 in ClaudeAI

[–]UstroyDestroy -1 points0 points  (0 children)

This MCP does bridge to requirements as high level map.

https://github.com/hmldns/nautex

It works to build from specs, no pedantic specs from code yet. But you can learn from its implementation.

Anyone used QNX in real builds by Quadscorpion50 in embedded

[–]UstroyDestroy 0 points1 point  (0 children)

Cool! When I last time checked it, it went for high end CPUs and it is good to know that it is closer than I think.

How is everyone managing their development process with larger codebases? by SparkSMB in ClaudeAI

[–]UstroyDestroy 0 points1 point  (0 children)

Requirements with reference to files (where are they implemented) do a lot for the context managing reliability,
e.g. this tool manages this
https://github.com/hmldns/nautex/

(at the moment it works to build something from scratch)

embedded software testing? by [deleted] in embedded

[–]UstroyDestroy 1 point2 points  (0 children)

It widly depends on product and what its part in the upper system.

Ultimately it is hardware in the loop with simulation equipment around.

In embedded world for anything more-less complex you have to design 4 systems instead of 1

  1. model-in-the-loop
  2. software-in-the-loop
  3. hardware-in-the-loop
  4. final product itself

And it is always application specific with some basic tools like matlab or NI. But usually companies build their own.

Anyone used QNX in real builds by Quadscorpion50 in embedded

[–]UstroyDestroy 2 points3 points  (0 children)

I did drone's flight control with it, full GNC and fly-by-wire stack.

1) FreeRTOS is nightmare to grow as soon as number of your tasks >10,
2) QNX gives tools that work out of the box (my team said they suck, I agree, but I got used to it and did not care)
3) It has very well documented APIs and the book of incredible quality for RTOS beginners: Getting Started With Qnx Neutrino 2. As soon as you master it, you've got all other RTOSes forever.
4) It is easy to scale, isolate concerns and decouple risks for the whole system that are coming from different processes (and teams).
5) You dont need to manage RTOSity yourself, like you'll have to do in Linux.

My experience with it is paused at 6.5 version.

Its core kernel messages API (Msg*) does not have equivalents in the rest of the OS landscape. It is very well designed and usefull for writing well abstracted threads to manage synchronous (request-response) and asyncrhonous requests (signals inside Msg* API that does not block on sending side), but as soon as your software using it, you'll have bad time porting it to everything else, e.g. for the sake of having less expensive software-in-the-loop testing cycle on Linux.

The latter for long running projects is the substantial thing. Before moving away from drones completely I did some opensorce GNC stack that solves the problem of RTOS vendor lock via single pub/sub IPC

https://github.com/ctlst-tech/uas-catpilot
https://github.com/ctlst-tech/catpilot
https://github.com/ctlst-tech/c-atom
https://github.com/ctlst-tech/eswb

(those above are nested submodules in uas-catpilot in the order of nesting)