Ravelin Dev

Hello, I am Rudy Ravelin I am a full stack web developer and I love technologies base in Kirkland WA. Founder of

[Ravelin Dev @DevRavelin]

🐍 Day 2/100 #100DaysOfCode Completed Day 2 of Angela Yu's bootcamp! Dove deeper into Python data types, mathematical operations, and string manipulation.

💸 Built: Python Tip Calculator

Day 2 ✅

[Ravelin Dev @DevRavelin]

��� Day 1/100 #100DaysOfCode

Started Angela Yu’s Python Bootcamp today!

Learned variables, data types, strings & user input.

🎸 Built: Band Name Generator

Day 1 ✅

#Python #CodingJourney

[Ravelin Dev @DevRavelin]

Session 6 complete.

No code today—and that's okay.

We designed the entire Invoice architecture before writing a single line of code.

Good software starts with understanding the business.

#buildinpublic #nodejs #mongodb #softwareengineering

[Ravelin Dev @DevRavelin]

Session 5 building InvoSwift 🚀

Today I designed and tested the first database models using MongoDB + Mongoose.

✅ User model
✅ Client model
✅ Relationships between them
Starting to think like a software engineer instead of just writing code.
#buildinpublic #nodejs #mongodb

[Ravelin Dev @DevRavelin]

@solrewards USA(3) - Belgium(2)

[Ravelin Dev @DevRavelin]

🚀 Today's progress on InvoSwift wasn't about writing code.

It was about designing the business.

• What belongs in a Client
• What belongs in an Invoice
• Why data ownership matters
• How to avoid duplication while preserving history

Good software starts with good design.

[Ravelin Dev @DevRavelin]

I just connected a real database to my SaaS backend.

Now InvoSwift has:
• Express API
• MongoDB database
• Mongoose integration
• Full backend + persistence

From “idea” → to a working system in 4 sessions.

Next: building real features (users, clients, invoices)

#MERN

[Ravelin Dev @DevRavelin]

@MrBeast 250

[Ravelin Dev @DevRavelin]

Session 3 of building InvoSwift

Refactored my InvoSwift backend into a proper structure:

✔ Routes layer
✔ Controllers layer
✔ Clean separation of concerns
✔ /health API still working

Now building like a real production backend.

#buildinpublic #NodeJS #Express #SaaS

[Ravelin Dev @DevRavelin]

🚀 Session 2/100Today

I laid the foundation for the InvoSwift backend.

✔ Express server
✔ First API endpoint
✔ Real-world debuggingSlowly turning an idea into a product.

#buildinpublic #SaaS #NodeJS

[Ravelin Dev @DevRavelin]

🚀 Day 1 building InvoSwift

A mobile-first SaaS for home service contractors (plumbers, HVAC, etc.)

Today: no code — just foundation
• GitHub setup
• Repo structure
• Sprint planning
• Dev workflow

Building in public from scratch.

#buildinpublic #SaaS #100DaysOfCode

[Ravelin Dev @DevRavelin]

@MechaNews_ The Netherlands (5) - (2) Morocco

[Ravelin Dev @DevRavelin]

The strongest contracts aren’t always the longest.

They’re the ones where both sides clearly understand the terms.

Clarity builds trust.

Confusion creates problems.

https://t.co/PvXZTZZN53

English • Spanish • French • Haitian Creole

[Ravelin Dev @DevRavelin]

Most people review contracts with one question:

“Is this okay to sign?”

The better question is:
“What could hurt me later?”
That’s the mindset behind Termslify.

English, Spanish, French & Haitian Creole.

https://t.co/PvXZTZZN53

[Ravelin Dev @DevRavelin]

Contracts rarely fail because people ignored the title.

They fail because of one overlooked detail buried deep in the document.

That small detail can become a big problem later.

That’s why I’m building Termslify.

https://t.co/PvXZTZZN53

[Ravelin Dev @DevRavelin]

Back to fundamentals.

Rebuilt a JS Library app and focused on how it works, not just that it works.

Live: https://t.co/l8tp5lSVqw

Classes, DOM, state, refactoring.

#JavaScript #WebDev #100DaysOfCode

[Ravelin Dev @DevRavelin]

The most dangerous contract terms are usually the ones people skip because they “look standard.”

A lot can hide behind normal-looking language.

That’s one of the reasons I built Termslify.

English, Spanish, French & Haitian Creole.

https://t.co/PvXZTZZN53

[Ravelin Dev @DevRavelin]

Tuesday morning thought:

A signature takes seconds.

Understanding what you signed can take months — especially when problems appear later.

That’s the gap I’m trying to solve with Termslify.

https://t.co/PvXZTZZN53

[Ravelin Dev @DevRavelin]

Monday reminder:

The cost of a contract mistake is usually invisible at the beginning.

People only notice it later:
when money, ownership, or obligations become real.
That’s why I’m building Termslify.

English, Spanish, French & Haitian Creole.

https://t.co/PvXZTZZN53

[Ravelin Dev @DevRavelin]

Saturday afternoon thought:

The people writing contracts usually understand them better than the people signing them.

That imbalance matters.

Built Termslify to help close that gap.

https://t.co/PvXZTZZN53