--- title: "Kartik Budhlakoti (@kartik-budhlakoti) | Hashnode" description: "B.Tech CS student documenting a structured DevOps learning journey." url: "https://hashnode.com/@kartik-budhlakoti" --- @kartik-budhlakoti # Kartik Budhlakoti @kartik-budhlakoti · Delhi, India · Joined May 2026 ### [The Project Behind These Posts: Medical Integrity System](https://kartikbudhlakoti.hashnode.dev/the-project-behind-these-posts-medical-integrity-system?utm_source=hashnode&utm_medium=feed) How I built a FastAPI learning project with patient access rules, file integrity checks, automated tests and Docker deployment—and what went wrong. 9 min read · [kartikbudhlakoti.hashnode.dev](https://kartikbudhlakoti.hashnode.dev/the-project-behind-these-posts-medical-integrity-system?utm_source=hashnode&utm_medium=feed) [3](https://hashnode.com/posts/the-project-behind-these-posts-medical-integrity-system/6af0cb964b0c43bd3011e349) [1d ago](https://hashnode.com/posts/the-project-behind-these-posts-medical-integrity-system/6af0cb964b0c43bd3011e349) ### [Month 7: The Plan Changed. The Design Did Not.](https://kartikbudhlakoti.hashnode.dev/month-7-the-plan-changed-the-design-did-not?utm_source=hashnode&utm_medium=feed) A credit-card requirement changed my deployment plan, but an isolated S3-compatible storage layer kept the rest of the project unchanged. 3 min read · [kartikbudhlakoti.hashnode.dev](https://kartikbudhlakoti.hashnode.dev/month-7-the-plan-changed-the-design-did-not?utm_source=hashnode&utm_medium=feed) [Oct 1](https://hashnode.com/posts/month-7-the-plan-changed-the-design-did-not/6abe5de37b492d18ebbb1e12) ### [Month 6: Two Times I Should Have Kept Reading](https://kartikbudhlakoti.hashnode.dev/month-6-two-times-i-should-have-kept-reading?utm_source=hashnode&utm_medium=feed) Two maintenance tasks showed me why generated migrations and newest dependencies need a second look before they reach production. 4 min read · [kartikbudhlakoti.hashnode.dev](https://kartikbudhlakoti.hashnode.dev/month-6-two-times-i-should-have-kept-reading?utm_source=hashnode&utm_medium=feed) [Sep 3](https://hashnode.com/posts/month-6-two-times-i-should-have-kept-reading/6a99805b972518a1e388514f) ### [Month 5: Working Was Not the Same as Correct](https://kartikbudhlakoti.hashnode.dev/month-5-working-was-not-the-same-as-correct?utm_source=hashnode&utm_medium=feed) Two backend bugs taught me that code can look fine, pass tests, and still be quietly wrong. 4 min read · [kartikbudhlakoti.hashnode.dev](https://kartikbudhlakoti.hashnode.dev/month-5-working-was-not-the-same-as-correct?utm_source=hashnode&utm_medium=feed) [Aug 3](https://hashnode.com/posts/month-5-working-was-not-the-same-as-correct/6a705012d29b51717f32a8e6) ### [Month 4: Two Hash Functions, One Bug, and Less Time Than Usual](https://kartikbudhlakoti.hashnode.dev/month-4-two-hash-functions-one-bug-and-less-time-than-usual?utm_source=hashnode&utm_medium=feed) A CS student's honest account of Month 4 — two hashing algorithms, one database default that wasn't, and less time than planned. 4 min read · [kartikbudhlakoti.hashnode.dev](https://kartikbudhlakoti.hashnode.dev/month-4-two-hash-functions-one-bug-and-less-time-than-usual?utm_source=hashnode&utm_medium=feed) [Jul 1](https://hashnode.com/posts/month-4-two-hash-functions-one-bug-and-less-time-than-usual/6a45358fbae45a5e09d142d6)