Full Stack Engineer
Kolkata, India
Joined March 2020
- Tweets836
- Following246
- Followers124
- Likes3.5K
Spawning 20 agents for making the changes in 20 projects is crazy..but you know what more crazy.. checking all of themselves code and review them manually...So as far as we can the Writing code part is Solved by AI.. – at Bardhaman, India
AI can fix bugs. But can I trust it to ship code?
My agent finds and fixes issues automatically. I still spend hours reviewing its code before merging.
In MNCs: Staging → Production.
In startups: Production → Panic → Staging. 💀
You ship first, learn why staging exists later.
Saw the Video about jev @typesafeai and it's a great one i already got a use case in our clients products for it ..Maybe will discuss with the client later when it will be available publically
youtu.be/cidPApHyXhI?si=9nGx… – at Bardhaman, India
I Go through Formbricks Codebase and find a criticcal issue of their webhook architecture..made an architecture change put an pr also raise an issue got reply from them that they are not currently accepting community contribution so my pr did not merge but what feels special is that they acknowledged my issue and thinks about my proposed architecture .. Sometimes Win is not Merging pr communication and acknowledgement also matter..
Issue link:- github.com/formbricks/formbr… – at Bardhaman, India
great podcast for solo developers who wants to build saas in the ai era ...
youtu.be/FkuQR-mTk1s?si=ZjJM… – at Bardhaman, India
We built the app for mobile.
But Apple reviewed it on an iPad — and that’s where we got rejected.
We built the app using Expo, and our target audience was mobile users, so our development and testing were mainly focused on mobile devices.
The problem? We hadn't explicitly disabled tablet support in our app.json, so Apple tested the app on an iPad and found UI overlapping issues.
Initially, I thought we would need to spend weeks making the entire app properly responsive for iPad.
Then I found a much simpler solution: supportsTablet: false.
After adding it to app.json, the app opened on the iPad using the mobile layout instead of trying to behave like a tablet app.
The overlapping issues were gone. One configuration change solved what initially looked like a much bigger UI problem.
The lesson: Don't assume that not targeting a device means it won't be tested.
Before rewriting your UI, check your platform configuration first. Sometimes the fix isn't more code — it's one line in app.json.
ALT Ios status approved
Every developer wants to scale as if he or she serves millions of users from the very beginning.
But this is not the case.
With 500 to 1000 active users, there will be no need for Kubernetes, microservices, and complex cloud infrastructures.
PaaS deployment on platforms such as Render, Railway, DigitalOcean, or Vercel will do the job just fine.
The real problem in your situation is not the lack of a complex infrastructure.
It's the quality of your code.
For example, if a user enters your inventory page, ideally, there should be one request made. However, poor code structure may lead to the making of 3 to 5 requests.
Multiply this by a hundred users.
Then, you have your bottlenecks not because of choosing PaaS over Kubernetes.
At the initial stage, you must pay attention to the following things:
Code quality;
Removal of unnecessary requests to the API;
Optimal database queries;
Simple architectural solutions.
Infrastructure should grow along with your application, not your ego.
And still I failed to give it time..But understand that to show value to the tech community you must have some great products of your own .. obviously...as you can't show the org Project for NDA
Hectic day so second energy drink of the day...btw thanks @vanshdevx sir for sponsoring...😁..
