Coding Blocks

In this episode, we have a discussion about what type of technology stack you should choose when you go to create your own project whether it be for profit or an open source type of deal.  As programmers, we often struggle with balancing our ADHD tendencies to code in every language known to man, or actually trying to accomplish something and create a finished product!  With that in mind,  check o...

This week we’re following up on our episode about talking about  Creational Design Patterns  a few of our favorite behavioral patterns: Template. Strategy, and Null Object. Also, pumpkin spice lattes, Mario’s pants, and a billion dollar mistake.

This week we're discussing NDpend , a static analysis tool for .NET.   Triage your biggest problems, Prioritize your refactoring, and CYA with real metrics and trend lines.   We also discuss hidden nuggets, Pintrest-envy, and we pour another one out for google reader.

Welcome back for part 2 of the podcast about databases.  In this half, we discuss several of the things we believe that developers should know about databases.  From joins to unions, group by's and indexing, we try to touch on a lot of the items that most developers should at least be familiar with when working with database systems.   News Attended Build Guild Atlanta, a social gathering of devel...

Part one of our two part database podcast starts with choosing the RDBMS (Relational Database Management System) and what to do when you run into deficiencies in that particular database system. First and foremost, what's with the title?!  Are these guys grammatically challenged?  If that was your first thought, then you should check out this link: http://en.wikipedia.org/wiki/All_your_base_are_be...

"Water Cooler" episode talking about sweet sugary C# kisses, JavaScript as a first language, T-shaped developers, how to get addicted to drugs and...Where in the World is Carmen Sandiego?

This week we're tackling the first section of seminal Design Patterns book: Creational Patterns.   We discuss factories of factories, "bullet hell" games, pathological liars, and Allen's lack of voice.   Big thanks to @rajsotweet for calling us out and getting us motivated to record!  

This week we're taking pot shots from the peanut gallery!   We talk about new features in C# 6. What we like, what we love...and binary literals.   We also struggle to define Roslyn and BONUS! poetry reading from Michael Outlaw!

You down with AOP? This week we're talking with Vlad Hrybok about his spectacular Aspect Oriented Programming Framework: Aspectacular .   Highlights include lots of Design Patterns, Acronyms, Buzzwords and...Duff Beer?

Q: What do developers love more than developing?   A: Expensive accessories!!!   This week we're talking about our Christmas in July lists. Dream keyboards, mouses, office furniture and tablets...oh my!

We discuss the 5 SOLID principles of writing maintainable code, with a focus on C# and .NET, Single Responsibility Principle, Open-Closed Principle, Liskov Substitution Principle, Interface Segregation Principle and Dependency Inversion.

This week we’re talking about LINQ, what’s so special about .NET, the differences IQueryable and IEnumerable, and another round of “Never Have I Ever”. Oh, and jokes!

This week we're trying to wrap our heads around open source software licensing. We discuss the main types of licenses (and a few of our favorites!), what it means to violate a license, and take a fun look at a few weird questions. Download the episode on iTunes or Stitcher and make sure to send us your feedback.

This week we discuss application security in .NET via the 2013 OWASP top 10. We discuss the top 10, how to prevent them and give you a examples of famous attacks that successfully targetted these vulnerabilities. We also give you our predictions for the 2014 top 10 and beyond in a post PRISM world and, as always, our tips and tricks of the week.

Source control stories from the trenches,a game of source control "Never Have I Ever", some fun stuff and our tips & tricks of the week.

In Defense of Boxing/Unboxing 1. Boxed values take up more memory. A boxed value resides in the heap. That means that we need a pointer (32b or 64b) from the stack to our reference-type in the heap as a well as a sync block index (32b). This means a boxed int32 now takes up between 92b or 128b. 3-4 times the space! Ouch!   2. Boxed values require an additional read Values on the stack are right th...

Interfaces are a powerful piece of object oriented programming that is often overlooked.  In this, the very first episode of Coding Blocks the Podcast, we discuss many of the things you should know about interfaces. To help follow along with the podcast, here are some code snippets to explain some of the conversation.  In regards to Joe's statement about interfaces being like guard rails on a high...