Lessons Learned: My First Self-Employment Contract Journey

My first glimpse of being self-employed was tough. Let me set the premise: I was a first-year student at the University of Irvine and a research assistant at the Language and Learning Analytics Lab with Nia Dowell. I loved academia and dreamed of writing a research paper, but then came an opportunity referred by Amin, one of the researchers in my lab. Love you, man ❤️. He knew of another lab needing a software developer on a contract basis, and at that moment, I got a taste of entrepreneurship.

I took the chance, even though my knowledge was lacking. I said “Yes” to everything. I know it’s not right to tell white lies, but I wanted to secure this contract so badly. After a lot of negotiating, the project scope grew by 3000% from the initial estimate, and the contract reflected that. I was thrilled, but this was just the beginning of the headaches I would endure.

Being Young and Naive

I pieced together a tech stack from my side projects: React JavaScript, Google Cloud Platform’s Firebase, and Vercel for deployment. I thought this was going to be simple—boy, was I wrong. Since we only had a verbal contract, the scope and demands kept growing. This was my mistake. As my first contract, I was timid and afraid to bring up issues. Every meeting, I would show my progress, and every meeting, the team would add more requirements: special student security protocols, different data structures, design changes, etc.

Scope and Pay Spiraling Out of Control

As the scope grew, so did the pressure. Deadlines became increasingly unrealistic. I found myself working around the clock. To speed up my progress, I outsourced some of the work. This allowed me to focus on architecting the systems and integrating everything, while the outsourced team handled the coding. This decision, though costly, was necessary.

The process was exhausting. It affected my relationships and my non-work life. I was constantly stressed, but I learned invaluable lessons about managing international teams, closing deals, and navigating work politics. Despite the chaos, I began to figure out a formula for quickly and cheaply deploying software projects.

Lessons Learned and Gratitude

Even though the team was initially confused about their goals, and I often felt lost, I am grateful they took a chance on me and entrusted me with their big research goals. Their mission resonated with me and taught me resilience and problem-solving on a whole different level. This experience made me realize that growth often comes from the most challenging and uncomfortable situations.

I’ll always remember this first contract as a baptism by fire, one that forced me to grow up fast and learn the ropes of entrepreneurship. It was messy, stressful, and overwhelming, but it was also the beginning of my journey as a self-employed software developer. Now, with these hard-earned lessons, I’m ready for whatever comes next.

---

Key Takeaways for Aspiring Entrepreneurs

1. Speak Up and Set Boundaries: Establish clear terms from the start. A verbal agreement is a recipe for scope creep and unrealistic demands.
2. Outsource Wisely: If you’re in over your head, find skilled help. It’s an investment in your sanity and project success.
3. Learn from Every Experience: Even the toughest projects teach you valuable lessons that shape your future career.
4. Balance is Crucial: Don’t let work consume your life. Maintaining relationships and personal health is key to long-term success.
5. Embrace the Challenge: Tough projects build resilience and problem-solving skills. They prepare you for future opportunities.

The Controversial Truths of Entrepreneurship and Coding

Entrepreneurship isn’t glamorous. It’s messy and full of failures. Coding isn’t just about writing beautiful code; it’s about dealing with constant changes and unrealistic demands. Most of the time, your biggest lessons come from your biggest mistakes.

Remember, every setback is a setup for a comeback. Share your thoughts and experiences below—what’s the toughest project you’ve ever tackled? Let’s talk about it!