Reminds me of this statement by Brian W. Kernighan, "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it."
But your next bridge will be better, benefiting from the experience of the previous one, and you might be able to even do some design up front for the third one that actually sticks.
Tl;dr get started on your first bridge early.
A corollary is that if you are writing code with minimum repetition, you are effectively a compression algorithm, not a programmer.
I do not understand why that follows. Can you elaborate, please ?
I did it with the Scala IDE back in 2006/2007, unfortunately, complete with mixin layer overuse.
Interesting. Power vs difficulty in debugging.
" BOT filled its goals of an architecture that is infinitely extensible and runtime modifiable, but that degree of power came at a cost - despite its simplicity the resulting program is very hard to follow. I've recently come to understand that this is because mixins are fundamentally an anti-pattern and BOT is basically dynamic mixins."
BOT is described here: http://www.chris-granger.com/2013/01/24/the-ide-as-data/