Carlos Alexandre Figueiredo

I've found that the Superpowers framework (https://lnkd.in/dMd5sHz9) is very effective when working with coding agents. I think most engineers working with coding agents realise how important the planning phase is. However, I've never been *completely* convinced by the native planning mode that you get with tools like Claude Code or Cursor. Over the last couple of weeks, however, I've gotten pretty consistent planning documents from Claude via the Superpowers plugin. I also like how each plan is broken down into two separate documents: one for design, and one for implementation. The actual implementation is then carried out via a new subagent per task, with additonal spec compliance and code quality reviews in between. This does obviously result in higher token usage, but I've found that the results are generally consistent (and I don't have to constantly keep going back and forth). Definitely worth taking a look at!

27

Hi fellow junior developers! I just want to remind you (and myself) about this: It's impossible to know four programming languages, countless frameworks, every single Git command there is, be a fullstack developer and know everything about data infrastructure all at once. Nobody expects you to, either. So just keep learning and become good one step at a time. Focus on learning and improving step by step. Track what you knew a year or even a month ago, and you’ll see how much you’ve grown. That’s what helps me trust my learning process. And honestly? This phase, where everything is new and progress feels fast, is something you’ll probably miss the most in the future. Try to have fun and remember why you even started this journey. It will pay off.

2.998

152 comentários

I can’t stress this enough: To become a Senior engineer you don’t need to complicate things. What you need is to focus your efforts on being pragmatic, business-oriented, and solution-oriented. I’ve seen too many talented mid-level devs shooting themselves in the foot by: 👉🏻Adding unnecessary abstraction layers “for future flexibility” 🤦‍♂️ 👉🏻Implementing design patterns that solve problems that don’t exist 👉🏻Building “elegant” solutions that take 3x longer to ship. Meanwhile, senior devs are out there asking the right questions: 👉🏻”Whats the simplest solution that works?” 👉🏻”What are we actually optimizing for?” 👉🏻”Will this help the business or just my ego?” Your promotion isn’t blocked by lack of complexity, actually it’s blocked by too much of it. Save your creative energy for problems that actually need complex solutions.

678

46 comentários

🆕 Goodbye to IntelliJ IDEA Community Edition after 16 years! IntelliJ IDEA: Moving to a Unified Distribution 📝 In July 2025, JetBrains announced that IntelliJ IDEA would be released as a single, unified product rather than two separate editions, so from version 2025.3 onward, there will be one installer for IntelliJ IDEA (no separate “Community” vs. “Ultimate” downloads). In my last article, I explored the changes and effects of JetBrains' decision. 🔗 https://lnkd.in/dDB-HJTE

202

✨ Just came across something super interesting for developers 😱 (best side income opportunity)🤫 → VickyBytes and I just shared my video on "European Summer Of Code" on VickyBytes 🙂 Most platforms reward only specific formats or rely on algorithms that decide whether your content gets seen. But VickyBytes is changing the game: 🔹 Developers can post articles, code, or videos and earn equally for all. 🔹 For short-form tech videos (Bytes), creators actually earn 2x what YouTube pays 🤯 🔹 And best of all no algorithm lock on payouts. If you create, you get paid. Simple. It feels like YouTube for developers, but with a much bigger vision. Along with content, VickyBytes also features: - Opportunities (fresh job openings from the last 24 hours) - Events - A developer marketplace (coming soon!) And it’s being built right here in India 🇮🇳 with a truly global vision. As someone who has watched the creator economy grow, this feels like a big leap forward for tech creators worldwide. 👉 If you’ve thought about sharing your development journey, code, or insights, this is the platform to start. ✨ Where can I check my uploaded videos? Watch here 🔗 https://lnkd.in/eHgpe467 Or get the link from the comments :) #tech #trend #info #resourses #ad

380

26 comentários

Several years ago (~2017), during a DevOps Porto Meetup, a peer reached out asking for help. His team was starting out with Kuberentes and they were having some trouble: they were a team of 5 engineers building everything, from product to operations and everything in between. For them, the ramp-up to go from their setup to Kubernetes was proving too difficult. They had a lot on their plate, and Kubenetes was a "pain" they could live without. So I asked: Why do you need Kubernetes? He fired back with: Because everyone is using it, and isn't it "the right thing to do"? First things first: No, everyone was not using it. Still true today, but back then, adoption was way lower. Second, the right thing to do is highly contextual. After discussing the topic with him, Kubernetes was not the right thing for his team. I remembered this interaction because a similar one happened a few weeks ago: an engineer from a small team having trouble with "platform engineering". So I asked again: Why do you need to build a Platform? And he fired back with: Because everyone is using it, and isn't it "the right thing to do"? No, everyone was not using it. The right thing to do is highly contextual. You need to understand *your* problems and build solutions that address them. We can learn a lot from others (DevOps Porto is a great place to share and learn btw), but we don't need to build or use something just because they do.

15

3 comentários

This is the thing I struggled with when I was a junior: How to represent Table per Hierarchy inheritance in EF? Did you hear about the Discriminator column? Suppose you are building a transport management system for different types of vehicles, such as cars and bikes. These types share some properties (e.g., Id, Model), but they also have unique attributes (has NumberOfDoors, and Bike has HasGear). The Discriminator column allows you to handle this scenario more effectively. When you retrieve vehicles from the database, Entity Framework Core will use the Discriminator column to instantiate the correct type (Car or Bike), enabling you to handle them polymorphically. Similarly, when you save a Car or Bike to the database, Entity Framework Core automatically assigns the correct Discriminator value. Learn more: https://lnkd.in/drVrmMYn

501

46 comentários

When I read complaints about Scala, they usually reduce to: no jobs, couldn’t make it work, or too many options. None of these are properties of the language — they’re properties of teams without engineers. Without tasks, no engineers appear. Without engineers, no tasks get solved. #Scala

26

41 comentários

Your Business Logic Is a Legacy Bomb Business logic is like glitter, once it’s in your codebase, it never leaves. Yet developers mix it with frameworks, AOP, JPA lifecycles, and even annotations as if that’ll age well. Spoiler: it won’t. Make logic explicit. Ban black magic. Kill hidden behavior before it kills your updates and your maintainability. Services should be boring. One responsibility. One intent. Not some god-class that knows 20 repositories and calls three clouds before breakfast. Isolate business logic. No, your entity is not a DTO in disguise. It should do something. Rules? Extract them, Strategy pattern, DSLs, Rule Engines. Variation? Externalize it. Sharing? Yes, even your beloved GitHub Actions. Reuse, don’t regurgitate. Frontend and auth layers should choke on business logic. The backend? A cold, lifeless BLS (Business Logic Service) or BFF. Keep core services stupid. Stupid scales. Stupid survives. And infrastructure logic? Out. CORS, HTTPS, tracing, pipelines,… should never haunt your domain logic. One place. One purpose. Fewer edge cases. Fewer WTFs. Databases are for persistence, not clever tricks. Your dishwasher doesn’t run Spring Boot. Neither should your repositories. You build tool has cool features? Ignore them, it should just build and your service should be dump and fast enough to build. No special feature pays in long term. Want maintainability? • No black magic. • No framework entanglement. • No accidental architecture. Just stupid simple, reusable, testable, measurable and boring code. That’s the dream. Because when your object mapper changes naming strategy and you wake up to a 500 error, you’ll remember this post. “You build it, you run it.” Just doesn’t mean you have to build a mono repository monster. DX is more important than performance as developers are expensive not the numbers of instances.

38

7 comentários