A few years ago I made a Spring Security course. Then everything changed — breaking changes, new APIs, deprecated stuff everywhere. The course aged badly and I didn't want to keep band-aiding it. So we rebuilt the whole thing from scratch. Here's the roadmap 👇 🔐 Part 1 — Foundations 🔑 Part 2 — JWT + Refresh Tokens 🚀 Part 3 — Advanced (coming soon after) Parts 1 & 2 drop next week. Inside Part 1 (5+ hours): ✅ Security Filter Chain — finally explained properly ✅ AuthenticationProvider, AuthenticationManager, SecurityContextHolder ✅ UserDetailsService + custom DAO auth ✅ Form login, Basic Auth, sessions ✅ BCrypt, salting, hashing, rainbow tables ✅ Roles vs Authorities (and why ROLE_ exists 🙃) ✅ Storing users + roles + permissions in a DB ✅ Security events with listeners Then Part 2 goes deep on JWT + refresh tokens — the way it should be done. If you've ever stared at a Spring Security config file and felt your soul leave your body… this one's for you. 👉 Drop a 🔐 below if you want me to tag you when it drops

Hi @Nelson Djalo 👋, first of all, thank you for the immense value you bring to the community. Your courses have taught thousands of us how to master code. But today I want to put a challenge on the table for a future course. I've realized the root problem we have in current tech education: We consume hundreds of hours of tutorials learning languages and frameworks, but we DO NOT know how to design software. We know how to write a class in Java, but when a client asks for a project from scratch, we hit a brick wall. We are missing the lost link: Object-Oriented Analysis and Design (OOA/D). Anyone who wants to build real software (whether at home or at a company) needs to master skills that go way beyond the programming language itself: ✅ Gathering real requirements (without getting overwhelmed). ✅ Differentiating and documenting functional vs. non-functional requirements. ✅ Writing Use Cases that actually add business value. ✅ Translating those Use Cases into Sequence Diagrams and Domain Models. ✅ Knowing how to elegantly assign responsibilities to objects (GRASP/GoF Patterns). The request: Could you guys consider making a full course on OOA/D? But with the Amigoscode magic: 100% PRACTICAL. We don't want more boring, 200-page university theory that no one reads. We want to see Nelson sit down with a "client", extract the messy requirements, draw the diagrams on a whiteboard, and then translate it into real code step-by-step using Agile iterations. I believe this is the ultimate leap to go from being just a "coder" to a true Software Engineer/Architect.

Most developers think their job is to write code That mindset works fine in the first year or two But it stops working the moment you start joining real teams and inheriting real systems Because in production engineering you spend far more time reading code than writing it You read pull requests You read legacy code You read code AI just generated You read code that broke at 3am The engineers who get stuck at junior level treat reading as a chore The engineers who level up treat it as the actual skill Here is the mental model you should have → Reading code is how you understand systems you did not build → It is how you spot mistakes before they reach production → It is how you learn patterns that took other engineers years to figure out → It is how you debug AI generated code instead of trusting it blindly → It is how you make better decisions about what to write in the first place → It is how you build the judgement that makes a senior engineer valuable The biggest mistake juniors make is rushing to type They want to ship something They want to look productive They want their commit to land first But shipping fast without reading first is how bugs enter the codebase Strong engineers slow down before they speed up They read the existing code They read the related tests They read the commit history They read the surrounding context Then they write something that fits the system instead of fighting it Reading is not the boring part of engineering It is the part where careers are actually built If you opened your team codebase right now would you understand what is happening end to end Share your thoughts below Follow Amigoscode for practical lessons that help developers move from coding to real software engineering

i bought the course a long time ago and my course Isn't showng up i bought the course back when it was new i bought the java master class i bought it in 2020 or 2021

I lost access few months back. Ever since, I am trying to sign up. is monthly subscription not offered anymore?