Are you our next hire?

  • We are a young company still establishing our stack and processes, so being open to trying new languages and technologies is a must, as is putting forth honest and reasoned opinions on what works and doesn’t.
  • At the moment we are using ReasonML, GraphQL, JavaScript, Python, React Native, Docker, MYSQL, RethinkDB, and AWS Lambda.
  • We are looking for a new developer, whose first responsibility will be writing React Native apps in ReasonML.
  • You don’t have to have experience with these technologies, as long as you are willing and able to learn – – We expect you to have a good understanding of JavaScript, HTML/CSS, and web development in general.

We are a young company still establishing our stack and processes, so being open to trying new languages and technologies is a must, as is putting forth honest and reasoned opinions on what works and doesn’t. At the moment we are using ReasonML, GraphQL, JavaScript, Python, React Native, Docker, MYSQL, RethinkDB, and AWS Lambda.
Continue reading “Are you our next hire?”

Building Web at UrbanClap — The React Way – UrbanClap Engineering – Medium

Building web at @UrbanClap — The #ReactJS way:  #JavaScript #frontend

  • Each React component is readable and maintainable and you know where to make the changes and how your changes will affect the complete system.
  • You have the power to reuse the components as building blocks for the system.
  • Using shouldComponentUpdate , we can also optimise the rendering of react components as per requirements and minimising costly dom operations.
  • Facebook has provided a Rect dev tool as chrome extension to inspect the components.
  • Data is trickled down from parent component to child components.

At UrbanClap, we love exploring new things — new libraries, frameworks and new ways of doing things more efficiently. We love anything that makes our work efficient by adding more value to our…
Continue reading “Building Web at UrbanClap — The React Way – UrbanClap Engineering – Medium”

Server Side Rendering vs Client Side Rendering ?

Basic diff. between Server Side Rendering vs Client Side Rendering : 

#JavaScript #ReactJS

  • Very simple put, in this model, the server provides with a page which is already populated with the data.
  • It’s just that your server uses the same templates/components to render the app on server.
  • Say you have a simple web application which displays the pictures of cats, and people can vote on how cute a cat is.
  • server.route( { method: ‘GET’ , path: ‘/cats’ , handler: ( request, reply ) => { /* For the sake of this example, imagine that the constant `data` is already populated with the data; similar to the JSON I have in the previous example */ const cats = …
  • Server-side Rendering — the server sends a pre-rendered (i.e., all the steps I outlines above been executed on the server-side) page, and that is displayed to the user.

Read the full article, click here.


@Hashnoder: “Basic diff. between Server Side Rendering vs Client Side Rendering :

#JavaScript #ReactJS”


Can some help me to understand the basics of server side rendering and client side rendering? And also the difference between them? When to use what? etc… Tagged with Programming.


Server Side Rendering vs Client Side Rendering ?