So you want a website
One of the hardest questions to be asked as a programmer who primarily does web development is: 'How much for a website?' It's one of those questions that doesn't really have an exact answer. 'How much do you want to pay for a website?' is probably a better question.
I was tasked with implementing some extra levels of validation on the registration form of a website I built. Registration was a simple AngularJS form that hit an ASP.NET WebAPI endpoint.
Umbraco Specification File
Umbraco is a powerful CMS that isn't overly intrusive. It can work nicely side-by-side your web appliction providing a nice and easy way to manage dynamic content pages. The latest version also has a nice fresh UI.
It's a terrible name, but maybe one day I'll figure a better one. Either way...
I was looking for a method to abstract away integrating my RESTful services for regular CRUD operations. There's ngResource, but it's a bit voodoo and restrictive. I wanted to come up with a solution that was a bit more simplictic that's also not surrounded by magic.
Flask, AngularJS and CORS
I am currently developing a website that will entirely be a Single Page Application (SPA). I started building the back-end in D and the front-end in AngularJS. I decided after a couple of weeks that Jeff Atwood was right in saying 'Storage is cheap, programmers are expensive.' Though D is a useful language, it was taking me too long to produce useful RESTful API endpoints, so I decided to make the switch to Flask given my familiarity with it.
Thoughts on D
I have spent the last few days learning a bit of D, I have contributed to a library, written my own library and developed a basic understanding of the language. It comes across as a very powerful and developer-friendly language. However there are a few downsides to it.
Musings about Web Application Development
In the ideal world is a great way to start any thought, then reality comes in and kills all your big ideas.
Running Jekyll on Heroku
My website once was an ASP.NET MVC website that was very full featured. I realised that most of the features weren't actually being used and I wanted to free up some spacing on my webhost.
Alternative to Entity Framework and the Repository pattern
About a year ago I wrote a post suggesting how one could approach the Repository and Unit of Work patterns when using Entity Framework, at the time I was somewhat new to Entity Framework and it was a shiny new toy that could do everything. Since then I've been involved in quite a few projects and though it is quite a nice framework, I've concluded that it's not the one tool to rule them all. I also realised that the Repository pattern isn't always the best approach to take.