Making the distinction
As director of software development, it is part of my duty to determine the technological direction of our organization. Over the last several weeks, team members and I have been doing mental exercises imagining a possible reality 3 to 5 years into the future. From there, we work backward and determine what steps can get us to that reality.
. . .
It's my party and I'll cry if I want to
I have a better understanding of the new runtime, the tooling, and the dependencies required to build applications. Although the experience is enlightening, I am leaving behind an old, warm, and comfortable environment for a new, cold, and frustrating one. I fully understand that not every skill I have cultivated will translate over, and I . . .
As a professional and a developer, I find myself practicing four categories of communication: Short Form, Long Form, Graphic and Code. Each type of communication requires a different set of tools. This post lists all the tools I utilize on a day to day basis for each type of communication.
Long Form Tools
I currently work in the healthcare industry and have found that the United States is a wealth of knowledge and data. Much of the data is freely available through web portals and comes in a JSON format. When consuming this data, I have two options:
- Process the JSON into my own proprietary format.
- Use the JSON as-is and leverage a technology . . .
There is a lot of activity happening around ASP.NET 5. To try to keep things straight, I thought I would create a mind map of my current understanding. The image below starts at ASP.NET 5 and branches out to concepts around the growing ecosystem.
What do you think? Is my mind map anywhere close to what you are thinking about ASP.NET 5?
I am starting to develop more with ASP.NET 5. My journey through beta 5 to 8 has been an interesting one, with much left unexplored. This post hopes to poke fun at me. Developers may receive insight into what it is like transitioning to the new platform.
The drumbeat gets louder as we approach a Release Candidate. It is hard not . . .
Stuntman is a .NET library built by RIMdev to give developers access to a set of authentication credentials at development time. It gives me the ability to mock quickly, while not having to deal with a complicated authentication mechanism. I wanted to write a simple ASP.NET 5 banking application utilizing Entity Framework 7. The application . . .