1.3 What is the problem? Suppose we are…
In short: Suppose you are on a team that ships Instagram-style features — feed, stories, likes.
Suppose we are building Instagram (like updates)
Suppose you are on a team that ships Instagram-style features — feed, stories, likes.
- Monday — a developer finishes “show a new badge on the profile.” It works on their laptop.
- They say “done” in chat and hand a zip / build folder to someone else.
- Wednesday — the operations person (server-side) is busy with another outage. They copy the files to the production server when they get time.
- Laptop had one library version; the server has another. Real users see a broken profile page.
- Friday night — support floods in. Developer: “It worked on my machine.” Operations: “I only put what you sent.” Nobody is sure which build is live. Blame starts.
That fight — app developer vs server-side operations — is why companies invent DevOps habits.
Suppose we are working at Netflix and we are giving updates
Suppose you work at Netflix and your team must push updates often — new rows on the home screen, bug fixes, small UI changes.
- If every update needs a manual copy to servers by one operations person, Netflix cannot ship safely many times a week.
- One bad manual step and millions of viewers feel the break.
- So they need: shared Git history, automatic tests on every change, the same package on every server, and a repeatable deploy path — not “ask that one person to copy files tonight.”
Big streaming apps survive on small, frequent, automated updates — that is DevOps thinking at scale.
Suppose you are working in Infosys (or a similar company) on a client project
Suppose you are working in Infosys (or any big services company) on a client banking / retail app.
- Your developer team is in one city; the client’s operations / infra team owns the servers.
- You email a build. They deploy on their calendar. Environments differ (dev laptop ≠ client UAT ≠ production).
- Release day becomes a war room: wrong config, missing file, “who approved this?”
- The client does not care about your laptop demo — they care that production works.
DevOps skills matter in jobs like this because you must speak both languages: code change and how it lands on the server safely.
Ravindra Bagale's Tip
Khup students jump to tool names — Docker, Jenkins, Kubernetes — and still cannot answer: “What is operations?” and “What was the problem between developer and server-side person?” Interview madhe pahile real example sanga: Instagram-style update, Netflix frequent release, Infosys client server. Mag DevOps loop. Mag ek tool tumhi practice kele. Lakshat theva.
Practice task
Retell one suppose story in six spoken lines (record yourself once). Name developer, operations, the broken moment, and one habit that would have helped.