CodeIsGo.com

Judah Gabriel Older article by Hugo Messer and John Okoro about Agile distributed teams. Distributed teams are the norm for many organisations today. Companies are global, communications technologies allow people to live away from the “office” location and many of the new workforce are nomads.

Becoming a high-performing team is possible in a distributed group, it just takes more effort to overcome the inherent challenges of distance.

In this inspiring article you will get plethora info on:

• Introduction to the distributed agile framework
• Learn how to manage culture within distributed teams
• Learn how to organize distributed work within an enterprise
• Practical examples and cases of distributed agile organizations
• Questions, virtues and practices to organize better distributedly

Authors also open sourced a big part of their own agile framework. The framework we have developed consists of 8 ‘bubbles’ including culture, organization, team, engineering practices. Read to learn more!

Graphcool published tutorial about GraphQL bindings. With GraphQL bindings you can embed existing GraphQL APIs into your GraphQL server. In this article, they present a new application of schema stitching which makes it particularly easy to reuse, compose and share existing GraphQL APIs: GraphQL bindings.

GraphQL bindings take the idea of schema delegation to the next level and make it easy to reuse, embed, compose and share GraphQL APIs.

Articles then explains what what are GraphQL bindings together with simple code examples. The major strength of GraphQL is its strongly typed schema.

Some benefits of using GraphQL bindings:

• Pragmatic API & simple abstraction
• Great IDE support: Autocompletion and other awesome IDE features
• Reusable: Can be easily shared as reusable packages using NPM (or other package managers)
• Compile-time error checking: Static bindings allow for static analysis
• Language agnostic: Works with any (typed) programming language

Excellent article for anybody in the APIs business.

Judah Gabriel wrote this post about his experience with PWA publishing. The article is about turning a web app into a Progressive Web App (PWA) and submitting it to 3 app stores requiring about a month of work, a few hundred dollars, and lots of red tape.

The article reads about:

• Why even put your app in the app stores (it is web app after all)
• Explains “horrible” brokenness of PWA for native phone capabilities
• Lists the barriers to get app in the app store
• App stores registration process
• App packaging, building, submitting
• App testing process
• Submitting for app review

This is one lengthy tutorial explaining all the pain points you may encounter when submitting to the app stores (Apple, Google, Windows). Well worth your time!

In this article Tyler Argo wrote how Yelp has been working hard to improve the performance of their search results on mobile devices (iOS and Android). We noticed that most users “grunted or made noises when waiting for search to load”.

They broke down performance into two different categories: perceived search performance and scroll performance.

They then broke the cycle of performance improvement can be defined as a series of steps:

• Measure
• Improve
• Monitor
• Repeat

In this article they focuse on Step 1: Measuring Performance. One of the advantages of developing for the Android platform is the wide range of tools available for profiling and measuring app performance. In the article they provide a brief overview of the tools that can be used to profile your app along with some links to the official documentation. Great read!

Simon Reimler published this article about working with canvas in Ionic. Working with the canvas can be challenging, but there are amazing things you can build with canvas. In the tutorial we will implement a canvas inside an Ionic app on which we can draw in different colours.

He then goes and explains:

• Set up blank Ionic app with crucial Cordova plugins
• How to build the Canvas Drawing View
• Prepare Canvas and how to paint on them
• How to save canvas images

It’s actually not super hard to build your own drawing app, and working with the file system has gotten so much easier.

You will find code examples with this article to help you set up your Ionic app. And you can also find a link to video version of the article. Nice!

Paul Armstrong interesting article about a look into removing common and uncommon performance bottlenecks in one of the worlds largest React.js progressive web apps, Twitter Lite. Creating a fast web application involves many cycles of measuring where time is wasted, understanding why it’s happening, and applying potential solutions.

Performance is a continuous game of watching and measuring for areas to improve.

The article focuses on few areas:

• Optimizing for the Browser
• Optimizing React
• Optimizing Redux
• Service Workers

Each section contains detailed information what to focus on and what steps to take to mitigate performance bottlenecks. It is invaluable insight into React.js deployment in production. Great read!

Idorenyin Obong from Auth0 wrote this piece about practices in Android development. Best practices are simply professional standards that are acceptable in a field. Here, we will look at such practices as it relates to Android development.

Android has about 74% of the mobile operating system market share according to StatCounter as at February 2018.

If you are building for billions of users, you have to grow above just building just for the functionalities. You have to consider other factors such as scalability, better user experience, etc.

Recently, there has been lots of promise in Android development since the formal introduction of Kotlin, statically typed programming language that runs on the Java virtual machine, with some interesting features including – null safety, smart inference, interoperability with Java, can be compiled to JVM bytecode or JavaScript.

The article then deals with:

• Design Patterns
• Dependency injection (DI)
• Separation of Concerns (SoC)
• User Experience
• Excellent UI

There is much more in the article, with example code snippets and charts accompanying the text. Good read!

Insidebigdata team wrote this article in which they provide 30,000 feet overview of Apache Kafka architecture. Kafka, the distributed streaming platform, features an architecture that provides application messaging that is very clear.

Kafka’s main architectural components include Producers, Topics, Consumers, Consumer Groups, Clusters, Brokers, Partitions, Replicas, Leaders, and Followers.

A fundamental explanation of Kafka’s inner workings goes as follows: Every topic is associated with one or more partitions, which are spread over one or more brokers.

It’s important to note the relationships between broker, replica, and partition components, such as:

• Kafka clusters can have one or more brokers
• Brokers can host multiple replicas
• Topics can have one or more partitions
• A broker can host zero or one replica per partition
• A partition has one leader replica and zero or more follower replicas

You will discover more relations following the article. And authors also make use of UML diagrams to explain architecture in greater detail. Great read!

An article by Agilemodeling in which they focus on important aspect of architecture in agile scaling. Contrary to popular belief, architecture is an important aspect of agile software development efforts. An architecture is a critical part of scaling agile approaches to meet the real-world needs of modern organizations.

Architecture provides the foundation from which systems are built and an architectural model defines the vision on which your architecture is based.

The article then (in details) explains topics and issues related to agile scalability, e.g.:

• How to gear up for agile architecture
• Architecture throughout the lifecycle of Agile Model Driven Development (AMDD)
• Who is responsible for architecture?
• Have an “architecture owner” role
• Agile architecture at scale
• Base your architecture on requirements
• Model your architecture
• Consider several alternatives
• Remember enterprise constraints

Much more could be learnt from this in depth article. If you are in the Agile business, this blog post is definitely worth your time!

An article by Cloudways in which they deal with different roles and permissions in typical web application. To verify the users, applications need to have an authentication module or functionality. Using Middleware, you can easily implement multiple authentication in Laravel. Middleware provides a convenient mechanism for filtering HTTP requests entering your application.

In this tutorial they use PHP 7.1, MySQL, Laravel 5.5. The author then explains:

• How to create Laravel app
• Use composer for dependencies installation
• Configure the MySQL database
• Set admin Middleware
• How to run database migration
• How to use built in Middleware admin

The tutorial contains plenty of code examples and it will help you to setup Multiple Authentication in Laravel projects. Good work.