Hi, my Docker Desktop app on Windows 10 is not properly working. I got the following message "Starting the docker engine..." and the application is still stuck on this screen. I've already installed the WSL version 2. It's possible to develop a SpringBoot project without using docker Desktop ? Can the file compose.yml file be ignored ? How can I skip the use of Docker Desktop and connect directly SpringBoot application with MongoDB Compass ? Please help me cause I'm stuck on a project due to this error. Thanks in advance. Kind regards. Eng. Camillo Bosco

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

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

In nowadays scammers are getting new ways to steal people's money or their information. NEVER EVER trust them , send any info , dm , ... to them. Becareful especially one of them exist even around our community. IF anyone asks you to come to their DM though discord , directly insult them and ban them. This lists are a few known scammers : vortex* , ariantahiri* , ( the * will be random numbers because they create random new nicks like abc1, abc2, abc1000 , ... )

I’m going to use it aggressively. Not for prompts, but for output. Here’s how I’m thinking about it 👇 Most people treat AI like: → Google → StackOverflow → A fancy autocomplete That’s a waste. I’m treating it like: • A junior engineer that writes first drafts • A reviewer that spots edge cases • A refactoring partner • A test + docs generator What I’ll be using it for • Scaffolding features fast • Refactoring ugly code safely • Writing tests I usually “skip for now” • Explaining unfamiliar codebases in plain English Goal for the next 90 days: 👉 Ship more without burning out 👉 Spend time on decisions, not typing I’ll share: • What actually worked • What was hype • Real examples (code, workflows, wins, failures) Question for you: If you had Claude Code Max for 3 months, what would you automate or build first? Drop it below 👇