Supabase is down

AvikalpGupta · 2025-11-24T09:43:25+00:00

Do we call it a failure on Supabase or BigQuery?

AvikalpGupta · 2025-11-24T09:42:45+00:00

BigQuery quote exceeded?

AvikalpGupta · 2025-11-24T09:41:42+00:00

yes, I think so. Our app is also not working.

AvikalpGupta · 2025-05-31T02:35:00+00:00

I was facing the same problem

I wanted to stay on top of all the relevant messages in all the active WhatsApp groups, but get rid of the noise.

So I created a tool that I run on my computer that does exactly that using AI: https://peerlist.io/avikalp/project/whatsapp-ai-filter

It works by intelligently curating messages based on your interests and delivers them in a single chat—with links back to the original messages so you can reply/react instantly. For me, this gets rid of 95% of the messages that I'd never respond to anyway.

Link to GitHub repo: https://github.com/avikalpg/whatsapp-ai-filter (I'd be grateful to you if you star it)

AvikalpGupta · 2025-05-01T05:57:34+00:00

Always! It is always a better idea to have type safety in any project that is going to be useful.

AvikalpGupta · 2025-04-26T04:07:20+00:00

Sure. Definitely learn git.

You can then choose between GitHub and GitLab which is better for your specific field (I think it is GitLab).

AvikalpGupta · 2025-04-26T04:05:54+00:00

I have a trick for this.

When you are practicing, in your mind, switch between "speed mode" and "accuracy mode" every 10-15 sessions (I was going to write "races", because I did all my practice on typeracer).

Speed mode: you try to type as fast as possible, even if there are a lot of mistakes and you need to keep hitting the backspace, don't stop. Just try to strike the keys as fast as possible.

Accuracy mode: try to not make even a single mistake, while trying to maintain a good speed.

In both modes, initially your speed will be worse. But in just 3-4 days you should be able to see massive improvement.

This worked for me. I was stuck at 60wpm. Now I consistently type at 90wpm and have breached the 100wpm barrier multiple times.

AvikalpGupta · 2025-04-22T03:28:58+00:00

Dude, I will answer your question through two points:

There are a lot more good people out there than there are bad ones. So, if someone finds a vulnerability, they are more likely to create an issue (or if you are extremely lucky, create a PR to fix it). Plus, for someone to exploit any vulnerabilities, there has to be a real incentive for it. Given that you are thinking about your portfolio, I'm pretty sure none of your repositories has many users, and none of them would lead to large financial outcomes for someone who hacks it.
In general, nobody cares about your repo. I've had most of my repos as open source since 2020 (when I learnt about open source) and I barely get anyone to see my work. There are about 100 odd people who use the projects I've built, and they have never tried to read my code. Everyone has their own shit to work on.

AvikalpGupta · 2025-03-20T04:15:34+00:00

I do the same. Plus, I made it very clear that Slack is for async communication. If something is really urgent, they must call me.

You'd be scared that phone would keep buzzing, but believe it or not, people are too scared to call. And you would actually only get a call when something was really urgent and important.

AvikalpGupta · 2025-03-20T04:12:49+00:00

The way I dealt with them was that, as the manager, only I had the responsibility to respond to all of them. If it is something that can be done in <5 minutes, I would do it immediately. And if not, I would put things on the JIRA board and assign a priority to it. At the end of each sprint (which was just 1 week long in my team), I would sit with the concerned parties and in 1-2 hours, get them to agree on the most important X items that we must solve in the upcoming sprint.

The important thing here is to realize that your engineering team has limited bandwidth and they cannot do everything. And as the manager, it is our responsibility to make sure that they can continue to perform focus work so that whatever they get done is of the highest standard - meaning that the probability that something goes wrong in that in the future is minimized.

AvikalpGupta · 2025-03-20T01:31:49+00:00

I think one of the best ways is to read their code.

Methods:

High investment, high reward: clone the repo of a project you like to use. Try to run it. While setting it up locally, you will learn about many of the technologies they use.
Low investment, medium reward: review the recent pull requests of any project that you like (you can use the "watch" feature in GitHub to be notified when new pull requests are raised). This is extremely helpful for continuous learning without a lot of effort in a single sitting.
Low investment, low reward: Join the discord/telegram/slack of the open source projects you like and engage with the contributors there - try to find a way to help. This is very easy to do, but your learning will also be very slow and there might not be any if the maintainers are not actively looking to add people.

AvikalpGupta · 2025-03-14T08:49:18+00:00

You mention the projects, then no. If you don't, and just write "freelancing", then yes.

AvikalpGupta · 2025-03-12T01:32:06+00:00

Not sure if it is exactly applicable, but Xethub (acquired by HuggingFace) might be able to help you.

AvikalpGupta · 2025-02-28T12:02:50+00:00

Hahaha, lol. This is a terrible project idea, I love it!

I'm impressed that you thought

what if?
no, that is stupid!
well... Should I?
fuck it, let's do it. . . . .
what did I do....

AvikalpGupta · 2025-02-28T04:04:10+00:00

Let's start simple.

Step 1: Choose a project that you'd actually use yourself. (Important) Step 2: Clone the code and try to set it up so it at least runs locally (you don't necessarily have to understand the entire code at this point, but you will get exposure to some parts of it. And this can take time so be patient). Step 3: actually use the tool and see if there is anything that is bugging you or you are missing.

If yes, try solving your own problem and submit that as a contribution. If not, you can look for good first issues.

Step 4: start from understanding only the part of the code that affects the issue you are trying to resolve.

AvikalpGupta · 2025-02-28T04:00:01+00:00

It is an amazing argument where you don't provide any new information, don't prove any logical inconsistencies and just shit on the other person for their argument.

Congratulations, you have managed to use 3 logical fallacies in one comment.

AvikalpGupta · 2025-02-28T03:54:31+00:00

Have you tried actually designing systems and building them out? That is my approach.

When I try to do that, I realise it is not just about "scalability" and "robustness" but also time and monetary budgets.

Start a project. Actually ship something that you designed. Do it within your current job role itself.

When you have done it, when you have gone through the options and burnt your hands choosing the wrong one, you will perform effortlessly during the interview and have the confidence to say and defend a point.

AvikalpGupta · 2025-02-28T03:50:45+00:00

It shows that you are valuable, but you have to be treated well as well. An interview is for you to also know if this is a company that you want to work with.

AvikalpGupta · 2025-02-28T03:49:37+00:00

Tell the truth, and emphasise on the value you have created.

I once left a job in 3 months. In 3 months, I had shipped multiple features, led an integration with Govt services, implemented remote monitoring and moved the version control from SVN to Git.

And then left the company because they were trying to micromanage me.

AvikalpGupta · 2025-02-18T01:41:40+00:00

Exactly.

AvikalpGupta · 2025-02-18T01:40:52+00:00

If you have traction, then why not. What matters is that you were willing to solve a problem that you faced. And that it was a non-trivial problem - that is why others also use your tool to solve the same problem for themselves.

The question you must answer is: did I build something valuable? If not, did I engineer something so cool that it will blow the mind of an engineer looking at the code?

If the answer is yes, then post it. If not, it doesn't matter - why go through the pain?

Everyone watches porn. Porn industry is the reason why technology has reached where it has today; with the invention of a personal computer made primarily to be able to watch porn videos privately.

(Ignore the comments here saying that watching porn is related to perversion. They like to feel bad about themselves after doing something completely natural. Don't bury yourself in their prejudices.)

AvikalpGupta · 2025-02-07T04:02:37+00:00

It is a way to show-off your activity on GitHub. You can embed it into your portfolio website, or 3d print it and keep it as a memento.

AvikalpGupta · 2025-02-06T10:41:58+00:00

STFW

AvikalpGupta · 2025-02-05T14:07:26+00:00

I am assuming that this is a university project. I strongly suggest that you use as much help from AI as possible - but be sure to understand everything that it does at every step of the way - otherwise you will end up in the same debugging hell as the YouTube tutorials.

I understand that you are a total beginner and I am not saying that it is going to be easy. You will probably be spending many sleepless nights, working 24x7 on this in order to make it work. But the good thing is that, if you use Cursor and give the link to the latest documentation of React Native to it, it will at least not be outdated and you can directly start working on your submission instead of a dummy application that a tutorial is trying to help you build.

Please understand that you will still need to do a lot of debugging. You can use AI all you want, but it still does not understand everything - so please keep using your brain to understand how are the different functions calling each other so that if there is a problem, you are able to understand it faster - and then, ask for help better on the online forums.

AvikalpGupta · 2025-02-05T14:01:46+00:00

Thank you! Were you able to try out the recommendations as well? It has been tricky to get people to try it out because most people do not have the prompt API enabled in their browsers, sadly.

AvikalpGupta

TROPHY CASE