Modernizing Processes

I know Harsh since we were 4 year old, we went to playschool, primary school, secondary school together and then he's been the 2nd employee who joined the company full time.

And the funny part is, for the majority of our life together, Harsh has been a bully to me.
He was always the funny guy in the room while I was always the timid one. Till school days, I had a love-hate relationship with Harsh.

But while he was a bully to me, he always had a big heart. He would trouble me enough to enjoy it himself but then stop when it got to a point where I would get disturbed by it.

Somehow he was always around in everything! I remember he was the first person in our group to start making money.

He would play CS Go for 12-14 hours a day and every other week win some gaming tournament and make a bunch of money and then spend it all on a treat when the group met.

Also, if Harsh is on the table, nobody would need to open the menu card. It was assumed that Harsh would place the order always!

I remember clearly that right before the Covid lockdown, Harsh decided to come back home from San Francisco after a 4 year long stay for his game design course. I had picked him up from the airport. Back then I was pursuing my MBA and MP was just conceived.

Covid lockdown extended indefinitely and Harsh couldn't go back and fate would have it that I need trustworthy people with me and Harsh joined MP - not with a role, not with any direction. Just with a strong work ethic and motivation to do something big together!

Over the years, he wore so many hats at MP, I can't even count. He tried many things, failed in some, excelled in others and eventually figured out what he does best! Harsh literally mirrored my thought process and helped me build the culture, the SOPs, the core operating systems etc. He would be my first call always when we had to tweak anything for the internal system.

In the last year, he stepped up even further. He internalized MP to be his company and with such passion and rigour chose to fully replace me while I could focus on my family business.

Continued in the 1st pinned comment.

What database should I be using for my Glide app? We get this question very often from our clients, and hence we made this quick post.

Here's a list of databases that Glide currently offers and 1 pro and 1 con for each:

1️⃣ Google Sheets:

Pro: The easiest to adapt and super flexible for all kinds of integrations and triggers.
Con: Becomes slow after scaling beyond 20k records.

2️⃣ Glide Tables:
Pro: Native to Glide. Fastest and most robust database to build if starting from scratch.
Con: Time-based triggers cannot be created. (possible with Google Sheets)

3️⃣ Glide Big Tables:
Pro: Can scale up to 10M records of data.
Con: Limitations with computed columns. Good enough for "read only" apps that don't need summarized info.

4️⃣ Airtable:
Pro: Much better interface than the rest.
Con: Expensive (should choose this only if you are already using Airtable somewhere.)

5️⃣ Microsoft Excel:
Pro: Universal database, easy to adopt.
Con: Microsoft ecosystem is a little more difficult to integrate with. (personal opinion)

6️⃣ SQL (newly introduced):
Pro: The real "software" database.
Con: Higher complexity

That being said, this is a fantastic variety of backend databases to use with Glide to build super powerful internal apps from your existing databases.

Are you still using an Excel interface for your operations in this day and age?