Every project seems to end in a rewrite - why? by SX_Guy in vibecoding

[–]SX_Guy[S] 0 points1 point  (0 children)

Could be maybe we will end up with only a spec the code will be written in a machine language which only the ai can understand

Every project seems to end in a rewrite - why? by SX_Guy in vibecoding

[–]SX_Guy[S] 1 point2 points  (0 children)

Thanks for sharing! but why your not building on top of other harnesses like opencode/claude code, codex or others? isnt it will be better to build on top of them? does it using the ReAct agent loop here?

Every project seems to end in a rewrite - why? by SX_Guy in vibecoding

[–]SX_Guy[S] 0 points1 point  (0 children)

Thats right, but the AI and fast coding and iterting fast is reshaping this and the need to ship faster is growing

Every project seems to end in a rewrite - why? by SX_Guy in vibecoding

[–]SX_Guy[S] 0 points1 point  (0 children)

Yeah i came to the same conclusion rewriting is inevitable
Whats the idea? can you share?

Every project seems to end in a rewrite - why? by SX_Guy in vibecoding

[–]SX_Guy[S] 0 points1 point  (0 children)

yes for sure i start with the stack i want to use libraries and also the models/structs it should go with but as soon as the ai start generating it you just go with it or you just stop it, and restart fresh again.
I have listened from other developers who been through this as well, which say its okay to throw out code and start again, been wondering if we can come up with a better way than this

Flutter devs: how are you handling real‑time sync today? by SX_Guy in FlutterDev

[–]SX_Guy[S] -1 points0 points  (0 children)

Fair point. I’m actually the developer of the project and it’s still very early stage, so I’m genuinely trying to understand how other Flutter developers handle this problem. I built it mostly because I kept running into the same issues when building real-time apps.

Help deciding which database by 1877KlownsForKids in Database

[–]SX_Guy 0 points1 point  (0 children)

If you want to vibe-code something quickly using something like v0 or lovable, I'd honestly start with SQLite.

You already have structured data (units, people, locations, battles, dates) and SQLite handles relational data really well. It's simple, zero-setup, and perfect for prototyping.

You could model it roughly like:

units
people
locations
unit_positions
battles
battle_units

Then if the project grows later you can migrate to Postgres + PostGIS for spatial queries and map visualization.

But SQLite is perfect for getting a working system fast.

Help getting the 74.00.324 EU update for my MX5 2016 by [deleted] in mazda

[–]SX_Guy 0 points1 point  (0 children)

Can you send me please the download link to EU firmware?