Some feedback from me (not a likely user though): - It was easier to find a link to where you worked at than your repo (https://github.com/skaldlabs/skald?tab=

Some feedback from me (not a likely user though): - It was easier to find a link to where you worked at than your repo (https://github.com/skaldlabs/skald?tab=readme-ov-file https://github.com/skaldlabs/skald?tab=readme-ov-file), you should have linked it visibly - I had no idea what / why I should use it so I looked at the demo video and it didn't seem to solve any particular use case for any particular problem, it was more a ,,config'' video instead of a demo video - From reading the (quite interesting) article it seemed like you are focusing on pivoting instead of iteration speed. Have you tried for example to just query an LLM to build the whole project that you have done? How much time would be to vibe code it? I know that HN is mostly against vibe coding, but if the project could have been created in 1-3 days and you took 3 month, that's a bigger issue than growth itself. In that case the metric that should be looked at is iteration speed instead of just growth (both are super important though!)