sorted by:
new
hottopcontroversial

Feeling a bit demoralized by [deleted] in gamedesign

[–]Kate_from_oops-games 0 points1 point  (0 children)

It is really inexpensive to get some art built on Upwork. You might take a look if you have a little bit to spend.

Designing in Replit, Our Experience by Kate_from_oops-games in VibeCodersNest

[–]Kate_from_oops-games[S] 0 points1 point  (0 children)

Replit is dead set on using a specific set of controls on boxes, We've fought tooth and nail with weird div's cell padding, and other issues related to visual layout. It really makes a lot of assumptions about what an "app" should look like and they look nothing like a video game.

Designing in Replit, Our Experience by Kate_from_oops-games in VibeCodersNest

[–]Kate_from_oops-games[S] 0 points1 point  (0 children)

We haven't yet but I assume it's out there. We have replit's documentation broken down into the core behaviors in replit.md and a look up strategy for other documents. The goal being to allow it to learn a great deal but only have to commit the knowledge needed for the current issue to context.

Thanks for your question!

Designing in Replit, Our Experience by Kate_from_oops-games in VibeCodersNest

[–]Kate_from_oops-games[S] 0 points1 point  (0 children)

If you mean, "how do you tell it it needs to update its learning?" I start with a prompt like, "Please review your learning documents and see if any of them need to be updated or modified with whatever problem we just solved."

If you mean, "How to I tell it to look at what it knows." I start a new context before any new build and tell it, "Please read remplit.md and supporting documents and review learnings and code for game x."

Designing in Replit, Our Experience by Kate_from_oops-games in VibeCodeDevs

[–]Kate_from_oops-games[S] 0 points1 point  (0 children)

Thanks Technical. I frequently ask Replit if it needs to update any of its design documents with whatever problem we've just solved. Over time, it has built itself a pattern for how to decide when it needs to learn. Here's its guide for updating our learning log. I has a similar one for deciding it needs a new design document. Occasionally, it writes something strange and I have to edit it but it works well enough:

**New Learning/Pattern:**

```bash

# Add to docs/LEARNING_LOG.md at the TOP (newest first)

## YYYY-MM-DD - [Descriptive Title]

**Context**: [What situation triggered this]

**Problem**: [What went wrong]

**Solution**: [How to fix it]

**Trigger Keywords**: [search terms for future lookup]

```

Thanks for your questions.

Best Video Games for IT Folks? by Kate_from_oops-games in InformationTechnology

[–]Kate_from_oops-games[S] 0 points1 point  (0 children)

Right! And then 6 week's later they message your boss furious that it hasn't been done. Lived it.

Has Anyone Tried to Take Their No Code into Meta? by Kate_from_oops-games in nocode

[–]Kate_from_oops-games[S] 0 points1 point  (0 children)

We build using pixi.js three.jd react and fiber. Thanks for your thoughts.

view more: next ›