Nick Cosentino | Simplifying software engineering concepts for you | Principal Software Engineering Manager @Microsoft | Creator of @BrandGhostAI đź‘»
Joined January 2023
- Tweets 18,403
- Following 1,110
- Followers 6,169
- Likes 11,851
4,675 Photos and videos
Pinned Tweet
Jan 12
Excited about our press release today! Super cool partnership for BrandGhost!
Monte Mader Partners with BrandGhost to Streamline Social Media Engagement prn.to/3YxGM8K
1
1
13
2,048
5
3
14
557
Liskov Substitution Principle C#: Correct Inheritance Every Time
Learn the liskov substitution principle c# with real examples. Avoid inheritance violations and build correct, substitutable hierarchies in .NET 10.
Read the article here:
bgh.st/6cfx6s
62
Less Than 30 Lines Of Code - MongoDB with Testcontainers in C#
MongoDB is an awesome document database that we can use from C# using the MongoDB Driver NuGet package. But what if you don't want to setup MongoDB Compass or deal with MongoDB Atlas? Is there an easy solution to just try out MongoDB locally, or even leverage it for testing purposes?
Testcontainers for MongoDB is the easy solution here! See how we can hook up Docker with MongoDB in less than 30 lines of pain-free C# code!
Watch here:
bgh.st/8jgm3f
1
76
What if we could easily spin up containers for services that our tests depend on?
Read more here:
bgh.st/9dah6a
#MongoDB #CSharp #DotNet #Testcontainers #Docker
74
Yup, I'm guilty of doing it...
I absolutely have classes that are hundreds of lines or over a thousand lines long.
It's something that can sneak up on us as we're quickly building and iterating on systems.
Yes. There are absolutely things we can do to prevent this from happening.
Yes. This is not ideal for readability.
Yes. I'd like to change it.
And I will. I will go improve this.
But sometimes it's not a priority. And if I'm fixing a bug in production, like in this particular video clip, I am not going to layer on refactoring a 1000 line code file and 1000 line test file into the same commit.
I'll just schedule to do it later if it's still even a priority for me. And if it's not... then it's because I'm focused on more important things :)
Watch the full video here:
youtube.com/watch?v=6so35iZN…
88
Memento Design Pattern in C#: Complete Guide with Examples
Master the memento design pattern in C# with code examples, undo/redo implementation, and best practices for state preservation.
Read the article here:
bgh.st/6ypz4u
65
How do you deal with feature creep? What do your recommend to developers to help keep this in check?
1
150
Success From Software Engineering Failures - Interview With Alex Lau
In this video, I got to sit down with Alex Lau to discuss his book, his almost-accidental success in public speaking, and how he continues to grow from his failures in software engineering.
On failures, most people shy away from them. We keep them secret. Failing is bad. Except... failing is one of the very best ways that we can learn and improve -- and Alex has set out to help others know that they can learn from failures.
And on public speaking -- you know I always say how important communication is in software engineering! Let Alex also remind you!
Thanks for the chat, Alex!
Watch it here:
podcasters.spotify.com/pod/s…
#Interview #Podcast #SoftwareEngineering
69
Extract Method Refactoring Technique in C# — What You Need To Know
Read it on Medium:
stories.devleader.ca/extract…
128
Jun 12
Remember to say thanks to your favorite senior dev AKA firefighter ❤️
#SoftwareEngineering #Developers #Memes
2
4
244
Jun 12
đź“Ś If you like the memes I post, you'll love my educational content:
weekly.devleader.ca
89
Jun 12
Open Closed Principle C#: Extending Without Modifying
Learn the open closed principle c# with real examples. Extend behavior without modifying existing code using Strategy pattern and .NET 10 features.
Read the article here:
bgh.st/ce6ywd
71
Jun 12
C# MongoDB Beginner's Guide: How To Update Documents
We're all so accustomed to working with different SQL databases... But have you spent much time working with document databases? In my development more recently, I've been trying to make sure I spend some time working with MongoDB in C# so that I have more exposure to these different tech stacks.
In this MongoDB tutorial, I'll show you how to update documents in MongoDB databases from C#. You'll want to make sure you understand how filtering works in MongoDB first so that you can properly target documents for updates! With your filtering knowledge, we can get our MongoDB updates done with some simple C# calls.
Watch here:
bgh.st/opya0j
90
Jun 12
How do we query records in MongoDB from CSharp?
Read more here:
bgh.st/na6bhi
#MongoDB #Databases #CSharp #DotNet
79
Jun 12
When I say "unit" tests, I mean...
I'm not interacting with anything outside of the class I'm writing tests on without fully controlling it.
Period. Hard stop.
But that's part of how I differentiate "unit" tests from all of the other types of tests we can write.
And that doesn't mean that I think this is always the best or the only way to test!
In fact, I encourage you to have a mix of tests! They serve different purposes for building confidence in different ways.
As soon as I start writing tests that use other class logic, interfacing with the environment, or interacting with other services... They're no longer a "unit" test to me. But I still write plenty of tests that do these things.
Watch the full video here:
youtube.com/watch?v=6so35iZN…
1
74
Jun 12
Mediator Pattern Best Practices in C#: Code Organization and Maintainability
Mediator pattern best practices in C# for clean code organization, maintainability, and avoiding common pitfalls with behavioral design patterns.
Read the article here:
bgh.st/58wcd1
1
56
Jun 12
What's the best way to approach building to test a product concept?
With the least amount of work possible.
If I am making an "MVP" for something and we're setting out to even prove if a concept is feasible, then I nearly disregard all architectural concerns.
If it's truly a prototype to even see if there's even value in pursuing development, then the goal is answering questions (generally about market fit) and not about building extensible code.
I've spent over a decade working a lot with rapid prototypes. This started with internships and continued on into my professional career after university.
As funny as it sounds, the least work you can do the better when it comes to answering if something is a feasible idea. If we could avoid writing any code to get those answers, that was the best fit.
This was because we were positioning ourselves to be as nimble as possible. We needed to be ready to toss it and move on. If it was a good fit, then we'd generally be rewriting whatever we hacked together.
In many cases, we didn't even know how we might package what we're building:
- Is it a new website?
- Is it a new desktop app?
- Is it going to be integrated into what we have?
If we don't even know if there's a valid use case, you're wasting time architecting it until you've proven that.
👇What would your advice be?👇
4
1
335
Jun 12
đź“Ś Check out my channel for FREE learning resources on C#, dotnet, and software engineering in general:
youtube.com/@devleader
102