Node.JS

Given the diverse range of responsibilities and technologies out there today, it is no wonder companies choose to employ full stack development services to achieve end goals without hiring multiple people and struggling to attain streamlined workflows.

What is full-stack development?

Full-stack development services refer to the development of both client-side and server-side interfaces of any application. In technical terms, these are the front-end and back-end, respectively.

A client-side-only developer typically is responsible for what users see and can interact within an application or a website. They use a specific set of languages, including HTML and CSS. They also use particular frameworks and libraries that include AngularJS, Bootstrap and ReactJS. On the other hand, a back-end developer typically focuses on how the website works and is built. The primary languages are Python, JavaScript and C++ among others.

To hire a full-stack web developer is to get someone who is well-versed in both front-end and back-end development and has the skills and technological prowess to step in at any stage of a project.

What qualities does the ideal full-stack developer possess?

If you’re looking to hire a remote full-stack web developer or a full-time one, consider looking out for these qualities:

• Mastery over front-end technologies
• Knowledge of at least one server-side programming language
• Concrete understanding of DBMS technology
• UI/UX design skills
• Experience in handling servers
• Knowledge of Git and version control systems
• In-depth understanding of web services or API
• Awareness of security concerns and frameworks
• Understanding of algorithms and data structure

With ML projects still on the rise we are yet to see integrated solutions in almost every device around us. The need for processing power, memory and experimentation has led to machine learning and DL frameworks targeting desktop computers first. However once trained, a model may be executed in a more constrained environment on a smartphone or on an IoT device. A particularly interesting environment to run the model on is browser. Browser-based solutions may be used on a wide range of devices, desktop and mobile, online and offline. The topic of this post is how to prepare a model for the in-browser usage.

This post presents an end-to-end implementations of a model creation in Python and Node.js. The end goal is to create a model and to use it in a browser. I'll use TensorFlow and TensorFlow.js as main frameworks. One could train a model in Python and convert it to JS. Alternative is to train a model directly in javascript, hence omitting the conversion step.

I have more experience in Python and use it in my everyday work. I occasionally use javascript, but have very little experience in the contemporary front-end development. My hope from this post that python developers with little JS experience could use it to kick start their JS usage.

Do you know Node.js has turned 11 on 27th May 2020? Can’t believe we have stepped into a new decade of this technology? Okay! Let me tell you the truth and story behind it with this article.

JavaScript has come a long way with its constant bombardment of open-source frameworks. We all have embraced its journey, and Node.js is one of its prevalent and predominant innovations that knocked this tech arena on May 27th, 2009. So, technically and mathematically, both Node.js is 11 years old now.

Choosing between Node.js and Ruby on Rails, when choosing a development platform, is a core decision. That affects how the project unfolds over time, and how much server resources will be needed. Both languages can support web applications of high complexity, but each has its advantages and disadvantages. Knowledge of these pros and cons will help to choose the best solution for the proposed project. Let's analyze in more detail and tell you about our choice and experience.

• Looking for the best node.js framework for web or mobile application development?
• Searching for top node.js frameworks for the year 2020?
• Hunting for topmost node.js frameworks to stay ahead in the competition? 

Here, in this blog, you will get the answers to all such questions. Let's quickly dive into it!

---

What is a Node.js Framework?

Node.js framework is a combination of libraries, helpers, and tools that offer a way to create and operate web applications in an uncomplicated manner. A node.js framework builds the base layer for creating a web app. 

The most important aspects of node.js framework, like any web framework, are its architecture and features such as support for customization, flexibility, security, compatibility with other libraries. 

If you are landing on this page you might be looking for several questions like:

– NodeJS or Python: which is the right choice for my next web app development project?

– Which programming language cost me less?

– Which programming language is suitable for which industry?

– Which programming language is suitable for small business or large scale enterprises?

– Which programming language is scalable, high performing and secure?

In this blog post, I’m going to answer all these questions AND MORE THAN THAT! So, continue reading this blog post:

In the online advancement world, Node.js and PHP are the most well-known programming languages being used. Although both of these languages are able to manage the applications of any sort of complexity, they are being built around the different concepts & architectures. If you are an app owner or looking to develop a website, you might be wanting to choose between these two environments, therefore, you must know about the major differences, advantages, and limitations of the two languages.

Have you ever wanted to have a swagger documentation for your express API based on annotations? I have. And unfortunately didn’t find any way of doing it without having to manually create a swagger.json file. My wish was simple as this: I want to have a clean express app with multiple endpoints and I want to keep swagger documentation for every endpoint close to the endpoint implementation, not in a separate file.

Maybe I’m just lacking some google skills, but I decided that it’d be much easier for me to create such a tool. And here it is: mgr-swagger-express

I hope that you will find Node version 12 new capabilities compelling and soon you will upgrade your app to it.

In turn, you will get advanced debugging, intelligent coding with the powerful IntelliSense engine, interactive window, quick tracking of performance issues, unit testing, typescript integration, source control, cloud integration, and npm integration.

To get started in this walkthrough, this post captures the steps on how to update Node.js in Visual Studio, Windows/macOS, and NPM.

JavaScript developers, I am working on an exciting opensource project pursuing two goals:

1. Learning best practices in JavaScript/NodeJS
2. Helping developers and myself to develop and launch MVPs to validate ideas quickly.

As developers, we have tons of ideas and would be awesome to have a simple tool to scaffold a secure project quickly, add a couple of forms, some project specific logic, and here you go — deploy and test your idea.

How many times did you write logger.info('ServiceName.methodName.') and logger.info('ServiceName.methodName -> done.') for each and every method of your service you wanted to log? Would you like it to be automated and has the same constant signature across your whole app? If that's so, we're very much alike, we have suffered the same pain too many times, and now we could finally try to resolve it. Together. Ladies and gentlemen, let me introduce… class-logger!

This is the second part of a post about the creation of a pipeline that can take a Sketch file and export all the icons included in the file, in different formats, for different platforms, with the possibility of AB testing each icon.

You can read the first part of the post here.



The Sketch files, with all the icons collected, styled and properly named, were ready. Now it was time to start writing the code.

Suffice to say, the process was very much a trial and error: after the important initial code core, developed by my team lead Nikhil Verma (who set the script foundations), I went through an incremental process that required at least three phases of refactoring and quite a few revisions. For this reason, I won’t go into too much detail on how the script was developed, but rather focus on how the script works today, in its final shape.

What's nagging you the most when you think about logging in NodeJS? If you ask me I'm gonna say lack of of industry standards for creating trace IDs. Within this article we'll overview how we can create these trace IDs (meaning we're going to briefly examine how continuation local storage a.k.a CLS works) and dig deep into how we can utilize Proxy to make it work with ANY logger.

TL;DR

Using a custom build script in Node JS, it is possible to manipulate a series of Sketch files, and then, using an internal Sketch tool, automatically export their assets, to generate multiple icon libraries, for multiple platforms and different brands, that support dynamic colourisation of the assets via design tokens, and also AB testing of the assets via naming convention. Easy peasy :)

---

Well, actually it’s not that easy, but it can certainly be done. This post is a detailed explanation of how we did it, and what we discovered along the way.

The problem we were trying to solve

At Badoo we build a dating app. Actually, multiple dating apps. For multiple platforms (iOS, Android, Mobile Web, Desktop Web), across multiple teams.

We use hundreds of icons in our apps. Some of them are the same across different apps, some are very specific to the brands the apps reflect. The icons are continuously evolving, in sync with the evolution of the design. Sometimes completely new icons are added, while others get updated, and still others get dropped (although, they often remain in the codebase).