Pritam

Recently, I deployed an app on the App Store and it got rejected because we weren’t using Apple’s In-App Purchase system. If your iOS app has digital subscriptions, Apple generally requires IAP, meaning around 30% of the transaction goes to Apple. That can obviously feel painful for some founders. One alternative is to have a website where users manage their plans and subscriptions. The iOS app can then focus on the actual product and the user’s account. For example, “Upgrade Plan” can take users to your website to manage their subscription. It’s not the cleanest solution, and Apple’s rules around this can be nuanced. But it’s an architecture worth considering depending on your app and the applicable App Store rules.

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

Started my open-source journey by exploring the Formbricks codebase. Took some time to understand the platform, found a few areas for improvement, and will be opening a PR soon. – at Bardhaman, India

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.

Mostly the reason why Databases uses B+ Tree? in this post i am saying about the case when we are just storing things sequentially on disk vs using an Index structure ? in normal sequential disk storage when we do any insert operation we can sequencially insert things but can not insert things between two or three things proficiently now the question comes why? suppose your disk blocks (pages) are full.. now suppose we need to put any thing in between 1 and 2, the database has to physically shift all the rest of the data down the disk to make space. this is an O(N) operation and it is terribly slow.. also one more thing without indexes it will be hell slow.. but wit b+ tree struture that would be great great fast.. now suppose anyone want to update any row of the db which is sequentially on the disk storage we need to do a proper linear search over the disk storage to find the row then update that that should also take huge huge time... range thing is not also can be done efficiently with just sequential disk storage right, you would have to read the whole disk. but b+ trees link leaf nodes so its super fast. so in the next post i will explain the deep architecture with diagrams of the b+ tree using

Key takeaways from the recent video of @kirat_tw👇 Even in 2026—and going forward—core CS fundamentals are non-negotiable. You can’t survive or land a solid job without them. Seeing a lot of people doing only “vibe coding”: – No understanding of frameworks – No idea what’s running under the hood – Just building random projects hoping for jobs That approach won’t work in this competitive market. AI is a tool, not a replacement. 👉 Use AI to train yourself first 👉 Then use it to build better If you skip the basics, AI won’t save you. youtu.be/XO8SbDVJVyo?si=g6ID…

Some security tips for vibe coders 👇 Most vibe coding apps are built on Supabase or Firebase, and often focus more on features than security. Here are a few must-follow tips to keep your app secure: 👉 When using Supabase or any backend, make sure RLS (Row Level Security) is properly configured. Since you’re calling the DB directly from the frontend, this is critical. 👉If your app has premium features, don’t store them directly in the user table. With RLS allowing users to modify their own data, they could increase limits and abuse your system. Always add rate limiting (including IP-based limits). Even if RLS is misconfigured, this prevents large-scale abuse. 👉Set a price/billing alert (available in Supabase). It can shut things down before costs spiral—better than waking up to an $80,000 bill.

Why Every Cloud VM Needs NGINX ? When you deploy apps on a VM, only port 80 (HTTP) and 443 (HTTPS) can handle public traffic. Now imagine: App 1 → runs on 3000 App 2 → runs on 5000 App 3 → runs on 8000 All need HTTPS. Only ONE service can bind to port 443. So how do multiple apps run on one VM? 👉 Enter NGINX NGINX: • Runs on port 80 & 443 • Routes traffic based on domain • Sends requests to the correct internal port • Handles SSL via Let's Encrypt • Adds security, caching, compression Example: app1.com → NGINX → localhost:3000 app2.com → NGINX → localhost:5000 One VM. One public port. Unlimited apps. – at Bardhaman, India

Made my first MCP server for the mcp hackerthon and its a great excitement to see things working..dont with the phase 1 implementation.. It can now programmatically fetch EC2 states and CloudWatch metrics directly into an AI context. @WeMakeDevs #2Fast2MCP @archestra_ai