Posts in ScenerySketching
Bridging the odds, with LSP
- 2026/07/26
- Geldrop
- English
- ScenerySketching
As CodeAI makes mistakes, code-checking has become even more important. And, it needs to be smarter than
traditional static checkers. Where human developers traditionally make mistakes around syntax details, generated
code is often correct on that aspect — but the reverse is often true for ‘names’. An engineer will hardly ever
calls an internal function that does not exist, but CodeAI might use a name because it is often named that way …
Especially when using hardware-related details, this can become erroneous. Reading register ‘X’ —because that is
statistically likely— may even compile and yield a bit, but when your pin is connected to register ‘Y’, it’s the
wrong result.
So, we need a checker that knows these kinds of details about your teams’ code. And when possible, can talk with
the CodeAI to contribute that kind of detail. It is possible to connect those ideas, although it is not obvious. We
need a few big steps to bridge the gap.
In this article, we introduce LSP; later, we will handle the other parts, such as MCP.
Document your thoughts (with gptel)
- 2026/07/05
- Geldrop
- English
- ScenerySketching
Many teams use AI to “type faster”, either by using tools that produce ghost code or by practicing vibe
coding. But “building sovereign software” isn’t like building a house—where high-speed brick-laying does
shorten takt time. Determining “what” the (embedded) system should do and “how” the (technically complex)
software should interact takes a significant amount of time.
As engineering is mostly reasoning, typing speed is futile.
To speed up engineering, the real question is: How to use CodeAI to “think faster”?