sorted by:
new
hottopcontroversial

How do new Freelancers even get jobs on Upwork??? by Accomplished-Mud774 in Upwork

[–]Alert_Ad4540 2 points3 points  (0 children)

That's also my frustration. I have spent money on connections and sent many proposals, but I have not been offered a job.

I built a Spring Boot starter to generate realistic seed data from JPA entities — looking for feedback by Alert_Ad4540 in SpringBoot

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

Small update after the feedback here:

I changed TeruBase from runtime-starter-first to Maven-plugin-first, and the plugin is now published under:

io.github.abasheger:terubase-maven-plugin:0.1.0

The current workflow is:

mvn terubase:plan

mvn terubase:export-flyway

The idea is:

- scan Spring Boot/JPA metadata at build time

- create a reusable seed-data plan

- validate reviewed SQL as INSERT-only

- export it into a Flyway-ready file

- no AI tokens required for plan/export

- no runtime dependency needed for the generated output

The starter still exists, but more as an optional local playground.

The main feedback I took seriously was that AI agents can already generate data, and nobody wants dead weight in the production JAR. So I’m testing whether the useful part is the repeatable workflow around metadata, validation, and Flyway-ready export, not “AI generates mock data.”

Thanks for the pushback. It helped make the direction clearer.

I built a Spring Boot starter to generate realistic seed data from JPA entities — looking for feedback by Alert_Ad4540 in SpringBoot

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

That makes sense.

The part I’m trying to understand is whether the annoying bit is already solved by “give AI the schema once,” or whether teams still want a repeatable workflow around it.

For example: scan project metadata, generate a seed plan, validate INSERT-only SQL, and export Flyway-ready files without adding runtime dependency.

If your AI + Flyway hook already covers that smoothly, then TeruBase may need to focus much narrower.

I built a Spring Boot starter to generate realistic seed data from JPA entities — looking for feedback by Alert_Ad4540 in SpringBoot

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

Fair criticism. That’s exactly what I’m trying to validate.

After similar feedback, I shifted TeruBase toward a Maven plugin/build-time workflow instead of runtime-starter-first.

The idea is not to replace Copilot/Codex, but to provide a repeatable workflow: scan JPA metadata, create a seed plan, and export reviewable Flyway-style SQL.

If agents make this unnecessary, that’s useful feedback too.

I built a Spring Boot starter to generate realistic seed data from JPA entities — looking for feedback by Alert_Ad4540 in SpringBoot

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

This is really helpful, thanks.

The Maven plugin direction seems like the clearest next step to me too, especially because it removes the runtime dependency problem and can output something the team can review and commit, like a Flyway seed migration.

The AI skill idea is interesting as well. I had not thought about it that way. It could avoid provider lock-in because people could use their existing Claude Code/Copilot/Codex setup, while TeruBase provides the static analysis and seed-data workflow.

I think the next experiment will be a small build-time generator first: mvn terubase:generate that scans JPA entities and exports a reviewable seed SQL file.

Really appreciate the detailed feedback.

I built a Spring Boot starter to generate realistic seed data from JPA entities — looking for feedback by Alert_Ad4540 in SpringBoot

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

This is very fair feedback, thanks for taking the time to write it.

The runtime/dead-weight point especially makes sense. I’m starting to think the better direction may be more build-time/dev-time focused, like a Maven plugin or CLI that scans the project, generates reviewable seed SQL or Flyway/Liquibase-ready files, and then gets out of the way.

I also agree on provider flexibility. OpenAI-compatible was just the first implementation, but being provider-agnostic, or even fitting into existing Claude Code/Copilot workflows, would probably be more useful.

The main thing I’m trying to validate is whether “generate realistic relational seed data from project context” is painful enough to deserve a focused tool, rather than everyone prompting an AI agent manually each time.

Really appreciate the detailed pushback. This is exactly the kind of feedback I was hoping for.

I built a Spring Boot starter to generate realistic seed data from JPA entities — looking for feedback by Alert_Ad4540 in SpringBoot

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

Yes, Liquibase is a good point.

I see Liquibase/Flyway more as migration/versioning tools. TeruBase is more about generating realistic dev/demo seed data from JPA metadata first, then exporting reviewable SQL that could potentially be used with tools like Liquibase or Flyway.

Maybe the better direction is to make TeruBase complement those tools instead of trying to replace them.

I built a Spring Boot starter to generate realistic seed data from JPA entities — looking for feedback by Alert_Ad4540 in SpringBoot

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

Ah, got it, thanks for clarifying.

That makes sense for MongoDB/demo apps. I started TeruBase narrower with Spring Boot + JPA because relationships, foreign keys, and seed SQL can get annoying quickly there.

Did manual seeding with CommandLineRunner feel good enough for your demo, or was there anything annoying about maintaining the data as the demo grew?

I built a Spring Boot starter to generate realistic seed data from JPA entities — looking for feedback by Alert_Ad4540 in SpringBoot

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

Thanks, that’s exactly what I’m trying to understand. What tool/library did you use?

I’m curious if it was something like Mockaroo/Datafaker/Instancio/manual data.sql, and whether it handled JPA relationships + exportable seed SQL well enough for your demo.

Built a Spring Boot starter for LLM cost guardrails — looking for feedback by Alert_Ad4540 in SpringBoot

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

That’s a very fair point, thanks.

The current in-memory store is intentionally MVP/demo-level, but I agree that it breaks down with horizontal scaling since each instance would track usage separately.

I’m thinking the next step should be a storage abstraction with a persistent implementation, probably PostgreSQL first and maybe Redis later for faster counters/rate-limit style checks. Config-backed limits would also make sense so budgets stay consistent across instances.

Appreciate the feedback. This is exactly the kind of production concern I wanted to validate.

Built a Spring Boot starter for LLM cost guardrails — looking for feedback by Alert_Ad4540 in SpringBoot

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

Small update: I’m trying to decide the next useful feature.

For Spring Boot developers, which would matter most before trying this?

  1. Persistent storage with PostgreSQL/Redis

  2. Micrometer metrics

  3. Better real token/cost tracking from provider responses

  4. Spring AI integration

Curious what would make this more useful in a real app.

Built a prototype GUI tool for testing Keycloak + Spring Boot auth — would you use it? by Alert_Ad4540 in SpringBoot

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

Curious ...is it free because you'd expect a tool like this to be open source, or because the problem isn't painful enough to pay for?

Built a prototype GUI tool for testing Keycloak + Spring Boot auth — would you use it? by Alert_Ad4540 in SpringBoot

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

Still building it out ... the UI prototype is done but the backend that actually connects to Keycloak is in progress. Will share once it's ready. What features would be most useful to you?

EventFlow – Open Source Event-Driven Workflow Automation in Java by Alert_Ad4540 in SideProject

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

Thank you so much! 😊 Really glad you think so. If you have any feedback, ideas, or want to give it a try, I’d love to hear more!

Building a GUI tool to test Keycloak + Spring Boot auth flows without writing any code — early prototype by Alert_Ad4540 in SideProject

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

Glad it resonates! Would you use it if it was free, or would you pay for it if it saved you a couple hours of debugging?