JavaScript Series (01) — Preface. “A Paradigm shift".
How coding used to be done in Javascript until 2016, compared to how it is done now with ES6 onwards, is a paradigm shift. Some posts of this series might be too little too late for the developers who started their careers in the last 5 years. Or others who keep them updated in technologies. Feel free to skip the whole series.
My experience
The last time I worked as a full-scale UI code contributor was in2009 in a small startup. Even after the restrictions, limitations & vulnerabilities of Javascript, what we did at that time was worth acknowledging.
We created a drag-drop-based completely customizable & persistable UI. The whole UI had a hierarchical structure implementing all OOPs concepts using Prototypal Inheritance, designedaccording to then-famous Douglas Crockford lectures. However, now all that seems so trivial compared to what ES6 provides out of the box.
Why now, what now
Why am I talking about ES6 almost 6 years late? I do have a (lame) excuse. With the advent of cloud technologies and the era of specializations, In the last 8–9 years I’ve mostly worked only on back-end design & development.
I kept hearing the UI buzz words and had a high-level idea about them, as to not sound like a fool in tech calls, but I never actually got my hands dirty on the new UI technologies.
So a few months ago, I decided to do what most unsuccessful people always do, “Achieve easy goals in a hard way”. The times when you can create & publish a website with just a few clicks, I tried to design and develop mine from scratch without using any libraries. (Except React modules).
While working on this site, I realized how easy things are in current times. So I decided to document some of my javascript experiences in this series. The advancements in CSS are even more mind-boggling, I’ll put a different series for it.
In the next post, we will look at the major features of ES6. Stay tuned.
Since the beginning of personal computers, few keyboard shortcuts are common among all operating systems and software. The ubiquitous cmd+c (copy), cmd+v(paste) , cmd+z (undo) and cmd+y (redo) I am not sure why, both of my favorite IDEs, Visual Studio Code & Intellij decided to not use cmd+Y for redo.Below are the quick steps to configure cmd+Y for a redo in VS-Code & Intellij Visual Studio Code Open VS Code & Go to keyboard shortcuts There will be a search bar at the top Type “ redo “ in the search bar. You can see on my system its still mapped to shift+cmd+z Double click on ⇧ ⌘ z and the below box will appear. Do not click anywhere or type anything on the keyboard except the key you want to assign, in our case it was cmd+y, so type cmd+y Press Enter and you are done. Now you can use cmd+z for undo and cmd+y to redo like always Intellij It is also as simple as VS-Code...
If you want to avoid overpriced pre-builts like the M1 Mac Mini, Mac Pro, or Dell XPS Desktop without compromising on performance, a self-built desktop is a preferred option. It's also a great choice if you enjoy building things. custom built with ASUS-PRIME-P If you choose to build a custom PC, be prepared to invest time in researching and assembling compatible components. In this post, I'll share my experience building this colorful powerhouse. I'll cover: Why did I do it. Key questions to ask when selecting components Thought process behind component choices Components used in my build Benchmark comparisons . ** My second custom-build **. *** Disclaimer: Not an Apple product. Just a free apple sticker is used *** Why did I do it I decided to get a desktop during the pre-MacM1 era (yes, that’s a thing). After browsing many websites, I found that well-configured prebuilt PCs were overpriced, while cheaper ones had subpar components. Unable to choose betwee...
It's a common use case to have an enterprise application, perform specific work, at a specific time or in response to a specific action. In other words, “There is an ask to execute a Job upon a predefined Trigger ”. This brings us to the need for a Scheduling System. A system, where Jobs & Trigger can be registered and the system will manage the remaining complexity. Thankfully for the Java systems, Quartz is for rescue. It‘s an open-source library that has been extensively used in enterprise applications for more than a decade. Components in Quartz Sub System: Following are the all major component in the Quartz subsystem: Scheduler : It’s the control room of Quartz. It maintains everything required for scheduling, such as managing listeners , scheduling jobs , clustering, transactions & job persistence. It maintains a registry of JobDetails , Listeners & Triggers , and exec...
Once, I was working on a few geospatial APIs handling many time zones. While writing tests, I realized I did not know much about timezones. A lame excuse might be, my subpar schooling as a village kid. Nevertheless, I decided to turn the pages on timezones, what I found was more politics than science. Photo by Arpit Rastogi on Unsplash Before diving into anomalies, let’s talk about history then we will go to science followed by politics. History The world without time zones By 300 BCE, the western world agreed that the earth is round. Each developed civilization devised its unique distinct system to measure distances, times & absolute locations, but relative to prime locations within their civilizations. It all worked in ancient times because long-distance travel was not prevalent among common people. Only merchants or armies traveled long distances. And they already developed systems that worked on their predetermined routes, irrespective of the time differences b...
During our java based microservice development, we extensively use build tools like Maven or Gradle. Usually, IDEs do a lot on our behalf or we just run some predefined commands without checking what's happening inside. Here in this series of 6 posts, I tried to explain Maven. Before I start talking about what Maven is, and its different components, let’s discuss the “why”. Why do we even need Maven? For this, I’ve to first explain the nature of a Java-based project and also need to take you back in history. The “Build” Step. Java is a compilable language, Unlike Python or Javascript, which are interpreted. ie, the code we write in java, can not as-is run on a Java virtual machine (JVM). JVM understands only the bytecode. Therefore, in the Java world, there is always a need for an intermediary step. A step that compiles the java code files into bytecode. That's why after writing the java code, we “somehow” create some deployable (jar, war, ear) to run on ma...
A wise man ( narcissist me ) once said, “Life is all about the question and answers. The trick to a meaningful life is, To ask the right questions to yourself, so you can get on the right path to search for the answer .” The very first question one should always ask oneself is WHY. Let's discuss our WHY in the current case. Why BDD Let's take a step back and start with the well-known software development practice TDD ( Test-Driven Development). In TDD, the very first thing developers do is, set up the technical expectations from the code by writing failing test cases. After the expectation is set, the code is written/modified to finally pass all of the failing tests. It's an Acceptance driven development strategy . TDD works fine to create a robust technically working product. But the whole TDD approach revolves only around technical teams. It barely involves the business analysis or product owners to validate the business aspect of a feature, they get involved o...
Comments