28
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 May 2026
28 points (93.8% liked)
Hardware
7424 readers
93 users here now
All things related to technology hardware, with a focus on computing hardware.
Some other hardware communities across Lemmy:
- Augmented Reality
- Gaming Laptops
- Laptops
- Linux Hardware
- Linux Phones
- Monitors
- Raspberry Pi
- Retro Computing
- Virtual Reality
Rules (Click to Expand):
-
Follow the Lemmy.world Rules - https://mastodon.world/about
-
Be kind. No bullying, harassment, racism, sexism etc. against other users.
-
No Spam, illegal content, or NSFW content.
-
Please stay on topic, adjacent topics (e.g. software) are fine if they are strongly relevant to technology hardware. Another example would be business news for hardware-focused companies.
-
Please try and post original sources when possible (as opposed to summaries).
-
If posting an archived version of the article, please include a URL link to the original article in the body of the post.
Icon by "icon lauk" under CC BY 3.0
founded 3 years ago
MODERATORS
I can see benefits during the development process, not necessarily in the finished product.
Hardware PCB development is currently very much iteration based. You update schematics and layout , produce a PCBA (can take weeks), then test thoroughly. In case of issues, you have to repeat the whole cycle.
In more complex designs where you need to achieve very low noise/interference and stable behavior in any ambient condition the testing can become very time consuming.
If you could reconnect traces, shift or reroute them you would not only greatly reduce the time it takes to update and test a design, but you can also test many layouts and therefore create more optimal designs that might be smaller, more cost optimized or better performing. And the entire process could become more tightly computer automated.