Did you know that git commands split into porcelain(used usally by the dev) and plumbing(used by git itself under the hood) commands. E.g git add, git commit, git log those are all PORCELAIN commands. E.g of a PLUMBING command is git cat-file -p <hash>, this command shows: 1. tree(git's way of storing a directory or blob(git's way of showing a file) 2. parent 3. author 4. committer Git doesn't store diffs, it stores full snapshots of every file on each commit. It's smart enough to deduplicate unchanged files, so identical content across commits only gets stored once. Verified it myself with git cat-file, same file, same hash, across commits.

I like projects that start with: “We know what we want to build, but we’re not sure how to build it properly.” I’m a senior software engineer and most of my work sits somewhere between full-stack development, AI, automation, mobile, and backend architecture. A few examples of things I can build: → An AI agent that reads documents, makes decisions, calls APIs, and takes actions instead of just answering questions → A SaaS product from rough idea to a working MVP with authentication, subscriptions, admin tools, and deployment → WhatsApp/Discord/web assistants connected to CRMs, internal data, calendars, and business workflows → Existing systems that need to be untangled, stabilized, sped up, or prepared for real production traffic → Mobile + web products sharing the same backend → IoT/robotics systems connecting real hardware, sensors, cloud services, and AI My usual stack includes TypeScript, React/Next.js, Node.js, Python/FastAPI, PostgreSQL, Redis, React Native/Flutter, AWS, Docker, and LLM/RAG tooling. I’m not only looking for neatly written project specs. If you have an unfinished prototype, a half-working product, or even an idea where the technical direction is still unclear, send it over. I’m happy to look at the problem first and tell you how I’d approach it. No sales call required.

Big thanks @Nelson Djalo for sharing this! On the amigoscode YouTube channel Always appreciate discovering useful content thank you https://www.youtube.com/watch?v=VC2YuBeT1-0&t=211s

Following along with a tutorial makes building full-stack applications look simple, but staring at an empty code editor right after is where the real panic sets in. You understand the architecture and API endpoints while watching someone else build it, but designing your own schema and handling edge cases from scratch feels completely different. Most people get trapped consuming one roadmap or course after another without actually finishing an independent project. For those who broke through that initial wall, what helped you transition from following guides to actually shipping your own software?

Java & Spring Boot developers, let’s have some fun. 😂👨🏽‍💻 Is this code fine, or does it have errors? If you see errors: - How many are there? - Are they compile-time or runtime errors? - What exactly is causing them? - How would you fix each one? Try to solve it without asking AI first 😂😂 Drop your answers below — let’s see who catches them all. 👀☕