0xecro1

5 ms·

1.
LLM PCB Routing: What the Contract Engineer Taught It(edgelog.dev)
2 points by 0xecro1 1mo ago|0 comments
2.
by 0xecro1 7mo ago
It's fundamentally different, and that's exactly why the CPU analogy has an expiration date. Intel never built Windows. The chip layer and the application layer were structurally separated — different companies, different business
3.
by 0xecro1 7mo ago
Interesting approach. I work in embedded Linux/edge AI where we constantly struggle to move knowledge from large training models down to quantized INT8 models on constrained hardware (ARM Cortex-A class). Have you tested transfer to qu
4.
by 0xecro1 7mo ago
Maker here. 18 years in embedded Linux/BSP. I built this because serial terminals haven't changed in decades, and I was tired of juggling 15 PDF tabs while squinting at logs. Two things that make NeuroTerm different: 1) Neuro Inpu
5.
Show HN: NeuroTerm – AI terminal for embedded devs (local LLM, local RAG)(neuroterm.dev)
1 points by 0xecro1 7mo ago|1 comments
6.
by 0xecro1 7mo ago
18 years in embedded. Yes to all three, with caveats. 1. The pattern is real. I write specs and prompts between meetings, agents deliver code by EOD. But deep focus blocks aren't dying, they're shifting from "writing code&quo
7.
by 0xecro1 7mo ago
Been thinking about this a lot myself. My current answer: go vertical and messy. Ex, Healthcare portals with ugly data. Compliance platforms with painful regulations. B2B tools with 6-month sales cycles.
8.
by 0xecro1 7mo ago
I use it for both — side projects and my day job in embedded systems. The key is where the tokens go. More tokens spent on planning, design, spec validation, test generation, and multi-agent review than on writing the actual code. The rev
9.
by 0xecro1 7mo ago
I think the comparison is slightly off. The compiler was never the author — it was the verifier. The real comparison is: 1. Human writes code (non-deterministic, buggy) → compiler catches errors 2. AI writes code (non-deterministic, buggy)
10.
by 0xecro1 7mo ago
I've seen non-programmers successfully launch real apps — not toy projects — through vibe coding. I'm doing it myself, and I'm about to ship a developer tool built the same way. They'll still need to pick up the fundamen
11.
by 0xecro1 7mo ago
Absolutely agree. I do vibe-code, but I still review every line of that 90% — I don't move forward until I understand it and trust the quality. Right now, that human verification step is non-negotiable. That said, I have a hunch we&#
12.
by 0xecro1 7mo ago
Hi,AI tools just shifted the interface of programming from code to natural language. The tool you've been sharpening your whole career — words — is now the primary tool of software development. You're not a non-programmer learning
13.
by 0xecro1 7mo ago
Hi, I’ve been working with embedded Linux for 18 years. I’ve been actively trying to apply AI to our field, but the friction is real. We require determinism, whereas AI fundamentally operates on probability. The issue is the Pareto Principl