devleader

Excited about our press release today! Super cool partnership for BrandGhost! Monte Mader Partners with BrandGhost to Streamline Social Media Engagement prn.to/3YxGM8K

What's reflection in CSharp all about? At compile time, we know the types of the objects that we're dealing with. But what if you dynamically want to look up information about a type? What if you want to look up a type by name at runtime? Reflection is a tool available to us in DotNet that allows us to look at the meta information of types. We can: - Examine type members - Invoke methods by their name - Create instances of types we didn't know at compile time We can even do things like set new valuables to private readonly variables! Reflection is powerful -- and just because you CAN doesn't always mean that you SHOULD! Watch the full video here: youtu.be/7xWaSuPn2I8

Decorator Pattern Best Practices in C#: Code Organization and Maintainability Master decorator pattern best practices in C# including code organization, maintainability tips, DI integration, and common pitfalls to avoid. Read the article here: devleader.ca/2026/03/20/dec…

What's the biggest misconception people have about your job as a software developer?

Architecting Systems at Startups and Beyond - Interview With @RaulJuncoV You've surely seen his system design and software architecture content, right? You know the man -- Raul Junco! I really enjoyed our chat, and navigating how software architecture looks whether you're at big or small companies. When you're trying to move fast, there's not as much time for these things -- so how do you balance it with your team? Huge thanks to Raul for making the time to chat with me! Watch it here: podcasters.spotify.com/pod/show/dev-l…

How To Use Enums In CSharp — Understanding The Basics Read it on Medium: medium.devleader.ca/how-to-use-enu…

📌 Have you been tuning into my AMA live-streams I do EVERY Monday at 7:00 PM PST? Each stream I focus on: - Reviewing my most recent newsletter - Providing my perspective on spicy Reddit posts related to software development - And most importantly... ANSWER YOUR QUESTIONS! 👇 Let me know what you want me to answer in my next stream! 👇

An employee out there still thinks of you because you were kind to them. And what a powerful thought that is -- truly, you changed someone's life. No. Not just for managers. Not just for formal leadership positions. You can have this lasting kind of impact on others regardless of your role. Regardless of your level. Regardless of your title. I've been very fortunate to have some stand-out individuals throughout my career -- some early on in my internships! Peter: Peter is a brilliant software engineer who always took the time to teach what he was doing, made space for any questions, and would "let me drive" because it was a safe place to fail (and learn). I don't think I realized at the time how great of a mentor Peter was -- but this was my very first job as a developer. Nick T, Ben, and Gary: These three gave me challenges to push my comfort zone as an engineer. They believed in me and when I'd deliver they'd continue to challenge me. This was one of the first times as a programmer where every time I could showcase my abilities, they were right there to say "Oh yeah? Try this on for size". And this was some of the best technical growth I had experienced in my career. Jad: This was my first boss and manager who gave me full autonomy AND full trust. I've never felt more empowered in my career and every minute I put into my work translated into positive impact. Even though I was working for someone, it felt like I was helping my own company grow -- and this is all because Jad had a high degree of trust in me and gave me space to do my best work. Who are some of the individuals from your career that have changed your life? What made them so memorable for you? #Mentors #SoftwareEngineering #SoftwareEngineers

What's a hacker's favorite season? … .. . Phishing season.

📌 📌 If you enjoy my content, consider subscribing to my newsletter: weekly.devleader.ca It's free and I have something for all levels of software engineers to help you out on your development journey. Join thousands of other readers every weekend!

Being a rubber duck is the path to success... Metaphorically, of course. Rubber ducks don't actually make great software engineers. But while many of you have heard of "rubber ducking" in programming (and some are reading this for the first time going "what the HECK"), how might this apply to problem solving in general? I have noticed that many junior software engineers need to spend a bit more time trying to answer their own problems first. If you keep in mind that someone should be asking you "What have you tried, so far?", then you can start becoming your own rubber duck to bounce ideas off of yourself. Be your own before you make someone else your rubber duck! Watch the full video here: youtu.be/fCr12yhrSbM

GitHub Copilot SDK Installation and Project Setup in C#: Step-by-Step Guide Set up the GitHub Copilot SDK in C# with this step-by-step guide covering NuGet package install, GitHub Copilot CLI authentication, and project configuration. Read the article here: devleader.ca/2026/03/19/git…

What Are C# Source Generators? History, Concepts, and How They Fit in .NET Understand what C# source generators are, their history in .NET, and how they differ from reflection and T4 templates. A clear introduction for .NET developers. Read the article here: devleader.ca/2026/03/19/wha…

Does this FULL STACK Developer Resume Measure Up To The Rest? A full stack developer has sent in their resume to get some perspective about what's working well and what could use some work. Do they have the right ingredients for a solid software engineering resume? Let's check out their resume in this resume review! Watch it here: youtube.com/watch?v=m4Uy09…

Why should we even bother with refactoring? Read more here: devleader.ca/2023/11/21/wha… #refactor #refactoring #programming

Have you seen these 14 FREE full-length CSharp videos yet? Here's a compiled list of videos to get you through many common aspects of starting off in CSharp! Strings: - Comparing Strings: youtu.be/nFFKfbuOvQw - StringBuilder: youtu.be/zQHc4RKC6F0 Enums: - Beginner's Guide: youtu.be/9GxabCuWTEk - Strings to Enums: youtu.be/VENbpXhGUZM - Flags: youtu.be/_yUOrzTCpGU - Avoid Incorrect Usage: youtu.be/Z_V-c7fph1U Collections & Enumerables: - Beginner's Guide to Dictionaries: youtu.be/5VvAcoBJGJs - Arrays, Lists, and Dictionaries: youtu.be/VFO5vK7QjBc - IEnumerable Crash Course: youtu.be/RR7Cq0iwNYo - Iterators: youtu.be/fU5-QeSLG2I - Iterators vs Collections: youtu.be/0s_VMhZSOwQ Switch Statements: - Basics of Switch Statements: youtu.be/R0Ed8LIGcyY Exceptions: - How To Rethrow: youtu.be/qqlw-BSFSMU - Stop Throwing Exceptions: youtu.be/47xt3gI5Ea8 #csharp #dotnet #dotnetcore #learntocode

📌 Check out my channel for FREE learning resources on C#, dotnet, and software engineering in general: @devleader" target="_blank" rel="nofollow noopener">youtube.com/@devleader

As a software engineering manager, here's what I prioritize when joining a team There are 3 main areas that I break my focus into. It would be impossible to put 100% effort into each of these in isolation, but I do try to focus on them in this priority: 1. Meet & Learn The Team: This is my number one priority when starting with a new team. This assumes that everything isn't on fire and that the team is operational. No fires to put out? Awesome - Spend time with the people who do the work. I fundamentally believe that my role and responsibility as an engineering manager is to empower my team to do their best work and support them in their career growth. That doesn't mean that strategy, prioritization, etc... aren't important. It just means that those things won't matter if I can't get a team engaged to do the best work they can. This often involves setting up regular one-on-one time, listening to what challenges they're currently facing, and getting started on career conversations early. I need to work early and often to ensure that the team can trust me as their leader, or else it's hard to make the rest happen. 2. High-Level Systems Perspective Existing engineering teams are going to have products and services that they're working on already. That means there's history put into what's been built and a (hopefully) shared understanding of why things have arrived at a certain point. This often involves spending time with subject matter experts to explain high-level areas of the systems we build and support. Design documents. Whiteboarding sessions. Video tech talks. All sorts of information to catch up on to understand how the different parts of the system fit together. For me, this doesn't involve understanding specific areas of code. However -- as time goes on and I can get more in-depth knowledge, this is something I personally try to lean into when I can. Given that I have a technical background, I find it helpful when communicating with my team when I understand more of the details. 3. Tactical Focus Unless I am joining a team right as they are about to go into some type of planning period, odds are they have an idea what they're working on now. They probably also have a pretty good idea of what they'll be working on. For me though, this is something I need to learn and understand so that I am not disrupting the plans that are in place. Especially as I spend more time with individuals to learn about how they work and what gets them engaged, understanding the tactical side of things helps ensure I can keep alignment with them as we move forward together. What things do you keep in mind when joining a new team?

When to Use Singleton Pattern in C#: Decision Guide with Examples When to use Singleton pattern in C#: decision guide with examples, use cases, and scenarios where a single instance provides the most value. Read the article here: devleader.ca/2026/03/19/whe…

How do you balance the need for new features with the need to fix bugs and maintain existing code?

How To Dominate Technical Debt And Build Better Code Read it on Medium: medium.devleader.ca/how-to-dominat…