Fundamentals Over Tools in Software Development

🚀 Just published a new tutorial on Dockerizing and Deploying a Python App with Gunicorn and PostgreSQL! In this step-by-step guide, I walk through: ✅ Building a FastAPI app ✅ Connecting it to PostgreSQL ✅ Running production-grade Gunicorn server ✅ Containerizing everything with Docker & Docker Compose ✅ Deploying to a real Ubuntu server This setup mirrors modern production practices and is perfect for backend developers and DevOps engineers alike. 👉 Read it here: https://lnkd.in/gQhY_whZ Let me know your thoughts or questions! 🚀

🚀 Library Management System Now Live A production ready Library Management System designed to simplify and enforce real world library operations. The application models the full lifecycle of book circulation, ensuring accuracy, accountability, and consistency across users and roles. What the system delivers: 📚 Structured book circulation with borrow requests, approvals, returns, and automatic inventory updates 🔐 Clear role based access for readers, librarians, and administrators 🧠 A robust backend built with Django 5.2 and PostgreSQL ⚡ Redis caching to improve responsiveness and system stability 🐳 Fully containerized with Docker and Docker Compose for consistent environments 🚀 Deployed to production on Render via GitHub Container Registry The goal was to build a system that mirrors real library workflows, reduces manual errors, and remains maintainable as requirements grow. 🔗 Live application: https://lnkd.in/d4wk5zBj #Django #Python #LibrarySystems #BackendEngineering #Docker #PostgreSQL #DevOps #BuildInPublic

Day 5 – Variables and Scope in Golang 🐹 📕 Understanding how variables are declared, how := works, variable scope, and default values in Go. ▪️ Variable Declaration 📌 Variables can be declared using var 📌 Go assigns default (zero) values if no value is provided 🔸 var a int 🔸 var name string ▪️ Default values: // Numeric types → 0 // Boolean type → false // String type → "" // Pointer, slice, map, function, struct → nil ▪️ Using := (short variable declaration) 📌 Used inside functions only 📌 Type is inferred automatically from the assigned value 📌 Cannot be used outside functions 🔸 count := 10 🔸 language := "Golang" ▪️ Variable Scope 📌 Global variables → accessible in all functions 📌 Local variables → accessible only inside the function Summary 🚀 Go provides clear variable declaration, strict scope rules, and predictable default values, making code easy to read and maintain.

Docker feels confusing… until Docker Compose clicks. Because real apps are never just one container. In Part 4 of my Docker series, I cover how real projects actually run: Why Docker Compose exists Running Django + PostgreSQL together (properly) Environment variables with .env Data persistence (no more lost databases 😱) How containers talk to each other without localhost 👉 One command. One system. Everything works: docker-compose up If Docker made sense before, Compose is where it becomes practical. 📖 Read Part 4 here: https://lnkd.in/dtyjeB_F Next: Volumes, logs, debugging, and common Docker mistakes 👀 #Docker #DockerCompose #Django #BackendDevelopment #DevOps #LearningInPublic #SystemDesign

🚀 Project Update — Rust Full-Stack Added a React frontend on top of a Rust-powered backend (server-side). The latency difference is immediately visible — responses in single-digit milliseconds. After working with Python backends for some time, this feels… different. Rust as a server-side backend is fast, predictable, and deeply satisfying. Open to feedback, critiques, and suggestions from people building serious systems. GitHub: https://lnkd.in/gmK9rZmB #RustLang #FullStackDevelopment #BackendEngineering #SystemDesign #HighPerformance #APIs #React #OpenSource #SoftwareEngineering

𝐂𝐨𝐝𝐞𝐫𝐂𝐨 𝐂𝐡𝐚𝐥𝐥𝐞𝐧𝐠𝐞 𝐂𝐨𝐦𝐩𝐥𝐞𝐭𝐞: 𝐃𝐨𝐜𝐤𝐞𝐫 𝐢𝐧 𝐀𝐜𝐭𝐢𝐨𝐧! 🚀 I’ve been learning Docker, and the CoderCo challenge was the perfect way to put that knowledge into practice. I built a Flask web app that uses a Redis database to count visits to a route. 𝘏𝘦𝘳𝘦 𝘢𝘳𝘦 𝘵𝘩𝘦 𝘬𝘦𝘺 𝘵𝘢𝘬𝘦𝘢𝘸𝘢𝘺𝘴 𝘧𝘳𝘰𝘮 𝘵𝘩𝘪𝘴 𝘱𝘳𝘰𝘫𝘦𝘤𝘵: 𝘉𝘦𝘵𝘵𝘦𝘳 𝘱𝘳𝘢𝘤𝘵𝘪𝘤𝘦𝘴 𝘢𝘱𝘱𝘭𝘪𝘦𝘥: - Using a non-root account for containers. - .dockerignore to exclude unnecessary files. - requirements.txt for Python dependencies. - Health checks for container reliability. 𝘕𝘦𝘸 𝘵𝘩𝘪𝘯𝘨𝘴 𝘐 𝘭𝘦𝘢𝘳𝘯𝘦𝘥: - Persisting data using Docker volumes. - Using environment variables for configuration instead of hardcoding. - Leveraging Nginx for scaling and reverse proxy. This challenge helped solidify my Docker knowledge, giving me experience with techniques that are directly applicable in real-world production environments. You can check out my Docker repository on GitHub to see all my material on Docker and my solution to the CoderCo challenge: https://lnkd.in/evqu5R3P #DevOps #Docker #Flask #Redis #WebDevelopment #NGINX

#backend #golang #faas go-faas (v0.3.0) Features > Supports immediate execution of code snippets without persistence. > Replaced Docker with Podman as the container engine. > Add MAX_CONTAINERS to limit concurrent container. https://lnkd.in/gdjGTth6

I found this GitHub repository very helpful to understand Essential TypeScript. It covers, 1. Types, Variables, Functions 2. Interfaces, Classes, Modules, Generics 3. OOPS topics: - Inheritance - Super() - Polymorphism - Access Modifiers - Public vs Private - Protected - Static - Readonly All of these can be find here: https://lnkd.in/gMETxGMq I started updating this repository, This repository is open for contribution. If you find anything to update, raise PR. #angular #typescript

Recently I tried to use both Cursor and GitHub copilot to create a helloworld microservice, some interesting findings here. In short, my feeling is "cursor is more like a programmer, and github copilot still acting like a chatbot" 😅 My task input is as below: (1) Java based microservices, and follow the microservices best practices (2) Deploy on GKE for GCP (3) Helm deployment template (4) Consider NFR, including unit test, design document in mermaid format etc (5) I have the local docker env, could provide the guideline for local deployment debugging

Day 13/30 — Making Sense of Backend Execution Today I deliberately paused coding to fix a gap I noticed: I could talk about backend concepts, but I didn’t fully see the execution in my head. So I focused on: Understanding how a backend server actually stays alive What really happens when a request hits Express Why middleware exists and how it can silently break a server When a request truly ends and why backend is stateless by default This wasn’t about learning new tools — it was about removing confusion around how things actually run. Key takeaway: Backend confidence doesn’t come from writing more code. It comes from clearly knowing what runs, in what order, and why. Stopping here to let the fundamentals settle before going hands-on next. #Day13 #BackendDevelopment #NodeJS #ExpressJS #ServerSide #30DayChallenge #LearningInPublic