Ever tried to edit sound using Audacity? Did you see the random error that just pops up for some video files? While you could listen the sound from Video, Audacity simply rejects the file from opening? If you are nodding head for most of these questions, you have experienced the same moment that I have been through recently.
We learned few basic Typescript concepts in last video series. This time, instead of just talking to you about the concepts, I felt it is better to make use of examples. The intention is to understand how and where these concepts are used. In addition to that, I have added a few tips to the videos. (I got my hands on After Effects 🙂
So we are moving ahead, with next set of Typescript lessons. The topics discussed in the Part-I focus on Typescript configuration and basic familiarity. The series now progress with experience from real-life project development and my struggle to make sure deliverables meet the quality standards. It is often very easy to develop something and be contained with the thought that we met the expectation. In reality usually what you have created may last for the next 4-5 years. Thus, it is our moral responsibility to adhere to standards.
Past few weeks, I was exploring an alternative platform to share my knowledge with you. I wanted to organize my content in form of Tutorial. I was practicing my communication and presentation skills to work on an interesting concept. Given the pH factor in my blood doesn’t let me settle at one place, I was in search of exploring options to improve my blog content. I confess, sometimes the habit impacts my blog adversely – My Posts gets delayed for longer duration. But this time, I could able to materialize my experiment. I felt accompanying my blog with visual elements and making it more interactive will add value to what I really want to convey. I started my own YouTube channel – Carbonrider. Though I am yet to churn out exhaustive output, let me share few glimpse of my experiences till now.
Material Design started in 2014 and it was introduced by Google to provide a consistent look and feel across browsers. It combines animation effects with soothing colors, shadows, aptly measured margins/padding etc to improve the User experience. Back in the era of Flash/Flex, components designed using Flex has a visual appearance which felt natural. Without any need of adding styles, the plain Flex User Interface felt good. HTML components were lacking such natural appearance. Maintaining consistency across the browser was always a pain. With Material Design the UI aesthetics and interaction has improved dramatically.
Though Angular CLI enables you to quickly get started with creating a new project, it doesn’t come bundled with the Material design. Additional steps are required to integrate the Material Design and apply the styling to the components. In this article, we will learn the steps to integrate Material Design in Angular 6. We will extend this article and build following UI to understand some of the Material Design Components.
In the previous article, we created backend system using AWS Lambda, DynamoDB and API Gateway. Unlike the traditional way of hosting code on an application server, we leveraged AWS serverless technologies to host and deploy APIs. In this article, we will develop frontend code, deploy it using S3 static website hosting and finally access the APIs.
Amazon S3 is one of the industry’s leading solution for storing data. It comes bundled with a lot of features to meet various requirements for building enterprise-grade applications. You can easily host a static website on S3 without worrying about scaling requirements. Store contents securely and enable access to only intended audiences with the click-n-configure interface. With a user intuitive interface, you can manage your storage efficiently. While preparing for the AWS certification, I came across various S3 features which really outshine other Storage options available in the market. I have crafted a few questions which will validate your understanding of Amazon S3. Good luck!!!
Serverless architecture – you might have already heard this term. But have you tried to build one? And do you understand what Serverless architecture really means? Typically a web application requires an infrastructure to host Web Server, Application Server, and Database Server. Traditionally organizations had either their own datacenters or rented servers to manage such requirements. With Cloud – Pay as you use model has gained a lot of popularity. The headache of managing physical infrastructure has been moved to vendors like Amazon, Microsoft, and Google. Given all that, your team is still responsible to provision, monitor and manage the servers.
With Serverless Architecture, Organizations gain total freedom from managing infrastructure and can focus on building functionality. The need for scaling, patching and provisioning servers is opaque to the development team, rather it is a responsibility of a Cloud Vendor. In this article, we will build a Serverless architecture with a Dynamic Web Application using Angular, AWS S3, Lambda, DynamoDB, and API Gateway.
Ok, I know what you are going to say. We have heard of modules with Programming languages, but modules in CSS. Is that even possible? and why do you need it at first place? Well, I had a similar reaction when I heard about it. CSS Modules were born out of the idea of relentless hours spent in debugging issues caused by overlapping CSS selectors, class names. It is a common practice of having multiple style declarations spread across CSS files. The web projects include multiple CSS files to define common layout appearance, widgets etc. This sometimes becomes a nightmare when you have multiple CSS files sharing same class selector.