Anderson Augusto

How to turn on features without deploying the app again? Use the power of Feature Flags 👇 Feature flags in .NET allow developers to enable or disable features dynamically at runtime, making it easier to control the behavior of applications without redeploying them. This is useful for gradual feature rollouts, A/B testing, and safely introducing new features. 𝐊𝐞𝐲 𝐂𝐨𝐧𝐜𝐞𝐩𝐭𝐬: • 𝐅𝐞𝐚𝐭𝐮𝐫𝐞 𝐅𝐥𝐚𝐠𝐬: Toggles that control whether a feature is enabled or disabled. • 𝐅𝐞𝐚𝐭𝐮𝐫𝐞 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭: Built-in support in .NET 8 for managing feature flags through a feature management API. • 𝐆𝐫𝐚𝐝𝐮𝐚𝐥 𝐑𝐨𝐥𝐥𝐨𝐮𝐭: You can release features to a subset of users before enabling them globally. • 𝐂𝐨𝐧𝐟𝐢𝐠𝐮𝐫𝐚𝐭𝐢𝐨𝐧 𝐒𝐨𝐮𝐫𝐜𝐞𝐬: Feature flags can be configured using various sources such as appsettings.json, Azure App Configuration, or other external services. • 𝐅𝐞𝐚𝐭𝐮𝐫𝐞 𝐅𝐢𝐥𝐭𝐞𝐫𝐬: These allow you to create conditions or rules to determine when a feature should be enabled (e.g., based on user roles, environment, or custom logic). Example: You have a new feature in the application that you want to test how it will be accepted by users. Feature Flags allow you to see the new feature by a certain percentage of users, e.g. 10%. Let's say that today 1000 people visit your website, and 100 people will see the new feature. In this way, you can see how users will accept new changes on your site. Did you try this feature? Join TheCodeMan.net for more content.

271

30 comentários

🚀 ASP.NET Core Filters Simplified 🚀 Filters in Web API help you run code before or after actions. They’re perfect for cross-cutting concerns like logging, security, caching, and error handling. Here’s a simple table to keep them straight 👇 ✅ Pro tip: Use Middleware for global cross-cutting (all requests). Use Filters for MVC-specific cross-cutting (per controller/action). 🔔 Join me to improve your skills to clean code. 👩‍💻 Please share and repost and help others to code better and clean code. Follow me : Ayyappa R.. #efcore #entityframework #csharp #csharpdotnet #csharpdeveloper #csharpprogramming #linq #dotnet #dotnetdeveloper #dotnetcore #dotnetfullstackdeveloper #aspnetcore #aspnet #aspdotnet #aspnetmvc #mvcframework #DotNetCore #ASPNetCore #CSharp #WebDevelopment

127

2 comentários

🚨 WORST Angular MISTAKES TO AVOID 🚨  After reviewing projects, mentoring teams, and digging into Angular features, I’ve noticed the same mistakes repeating again and again. Some come from rushing deadlines, some from habits carried over from older Angular versions, and some from not keeping up with the latest best practices.  I’ve grouped them into two simple categories 👇  🧩 Bad Coding & Architecture Practices   - Skipping unit & integration tests   - Hardcoding configs & environment values   - Mixing business logic inside components   - Overusing 3rd-party dependencies (npm fatigue)   - Avoiding state management for complex flows   - Mutating state directly (breaking immutability)   - Misunderstanding dependency injection scopes   - Copy-paste driven development instead of abstraction   - Ignoring smart/dumb component separation   - Creating “god services” that handle everything   - Forgetting route guards & lazy route protection   ---more ⚡ Performance & Modern Angular Pitfalls   - Ignoring OnPush change detection (or applying it blindly)   - Binding functions directly in templates   - Overusing async pipes everywhere   - Nesting subscribes instead of using switchMap/mergeMap   - Not unsubscribing (or not using takeUntilDestroyed / asyncPipe)   - Misusing Signals like Observables   - Forgetting lazy loading & route-level code splitting   - Ignoring hydration & defer blocks in Angular 17/18   - Overusing ChangeDetectorRef.detectChanges()   - Not using trackBy in @for loops (huge perf issue in lists)   - Skipping SSR, pre-rendering, or PWA optimizations   ---more 💡 The good news? Almost all of these mistakes have straightforward fixes if you adopt modern Angular patterns, profiling tools, and a clean architecture mindset.  👉 I’ve put the full detailed checklist (80+ pitfalls) into a single copy-ready format, happy to share if you want it.  💬 What’s the worst Angular mistake you’ve seen in production?  Follow Sonu Sindhu for more Angular tips & clean code practices 🚀  #Angular #WebDevelopment #Performance #CleanCode #Frontend #JavaScript

430

5 comentários

If you’ve been in .NET for a while, you probably don’t even notice these anymore. Things like: - Built-in DI - async/await that just works - LINQ - EF Core migrations - Hot reload and tooling - Cross-platform runtime Step out of .NET for a year, and suddenly every small task feels like pain again. That’s when you realize how much .NET spoils us as developers. I made this short carousel on 10 things .NET developers take for granted. Go through it and tell me which one you think is the most underrated. And if you’re a .NET dev? Share this proudly. Let the world know .NET isn’t “boring” – it’s just quietly powerful. -- If posts like this make you proud to be a .NET dev, you’ll love my weekly newsletter. Every week, I break down .NET, APIs, architecture, and developer growth. Join 10,000+ devs here: https://lnkd.in/g-2uVCWz

476

17 comentários

💥 𝗥𝗲𝘀𝘂𝗹𝘁 𝗽𝗮𝘁𝘁𝗲𝗿𝗻 𝘃𝘀 𝗘𝘅𝗰𝗲𝗽𝘁𝗶𝗼𝗻𝘀 – 𝗧𝗵𝗲 𝗕𝗮𝘁𝘁𝗹𝗲 𝗳𝗼𝗿 𝗖𝗹𝗲𝗮𝗻 .𝗡𝗘𝗧 𝗔𝗣𝗜𝘀 When building APIs in .NET, one common design debate is 𝗦𝗵𝗼𝘂𝗹𝗱 𝗜 𝗿𝗲𝘁𝘂𝗿𝗻 𝗮 𝗥𝗲𝘀𝘂𝗹𝘁<𝗧> 𝗼𝗿 𝘁𝗵𝗿𝗼𝘄 𝗲𝘅𝗰𝗲𝗽𝘁𝗶𝗼𝗻𝘀 𝘄𝗵𝗲𝗻 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗴𝗼𝗲𝘀 𝘄𝗿𝗼𝗻𝗴? After working with both approaches across various projects, here's a practical comparison to help you decide what works best for your architecture. 🧩 𝗧𝗵𝗲 𝗦𝗰𝗲𝗻𝗮𝗿𝗶𝗼 Let’s say you're fetching a user by ID. If the user doesn't exist, do you: ❌ Throw a UserNotFoundException? ✅ Return a structured Result<T> with a failure message? Both approaches are valid, but they solve different problems. ✅ 𝗧𝗵𝗲 𝗖𝗮𝘀𝗲 𝗳𝗼𝗿 𝗥𝗲𝘀𝘂𝗹𝘁<𝗧> The Result<T> pattern wraps success/failure states in a single object. It’s predictable, consistent, and ideal for business logic outcomes. • Why developers love it: • Clear separation of success and failure • No exception overhead • Consistent response shape for clients • Easier to test (no try-catch needed) 🚨 𝗧𝗵𝗲 𝗖𝗮𝘀𝗲 𝗳𝗼𝗿 𝗘𝘅𝗰𝗲𝗽𝘁𝗶𝗼𝗻𝘀 Throwing exceptions is useful for signaling unexpected failures, like DB connection issues or null references. • Why exceptions still make sense: • Cleaner service code (no if checks) • Built-in middleware support in .NET • Better suited for truly exceptional cases 💡 𝗠𝘆 𝗥𝘂𝗹𝗲 𝗼𝗳 𝗧𝗵𝘂𝗺𝗯: Use Result<T> for expected, business-level outcomes. Use exceptions for unexpected, system-level issues. 📖 𝐅𝐮𝐥𝐥 𝐆𝐮𝐢𝐝𝐞 𝐇𝐞𝐫𝐞: 🔗 https://lnkd.in/dBbuGREK 💬 𝗪𝗵𝗮𝘁 𝗱𝗼 𝘆𝗼𝘂 𝘂𝘀𝗲 𝗶𝗻 𝘆𝗼𝘂𝗿 𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀? Do you lean toward structured results or stick with exceptions? Would love to hear how your team handles this! 👉 Follow me Kanaiya Katarmal and hit the 🔔 on my profile so you don’t miss upcoming .NET tips and deep dives. 𝗧𝗵𝗮𝗻𝗸𝘀 𝗳𝗼𝗿 𝗿𝗲𝗮𝗱𝗶𝗻𝗴 — 𝗹𝗲𝘁’𝘀 𝗰𝗼𝗻𝘁𝗶𝗻𝘂𝗲 𝗴𝗿𝗼𝘄𝗶𝗻𝗴 𝗮𝗻𝗱 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 .𝗡𝗘𝗧 𝘁𝗼𝗴𝗲𝘁𝗵𝗲𝗿! 👉 𝗦𝘂𝗯𝘀𝗰𝗿𝗶𝗯𝗲 𝘁𝗼 𝗺𝘆 𝗻𝗲𝘄𝘀𝗹𝗲𝘁𝘁𝗲𝗿: https://lnkd.in/dp7tz_3V #dotnet #aspnetcore #webapi #csharp #cleanarchitecture #softwarearchitecture #api #designpatterns #exceptionhandling #resultpattern #dotnetcore #backenddevelopment #cleancode #developers #programmingtips

646

49 comentários

🟦 Reviewing Essential C# Concepts — My Dev Checklist Hey folks! 👋 I've been refreshing my C# fundamentals lately, so here’s a quick review of the key concepts every .NET dev should master — whether you’re getting ready for a new project, an interview, or just want to feel more confident in your daily coding. 💡 Dependency Injection (DI) DI helps decouple components and makes your code more testable and maintainable. Why use it? Allows easy swapping of implementations, makes unit testing much simpler, and follows SOLID (especially Dependency Inversion). 💡 Interface vs Abstract Class Interface: Only method signatures and properties, no implementation. Abstract Class: Can have both abstract members and concrete methods. Use interfaces for unrelated classes that share behavior, abstract classes for related ones that share code. 💡 Handling Large Data Files / Memory Management Use streams to process big files chunk by chunk, instead of loading everything into memory. For bulk inserts, Dapper/raw ADO.NET is often better than Entity Framework. Always dispose unmanaged resources! 💡 Efficient File Streaming in C# Don’t load everything into memory! Streaming processes data in small parts, preventing crashes or slowdowns. Always Dispose streams and, for async, use ReadLineAsync() in C# 8+. 💡 LINQ & Lambdas LINQ makes data querying expressive. Lambdas (x => x.Property) are great for filtering and chaining operations. 💡 Async & Await Write non-blocking code for I/O. Avoid .Result or .Wait() on async calls to prevent deadlocks. 💡 Exception Handling Use try/catch/finally for errors. Prefer global exception handling via middleware (like IExceptionHandler) in ASP.NET Core. 💡 BONUS: SOLID Principles & Clean Code Aim for code that is Simple, Organized, Loose, Isolated, and Descriptive. SOLID principles make your code easier to scale and maintain. 🟨 My Golden Tip: Don’t just read these concepts — implement code samples, break things on purpose, and debug your way through! Real learning happens by doing. Helpful Docs & References: Dependency Injection: https://lnkd.in/dGaxgAGk Interfaces vs Abstract Classes: https://lnkd.in/d9hXtZys Working with Streams: https://lnkd.in/dNgS3fNB Async Programming: https://lnkd.in/dH9SpFqF Global Exception Handling: https://lnkd.in/dJ5EwAtV SOLID Principles: https://lnkd.in/dAnEnfA4 ✨ Which C# concept do you think is most underrated — or the trickiest for real-world apps? Drop your thoughts or tips below! 👇 #CSharp #DotNet #Backend #Coding #Learning #WebDev #Career #Programming

50

6 comentários

To all software devs who want to start exploring topics like DDD or Event Storming. Several months ago I published an ebook which is completely FREE to download and I am confident you won't find better free material on these topics. It is high quality content with real practical value - not another "download me and then buy other things" with fluff inside. If you are keen about learning DDD and Event Storming, grab your copy from here: https://lnkd.in/dQ3fCRZW

36

2 comentários