One2N

We often get asked about why we are called One2N well, here’s @chinmay185 & @jdk2588 sharing the story. Our mission: help you go from 1 to N, wherever you need scale. Watch the video to hear it straight from the founders!

When do you actually need a platform team? Not "what tools should we use", but when, why, and how to build the culture around it. New One2N Bits with @jdk2588 and @techvatsa covers exactly that 👇 youtu.be/QnerxCpZg8c

Batching your I/O is solid advice -- until you enable the wrong kind of batching. One of those "we broke it, then fixed it" stories from our engineering team. one2n.io/blog/shooting-…

Follow @One2NC so you don’t miss registrations for the next mitramandal.ai meetup.

To close the morning, Udayan Kanade from spoke about a system that turns natural language into persistent, inspectable meaning representations for use cases like knowledge bases, querying, analysis, and causal questions. This session will stay offline for now.

ICYMI: Talks from mitramandal.ai Episode 2 (Feb 21, Pune) are now live on YouTube mitramandal.ai/past-events

Struggling with AWS Glue costs? See how One2N migrated a fintech to self-hosted ClickHouse, cutting analytics infrastructure costs by 70%. read more: one2n.io/case-studies/m…

I recently had a call with a CISO (they booked via One2N's SRE services page) about understanding our SRE and DevSecOps services. They needed help with DevSecOps, reliability and infrastructure automation. I talked about how we approach such kind of work at @One2NC. In essence, I covered that: - we do a quick technical discovery - come up with a roadmap of improvements/suggestions from our side - work closely with you to prioritise these as per business impact I didn't have any powerpoint slides to show, no "sales pitch" to give. Only 1:1 conversation to understand their use case and challenges they are facing. They were so happy with the approach and the conversation that they mentioned - "You are the first person who's actually interested in understanding and solving our problem. I am so glad you didn't start with a powerpoint". Here's how we operate at One2N when working with our customers: - Talk to people as people, it's that simple. Don't "sell". - Care for the problems and business impact. This is what separates us from a bunch of other _vendors_. - Business happens on trust and our job is to demonstrate the trust with the people we do business with. If you're an engineering leader looking to work with good engineering vendors who care, reach out to me. My DMs are open.

@_svs_ @_svs_ you would find this interesting. In @One2NC 's 3rd cli heroes meetup at Blr, we presented an interesting scenario how installing kiro coding agent broke tmuxinator and how we optimized zshrc. Skip to the 8th min as initially we intro tmux - youtu.be/YugQ3uv6GU0?si…

We have released @One2NC 's Command Line Hero's 3rd meetup videos. Here's me debugging an interesting scenario around an AI coding agent quietly breaking my tmuxinator setup, how we debugged it and optimized zshrc along the way. Hands on demo - the way it's meant to be. 1/2

All set for Mitramandal [dot] ai meetup tomorrow at @One2NC

RSPV: luma.com/f3j9ssuk

This is exactly the kind of conversation we like to host at One2N. Engineers sharing how they wired AI into real products, what failed on the way, and what they would do differently now.​ Ep2 of mitramandal.ai is just 2 days away. RSVP on Luma if you haven't already

mitramandal is an AI meetup where engineers share how they've actually integrated AI into their daily development workflows. learn more: mitramandal.ai

Hi everyone! Join us for the second episode of mitramandal.ai It's happening on Feb 21, 10 AM - 12:30 PM in Pune, and registrations are now open on Luma. RSVP: luma.com/f3j9ssuk

Most local microservice setups fall apart once you have a few services talking to each other. We use Postman mock servers as drop in replacements for dependent APIs so a single service can be built and tested without running the whole stack. Details: one2n.io/blog/mock-apis…

Everybody wants to learn. Very few want to study. We are hiring engineers who "like" to study. After a recent technical interview, I asked the candidate: "Are you genuinely ready for learning?" Because here's what learning actually looks like in One2N: - Tech sessions every Thursday for 6 years (300+ sessions recorded) - Exposure to building and designing systems end to end at scale - Asking questions that might feel basic We're training software athletes. Are you ready to be an athelete? If yes, apply at @One2NC careers.

Last week at @One2NC, we conducted an Architecture Kata session. The goal was to practice architecture and system design, given a real customer problem. We discussed - what is an "architecture decision" and why it matters? - how to decide which type of database to use, for a given use case - how to think about software architecture in a structured manner We are planning to open up these Kata sessions to the wider audience (as a meetup). If you're a Senior/Staff/Principal engineer who wants to participate, leave a comment below and I'll get in touch with you soon. As I keep saying - "You can't learn swimming by reading a book or watching videos, you have to get into the water". Similarly, the only way to get better at system design and software architecture is to actually pratice building real systems. You'd get that practice by participating in these Architecture Kata sessions.

Most “we adopted OTEL” stories stop at config. This one from @sanket_rajgiri gets into the gotchas of OTEL collector processors in Kubernetes, what actually broke in prod, and how to handle them without blowing up costs. Read more: one2n.io/blog/the-gotch…