I always assumed storing sensitive values in Kubernetes Secrets was a safe approach. Recently learned that Kubernetes stores secrets in etcd in base64, which means they are not encrypted unless you enable encryption at rest manually. Anyone with etcd access can read them in plain

I have been learning Helm for a week and it feels like a serious upgrade from writing raw Kubernetes manifests. Charts, templates, and values files make deployments clean and scalable. Helm is already proving super useful for managing similar services across environments.

The SaaS platform I am building at my company is very niche to insurance. The product is useful for a very limited audience who want to generate insurance quotes and share them with their customers. What would be the best channels or mediums to reach potential users for a niche

Sometimes a pod in k8s needs to prepare its environment before the actual container starts. That is where Kubernetes initContainers come in. Init containers run first and can handle tasks like running database migrations, seeding initial data, waiting for dependent services, or

I still don't understand why people wear analog watches to the gym. Digital watches make sense since they track something, but wearing an analog watch while lifting feels like compromising wrist movement just for fashion.

Spent the last four days building Helm charts and finally seeing everything come alive is real fun. After moving to Helm, deployments have become so easy that services can go live in under five minutes by just tweaking values. Watching the whole pipeline sync automatically with

X dropping the premium price to 89 rupees for the first month feels like betrayal because I literally bought it for 427 just two days ago 😭😭

For our enterprise plan we already have a fixed price internally, but I am unsure whether we should display it on the website or ask users to contact us first and share the pricing after a call. What do you think is the better approach for enterprise SaaS?

One thing I learned while designing subscription pricing is that not every config belongs in a separate database table. When the structure keeps changing, rigid schemas become a bottleneck. For dynamic configs it is far more practical to store them as JSON and bind them to a

Actually we decided to take this route. After signup users will be able to configure their plan based on their team size and purchase it directly without any manual intervention. This makes the SaaS run in true autopilot mode. I am building this right now and it should be live

Working with interns can sometimes feel slower than doing the task yourself. Explaining things, reviewing work, guiding them through the basics takes time. But this is how you build real leverage. When you teach someone well, you are not just helping them grow, you are creating a

One year at the startup and this contribution graph is the summary of everything I worked on. Frontend, backend, infra, microservices, tooling, debugging, firefighting, learning. The best thing about startups is that you never write the same kind of code twice.

Is it normal to sleep 9–10 hours a day? Some days it feels like I’m taking care of my health, and other days it feels like I’m wasting precious time that I could use to build something for my future. Curious how others think about this.

🚨 We are hiring a Software Development Intern 🚨 Bangalore • Onsite • WFO If you want real world experience instead of just reading about it, this is for you. At OneAssure, we are building the future of InsurTech and looking for someone who is hungry to learn and ready to

Going home on Friday knowing the tasks aren’t done hits different. You keep telling yourself, ‘It’s fine, I can finish it anytime before Monday.’ Deep down, you know Sunday night is doing all the work 😅

Finally submitted the iOS app for review after going through all the strict checks. Some of them really feel unnecessary, but this is Apple so you just follow the rules. Now waiting for the review results and ready to fix whatever they send back. Fingers crossed. 🤞🤞

One webview app submission later and suddenly I feel like an iOS developer 😁

I'm stuck with app reviews on both Apple and Google Play. They require login credentials for testing, but our app only supports OTP based login. How do you usually handle this? Has anyone faced this before and found a good workaround? Would love some guidance.

Received a rejection on my first iOS app review. Not disappointed at all, feels like a win since this is my first attempt at iOS development. Will fix and resubmit.

Today we hit a cost problem in our Azure K8s setup 🤔 We were using Application Gateway for Containers for load balancing. Fixed cost. Getting expensive. So we decided to split the work: → L4 load balancing (TCP/UDP) - keep in Azure (cheaper) → L7 load balancing (HTTP routing)