Back in 2012, when I discovered the possibilities of having a rich text input by simply adding the
Continue reading “Yet another developer writing a rich text editor”
contenteditable=true attribute to my element, I tried to build a full content editor. I didn’t know the purpose of it at that point in time, however, it was nice to dig into these new possibilities. I remember it was a simple editor, although you could drop files and images into it, and it would automatically upload the files and attach them to the editor area. Expand the image previews as well. Furthermore, it also embedded content from Youtube and other platforms. It was a lot of fun. It was a lot of o hacks and workarounds as well. Not any longer after that, I sent this idea to the cemetery of side projects.
There’s always that moment when you need to implement authentication and authorization to an application and, besides intercepting and protecting requests, we also need to protect the application’s routes. Angular uses Route Guards through canActivate and or canLoad methods to decide whether a route or a child module should be available or not, and, it can use multiple conditions – or Guards – to decide that.
Continue reading “AccessRole Guard for Angular apps”
I am not judging, although it might appear as I am. I already mentioned a couple of features that make me think Angular is a great choice for a web framework and I’m still decided to invest my time on it. However, I failed by not evaluating it more deeply, to be fair. Anyway, we all have our flaws, don’t we?
Continue reading “Building time is a disappointing issue on Angular development experience”
I have been playing with the latest Angular version for the last couple of weeks and I’m enjoying it. The last time I touched Angular 2+ was in 2016 on an Ionic mobile project and before that, only had experienced working with the now called AngularJS. The current version (7) looks great!
Continue reading “Giving Angular another try”
Recently I was invited to present a talk about front-end development at a company event of my current work, which I did a couple of weeks ago. I was pretty nervous about it mostly for two reasons: a) I never did a presentation to a large audience like this(about two hundred); b) I thought that I needed bring the current most relevant content to that presentation. While I was making the presentation slides I realized that the second reason was about the complexity of front-end development nowadays.
Continue reading “Front-end architecture is everything but simple”
CSS is a convenient programming language, we can be as lazy developer as we want and it will still work. I assume that you know what the results will be if you choose the lazy way. We share techniques and philosophy with software engineering principles, like DRY, Single Responsibility, Open/closed principal, Separations of concerns among others. DRY is a useful principle to get start with CSS if you aren’t yet.
Continue reading “Start by don’t repeating yourself in CSS”