It's not often I wish such bad fortune on a new innovation but I am wishing Accelerated Mobile Pages (AMP) dies a quick death.

When I was looking for an alternative to Masonry to produce a responsive Pinterest style grid that was a lot simpler and lighter weight I came across this jQuery plugin on www.jqueryscript.net that is very simple and works well. However, It has a few issues which I needed to fix before I could use it.

Isn't it nice how search engines show a brief section of content with your search terms highlighted in search results?

Recently I've been researching and experimenting with alternate methods to various things involving development, particularly database access, and have come to the conclusion that the systems that we have evolved to today are not ideal.

Any website other than a very simple one uses a database these days, right? Well then why is there a separation between web server and database server? Surely there has to be an advantage in integrating these two systems into one?

I've been looking forward to the release of Bootstrap 4 and finally an Alpha version has been released.

I recently needed to display an implied consent EU cookie law message on a website which uses Bootstrap 3.x and jQuery.

As of July 2015, many of my Classic ASP websites have started logging strange errors, either 80004005 or not reporting any error code at all.

As much as I thought my simple JavaScript solution for responsive web design without media queries was a good idea (and still has a place), I have updated my blog to using the Bootstrap 3 framework.

I have been working on an ASP.NET Web Forms project that is being converted to Bootstrap 3 and have run into a few issues with Modals.

Following on from my last post about improving Bootstrap styling and accessibility for ASP.NET RadioButtonLists and CheckBoxLists, in this post I offer a solution for styling these controls within Bootstrap horizontal forms.

I have wanted to add protection from vavigating away from some of my web forms but most of the solutions I have seen do not work well with ASP.NET with it's many possible ways of posting back and AJAX using Update Panels.

If you come across a problem where you set the Visible property of an ASP.NET control to true in a code behind file, but even when you debug it still shows the value as being false then the problem is most likely to be that the control is inside another control such as a Panel or PlaceHolder that has its Visible property set to false.

I recently experienced an issue with an ASP.NET Web Forms page with various UpdatePanels. The page has two DropDownLists, the selection of one results in populating of possible values in the other, and the selection of the other results in enabling of a Button. Then if the Button is clicked the user is redirected to another website, based on their selection.

Web forms makes it really easy to create a simple website, but it is also really difficult to crate a complicated website. These are some of the things you will need to know sooner or later.

Over fifteen years of developing for the web, I've learned some lessons the hard way. There are some things they don't teach you in books and tutorials.