Coding Blocks
Summary: Pragmatic talk about software design best practices: design patterns, software architecture, coding for performance, object oriented programming, database design and implementation, tips, tricks and a whole lot more. You'll be exposed to broad areas of information as well as deep dives into the guts of a programming language. Most topics discussed are relevant in any number of Object Oriented programming languages such as C#, Java, Ruby, PHP, etc.. All three of us are full stack web and database / software engineers so we discuss Javascript, HTML, SQL and a full spectrum of technologies and are open to any suggestions anyone might have for a topic. So please join us, subscribe, and invite your computer programming friends to come along for the ride.
- Visit Website
- RSS
- Artist: Allen Underwood, Michael Outlaw, Joe Zack
- Copyright: CodingBlocks.NET ©2019
Podcasts:
We continue our Domain Driven Design conversation this week as Allen is indecisive, Michael decides for him, and Joe can't handle the night life.
We continue our Domain Driven Design conversation this week as Allen is indecisive, Michael decides for him, and Joe can't handle the night life.
We're back with another exciting episode as Michael questions Hollywood, Allen dreams of his Hackintosh, and Joe is surrounded by Star Wars as we talk about how to jumpstart your next app with Michael Crump (@mbcrump) and Clint Rutkas (@clintrutkas).
We're back with another exciting episode as Michael questions Hollywood, Allen dreams of his Hackintosh, and Joe is surrounded by Star Wars as we talk about how to jumpstart your next app with Michael Crump (@mbcrump) and Clint Rutkas (@clintrutkas).
This week, Michael asks his customers about their anemic domain model, Allen talks in front of people, and Joe plays Rocket League as we begin our dive into understanding domain driven design.
This week, Michael asks his customers about their anemic domain model, Allen talks in front of people, and Joe plays Rocket League as we begin our dive into understanding domain driven design.
This week we talk about all of the bad things we've done while making software. The good, the bad, ... oh wait, it compiles, never mind.
This week we talk about all of the bad things we've done while making software. The good, the bad, ... oh wait, it compiles, never mind.
We're back with another deep dive into the infamous book Clean Code by Uncle Bob as Joe alters columns, Michael misreads things, and Allen has a positive customer service experience.
We're back with another deep dive into the infamous book Clean Code by Uncle Bob as Joe alters columns, Michael misreads things, and Allen has a positive customer service experience.
This week Allen is troubled by circles, Michael talks like a game show host, and Joe announces it's twins as we continue our deep dive into the classic Clean Code book by Robert C. Martin.
This week Allen is troubled by circles, Michael talks like a game show host, and Joe announces it's twins as we continue our deep dive into the classic Clean Code book by Robert C. Martin.
When and why should you write unit tests, and just how important are they? Take a listen and see what YOU think. For the full show notes visit: https://www.codingblocks.net/episode54
When and why should you write unit tests, and just how important are they? Take a listen and see what YOU think. For the full show notes visit: http://www.codingblocks.net/episode54
In this episode we talk about how to insulate your application at it's boundaries? What in the world does that even mean?! We're not talking about those boundaries where others aren't allowed to touch your keyboard (although that's a real thing). No, we're talking about making sure you make your code easier to maintain over time by coding to interfaces or wrappers for third party libraries or external APIs. Come join us on another deep dive into Clean Code, and our (polluted) thoughts on the topic.
