DEV Community: Ricardo Batista

🚀 Launching FidForward! 🚀

Ricardo Batista — Mon, 08 Jul 2024 16:54:15 +0000

Today, Bernardo and I are excited to launch FidForward in private beta!

We're looking for companies with 10-50 employees willing to pilot the next generation of performance management.

With two pilot programs already running successfully (achieving a 30-50% improvement in eNPS), we’re eager to expand FidForward to more companies to validate these results further.

If you’re a founder seeking to implement performance management or a larger company aiming to elevate your current system, please reach out to me!

🔗 Learn more about FidForward at FidForward.com

We were tired of bureaucracy, so we built an opensource repo for the best guides

Ricardo Batista — Sun, 23 Jun 2024 21:09:11 +0000

Today we are launching Tramitit, a shared database on getting all those poor-UX local procedures done in a much simpler way!

How it works: The community provides detailed walkthroughs on every possible bureaucratic process you might go through.
For the community by the community: The content on this website is curated, verified, and rated by the community.
Welcoming providers that can help our users: Although our guides are as simple as possible, users may still prefer to delegate tasks to a curated provider.

We are in a bit a chicken & egg problem: for the traffic to pick up and have contributors, we need to start by adding some content - some of which we have already gone through and fixed it, other not yet there. We will get there over time, and work with providers that can also bring the quality up.

You can find our GitHub repo here, where you can contribute as well!
Our website is also open-source, so feel free to add anything.

Getting started with Open SaaS

Ricardo Batista — Sun, 21 Apr 2024 07:34:17 +0000

When building Article Generation and Meeting Reminders, I decided to get started as fast as possible. So I looked for a free boilerplate and stumbled upon Open SaaS, which used YC-backed Wasp. It is a full-stack React + NodeJS + Prisma that takes 8 hours to get started with.

Their documentation is brilliant, and great support over Discord. I decided to list here the full walkthrough on how to set up the development environment so that it is a simple copy-paste for you.

For frontend deployment, I used Netlify (for the generous free package) and the recommended fly.io for server + database (also cheap package).

Run development commands

Start development database:

cd app && wasp start db

View development database in Prisma:

wasp db studio

Start development app:

cd app && wasp start

Start development blog:

cd blog && npm install && npm run dev

Run frontend deployment commands

Locate the folder:

cd .wasp/build/web-app

Install dependencies:

npm install && REACT_APP_API_URL={your-server-URL} npm run build

Deploy preview:

netlify deploy

Deploy to production:

netlify deploy --prod

Every time there is a Wasp app rebuild (with wasp build), it will remove your .wasp/build/ directory. Until the GitHub issue is fixed, you need to update netlify.toml’s publish line to:

  publish = ".wasp/build/web-app/build"

Run backend & db deployment commands

Locate the folder:

cd .wasp/build/

Deploy preview:

flyctl deploy --remote-only --config ../../src/shared/fly-server.toml

Every time there is a Wasp app rebuild (with wasp build), it will remove your .wasp/build/ directory. That’s why there is a copy of the file in app/src/shared/.

Run blog deployment commands

Locate the folder:

cd blog

Build the app:

npm run build

Deploy preview:

netlify deploy

Deploy to production:

netlify deploy --prod

Good luck with building, hopefully it will be faster now!