Wevo Institute - India

Currently, as developers, we are faced with many emerging development technologies such as new languages, frameworks, architectures, methodologies, and other types of development models to improve our software implementation processes. Of all of them, the ones that caught my attention the most are related to software development on LowCode platforms, as they focus not only on development but also on managing the entire process.

What is a LowCode platform?
Initially, LowCode was a software development approach that allowed the creation of applications quickly and with minimal programming, and where fully graphical development platforms are used for deployment. This covers not only the development process, but also the deployment of applications and their administration, thus having under control the vast majority of scenarios needed to develop your process, such as exception handling, alternative flows, and customization options.

The necessity of a rock solid portfolio [Tech Column]

The importance of a proper portfolio cannot be overstated during the process of job search for a developer.

According to the latest statistics from Adecco, over 46% of employers in India will look for a candidate with a strong portfolio, and prioritize portfolio quality over formal education during the interview process.

As such, developing a portfolio that can showcase your programming methodology and talent is of utmost importance for someone that is trying to break into the tech landscape.

Learn how our career specialists can help you out with our full-stack software engineering bootcamp coming up in March.

Let's congratulate our cohort students for completing a charity event hosted for teenagers in need based in Mumbai. Our participants had designed a curriculum and conducted a brief set of lessons for these passionate learners and delivered content that they had learnt during our bootcamp. Great job guys!

[JavaScript Revision 101]

At its simplest, JavaScript is made up of a series of statements and semi-colons.

A statement is like a sentence — but in code.

For example, this is a statement:

alert('Say hi');
Semi-colons are not compulsory and can be committed when there is a physical line break in between. It’s the equivalent of a full stop.

But sometimes, line breaks do not guarantee that the statement is done. Using + signs can act as a connector between lines.

For example:

console.log('This ' + name + ' is gibrish');

Brief industry comparison of React and Vue.js

React
React.js is flexible and open to a variety of choices. It doesn't imply any opinionated direction or mentality for development. However, this approach has some cost because the developers need to have a strong knowledge of JavaScript and be experienced with Single page applications (SPA) design.

Pros of React:
Fast client-side rendering.
Good control of the data flow.
Light-weight architecture.
Extensibility and scalability.
Large community support.

Cons of React:
Steep learning curve.
Does not operate without other libraries and services, like Redux, routing, etc.
Structure-free code may get to spaghetti and boilerplate.

What companies should choose React:
Early-stage startups that need fast feature development and validation campaigns on the market.
Companies that are looking to outsource their development. It is much easier to find a React developer compared to the one with Vue.js expertise.
Product-based companies will also require cross-platforming app development (React Native based on React technology, that it will be a good fit).

Vue.js
Vue.js combined the top-level features of React and Angular, but its main feature is the perfect user experience. Also, it leveraged the capacity of the virtual DOM and optimized the code structure.

Pros of Vue.js:
Elegant language syntax.
Fine user documentation.

Cons of Vue.js:
Lack of experienced developers.
Small community.
A big part of the documentation is written solely in Chinese.

What companies should choose Vue.js:
Companies that approach the market of web-based products.
Companies that are looking to implement a single flow in their development process.
Companies with no previous experience of using frameworks in their build process or those looking to leverage their proficiency with JavaScript.

About AJAX - The technique that changed web development

In the early-to-mid 1990s, most Web sites were based on complete HTML pages. Each user action required that a complete new page be loaded from the server. This process was inefficient, as reflected by the user experience: all page content disappeared, then the new page appeared. Each time the browser reloaded a page because of a partial change, all of the content had to be re-sent, even though only some of the information had changed. This placed additional load on the server and made bandwidth a limiting factor on performance.

In 1996, the iframe tag was introduced by Internet Explorer; like the object element, it can load or fetch content asynchronously. In 1998, the Microsoft Outlook Web Access team developed the concept behind the XMLHttpRequest scripting object.[4] It appeared as XMLHTTP in the second version of the MSXML library,[4][5] which shipped with Internet Explorer 5.0 in March 1999.[6]

The functionality of the Windows XMLHTTP ActiveX control in IE 5 was later implemented by Mozilla Firefox, Safari, Opera, Google Chrome, and other browsers as the XMLHttpRequest JavaScript object.[7] Microsoft adopted the native XMLHttpRequest model as of Internet Explorer 7. The ActiveX version is still supported in Internet Explorer, but not in Microsoft Edge. The utility of these background HTTP requests and asynchronous Web technologies remained fairly obscure until it started appearing in large scale online applications such as Outlook Web Access (2000)[8] and Oddpost (2002).

Google made a wide deployment of standards-compliant, cross browser Ajax with Gmail (2004) and Google Maps (2005).[9] In October 2004 Kayak.com's public beta release was among the first large-scale e-commerce uses of what their developers at that time called "the xml http thing".[10] This increased interest in Ajax among web program developers.

The term AJAX was publicly used on 18 February 2005 by Jesse James Garrett in an article titled Ajax: A New Approach to Web Applications, based on techniques used on Google pages.[1]

On 5 April 2006, the World Wide Web Consortium (W3C) released the first draft specification for the XMLHttpRequest object in an attempt to create an official Web standard.[11] The latest draft of the XMLHttpRequest object was published on 6 October 2016,[12] and the XMLHttpRequest specification is now a living standard.

Content Model 101 For Beginners [Tech Column]

A semantic content model uses type and attribute names that reflect the meaning of the content, not how it will be displayed. For example, in a nonsemantic model, teams might create types like teasers, media blocks, and cards. Although these types might make it easy to lay out content, they don’t help delivery channels understand the content’s meaning, which in turn would have opened the door to the content being presented in each marketing channel. In contrast, a semantic content model uses type names like product, service, and testimonial so that each delivery channel can understand the content and use it as it sees fit.

When you’re creating a semantic content model, a great place to start is to look over the types and properties defined by Schema.org, a community-driven resource for type definitions that are intelligible to platforms like Google search.

It is with great concern and disappointment that our Facebook and Instagram page was shut down by moderators without any forewarning on Jan 5 (Wed). After our team had made contact with support representatives from Facebook multiple times for over a week, no proper explanation was offered officially regarding this matter.

As a result of this unfortunate incident, Wevo Institute will now migrate its social media content over to this official page. It Is uncertain whether the unexplained ban would be lifted by support representatives from Facebook, and we are extremely disappointed by the way the incident was handled.

It is upsetting to see the work of our alumni and colleague being wiped out in such a manner. Nonetheless, our team will stay strong and continue to offer new content about digital careers. In the meantime, we would deeply appreciate any help offered by our supporters. Simply liking and sharing the page would take us one step closer to recouping the loss.

Shikha Palsania,
Community Manager @ Mumbai Campus