InfernoRed Blog

We love tools that help our clients save time, but some of them are easily misunderstood. Here's the scoop on Xamarin.

1. Maximize UI performance by reducing excess render cycles associated with traditional view nesting
2. Increase maintainability and readability by removing ceremony and keeping layout code concise
3. Simplify usage of RelativeLayout while increasing its power and abstracting away its quirks

In this post I’ll briefly explain what it is, then get into why we need a new UI framework in the context of each of the above three goals.  I'll finish with limitations, some history, and how to get started.

ReSharper can massively boost productivity and improve code quality, while teaching you to be a better developer. In this presentation from NOVA CodeCamp last fall, I distill years spent mastering the tool into a discreet set of 24 tips to help you immediately get more done in less time.

(Read the 24 ReSharper tips here.)

Displaying list data in Android using a custom layout is traditionally accomplished by inflating an AXML file for each row of data.  However, in my article introducing EasyLayout.Droid I made the case that AXML files slow development speed and decrease cross platform re-usability.

If you've done much Xamarin iOS work you've probably run into Frank Krueger's awesome framework, EasyLayout, that makes manually coded auto layouts considerably easier to read and maintain.  

We absolutely love the Hololens, so much in fact that we decided to launch a video series on the Hololens. In this video, Lee Richardson discusses three elements of the Hololens that he feels users will come to appreciate. 

In the first article in this series (Git: Rebase vs Merge) I covered the tactics of rebasing.  I discussed what merge commits are, and how to avoid them with rebasing.  In this post I'll cover the benefits of rebasing, including how its use speeds up finding hard to track down bugs via git blame and git bisect.

I firmly believe ReSharper is the best thing to happen to .Net since Visual Studio (NCrunch is a close second).  In evangelizing it I managed to convince my program to purchase copies for every developer.  One caveat: I had to train everyone.

Distributed version control (git): Check.
Feature branches: Check. 
Rebasing: Ugh, seriously?

On multiple projects I've attempted to introduce the concept of rebasing commits.  It rarely goes well (at first).  The initial reaction tends to be reluctance and confusion.