It’s been a long time coming but I’ve finally recorded the first demo of Bizio. In this half-hour special we’ll start a company with Will Smith, tackle an easy portfolio project, hire some employees, slash salaries, and so much more. Take a look, leave some comments, and get pumped because Bizio is moving along. I’ll continue producing videos more regularly to cover particular features as they are added and in a while we’ll do another playtesting demo. Enjoy!
AI is such a broad term these days, but in Bizio it directly refers to the decision-making logic implemented for the non-human players in a game. You first need to understand the mechanics of a turn before you can understand how the AI leverages these mechanics to make decisions like a real human.
At this point in the project you might expect that things are organized, documented, and that we have a clear roadmap to completion. Unfortunately that is not the case, but it’s never too late to make a change for the better!
Hey! The first update on the development progress for Bizio obviously can’t cover everything I’ve done up to this point but over time I’ll cover a majority of the functionality and inner workings.
The purpose of this article, however, is to talk about Linq beyond the 101-level course. Linq is incredibly convenient and also introduces a few other programming concepts that can be applied elsewhere. This article will talk about some less well known extensions as well as the programming mechanisms used to take advantage of them. Here are a few of the things I’d like to cover:
- Count, Any, and All
- We need an implementation of the INotifyPropertyChanged interface to allow for data binding
- We need some safe and convenient syntax for calling the event handler for PropertyChanged
- We need to make this call thread safe
- We need to reduce the memory footprint of this call
- *BONUS* Can we factor a pattern out of our code?
This is the first article I am writing and decided to tackle a fairly straightforward topic. Every application I’ve worked on that was larger than a proof-of-concept benefited from some form of logging. The problem always was one of the following:
- There was no logging system at all
- The logging system was cumbersome to actually use
- The logging system logged way too much information
- The logging system wasn’t used in the most critical areas
So the first point is going to be solved simply by reading this article. We are going to walk through creating a simple yet useful logging system that is extendible and solves the above problems. Without further ado, let’s begin!