Working with jQuery solely can be very, very messy, the code can be quite difficult to follow, specially when it grows a lot. What I’m going to expose here is a series of practices and, some code that will allow you to emulate React hooks workflow without requiring any library other than jQuery.

Interfaces, those neat artifacts created to represent contracts to be fulfilled by classes. When appropriately used, they’re a very powerful way to express the expectations a client class has on implementations. Yet, most languages lack of tools to express those aspects you can’t see by looking at the method signatures.

Today while preparing for myself a lemonade, I though: how would I explain recursive functions? I found out that I can’t think of an analogy or metaphor or whatever thing in reality to explain such a weird concept. So the question transformed into: What kind of abstract thing exists that everybody knows and allows one to create rules that, being absurd, can be accepted easily by most people? that is, dreams!

Hosting Nancy in DNN is fairly easy, but it has some gotchas; I’ll explain how to do it with a simple hello world module connected to DotNetNuke via Nancy.Hosting.Aspnet.

In ASP, there is a built-in validation system, it is flexible enough to provide a simple interface to create your own validators:

This article is about comunicating a jax-ws client with a WCF service using certificates having these conditions:

In some rare cases is necessary to filter what users paste in the exact moment they do it, one reason is to allow users to paste URLs with space characters which otherwise would be ignored by any script with the responsibility of converting URLs into links.

These days I’ve been looking at django framework, I need to learn it for my new job, so, while following the django tutorials I realized that for each method in my solution is necesary to configure a URL. That’s not bad at all as it allows the creation of user-friendly urls, but, I’m too lazy to spend my time creating a new line which almost certainly will be a copy of the one on top of it for each module and public method I make.

Well, for many developers too lazy with no time to climb the steep drupal’s learning curve the solution is to simply implement a hook_menu and do the job with plain old PHP.

Well, as this guy said is impossible to put your models in different files due to circular references and multiple sequelize instantiation(?). So, creating a single file is mandatory in order to create complex relationships.