In the last Blog we have discussed the basics of BSC, let's start a discussion about four perspectives of BSC.

A Balance Scorecard looks at an organization from four different perspectives to measure its health, each of these perspectives focuses on various sides of the company and creating a balanced view of the organization.

And yes all four areas of BSC are interrelated we cannot ignore any out of four to the success of the organization.

Financial Perspective:

This perspective views organizational financial performance and the uses of financial resources.

We need to focus on two points:

• Is the company achieving its financial goals?
• How well the strategies and operations contribute to improving financial health?

Well, now the question is how we can measure the output of the financial perspective?

these data always past focused, we need to gather two types of data. 

1. Historical Data: How did we do last month, last week, last year, and so on.
2. Current Data: How we are doing right now, Today?

For instance, 

1. our net profit for the year versus last year
2. Our sales revenue this year versus last year

These measures of corporate performance are based on history and also vary from organization to organization. 

As the BSC is holistic approach, any key objectives that is related to company's financial health and the performance may include in this perspective as given below:

• Cost Saving and Efficiencies [Specified Goals: Reduced production cost 10% by 2021]
• Profit Margins [increase operational profit Margins]
• Revenue Sources [adding new revenue channels/department/products]

In the end, 

• Are you making money?
• Are your investors happy?   
  If yes then be happy...

The financial health of your organisation may be the indicators of your past decisions but still incredibly important.

' Money keeps the company alive ' and the financial perspective focus solely on this. 

Internal Process Perspective:

This perspective views various organizational processes and the efficiency of the particular process. 

1. from this view, the question should be asked what internal processes have added values within the organization and what activities need to carry in the organization (In all three perspectives).
2.  The internal Process perspective looks at how smoothly your business is running (Here, Efficiency is important )
3. It's all about,

• Reducing waste, 
• Speeding process/ production
• Doing more with less

We need to focus on three points:

• Is the company improving the critical process?
• Are there any obstacles standing between ideas and execution?
• How quickly you can adapt to changing business conditions?

This perspective answer the question :

"what process we must excel at to satisfy our shareholders/financial Backers and customers?"

To know more about BSC please read my weekly Blog.

1. Remember only you are not interviewing
2. Look back years of candidate's career
3. Trust your Gut
4. Don't be boring Interviewer 
5. Represent Job Description
6. Think like Marketer 

In the previous article, we learned 4 cases for how to  test  Android Applications.

In this article, we will learn more cases for how to  test  Android Applications.

5. Compatibility testing test cases

1. Have you tested on the best test devices and operating systems for mobile apps?
2. How does the app work with different parameters such as bandwidth, operating speed, capacity, etc.?
3. Will the app work properly with different mobile browsers such as Chrome, Safari, Firefox, Microsoft Edge, etc.
4. Does the app's user interface remain consistent, visible and accessible across different screen sizes?
5. Is the text readable for all users?
6. Does the app work seamlessly in different configurations? 

6. Security testing test cases

1. Can the mobile app resist any brute force attack to guess a person's username, password, or credit card number?
2. Does the app allow an attacker to access sensitive content or functionality without proper authentication?
3. This includes making sure communications with the backend are properly secured.  Is there an effective password protection system within the mobile app?
4. Verify dynamic dependencies.
5. Measures taken to prevent attackers from accessing these vulnerabilities.
6. What steps have been taken to prevent SQL injection-related attacks?
7. Identify and repair any unmanaged code scenarios
8. Make sure certificates are validated and whether the app implements certificate pinning
9. Protect your application and network from denial of service attacks
10. Analyze data storage and validation requirements
11. Create  session management to prevent unauthorized users from accessing unsolicited information
12. Check if the encryption code is damaged and repair what was found.
13. Are the business logic implementations secure and not vulnerable to any external attack?
14. Analyze file system interactions, determine any vulnerabilities and correct these problems.
15. What protocols are in place should hackers attempt to reconfigure the default landing page?
16. Protect from client-side harmful injections.
17. Protect yourself from but vicious runtime injections.
18. Investigate and prevent any malicious possibilities from file caching.
19. Protect from insecure data storage in app keyboard cache.
20. Investigate and prevent malicious actions by cookies.
21. To provide regular checks for the  data protection analysis
22. Investigate and prevent malicious actions from custom-made files
23. Preventing memory corruption cases
24. Analyze and prevent vulnerabilities from different data streams 

7. Localization testing test cases

1. The translated content must be checked for accuracy.  This should also include all verification or error messages that may appear. 
2. The language should be formatted correctly.(e.g. Arabic format from right to left, Japanese writing style of Last Name, First Name, etc.) 
3. The terminology is consistent across the user interface. 
4. The time and date are correctly formatted. 
5. The currency is the local equivalent. 
6. The colors are appropriate and convey the right message. 
7. Ensure the license and rules that comply with the laws and regulations of the destination region.
8. The layout of the text content is error free. 
9. Hyperlinks and hotkey functions work as expected. 
10. Entry fields support special characters and are validated as necessary (ie. postal codes)
11. Ensure that the localized UI has the same type of elements and numbers as the source product. 

8. Recoverability testing test cases

1. Will the app continue on the last operation in the event of a hard restart or system crash?
2. What, if any, causes crash recovery and transaction interruptions?
3. How effective is it at restoring the application after an unexpected interruption or crash?
4. How does the application handle a transaction during a power outage?
5. What is the expected process when the app needs to recover data directly affected by a failed connection? 

9. Regression testing test cases

1. Check the changes to existing features
2. Check the new changes implemented
3. Check the new features added 
4. Check for potential side effects after changes start 

That's it. If you want a good application, take these tips and follow cases for Android Application test. It will help to make quality & standardize your Applications.

1. Bad lines in the logo

When the characters and design elements in the logo are drawn or modified, great care should be taken by the graphic designer. The lines and dots inside the logo should be smooth and clean. In the logo design example below, you will see how the inside line of the letter does not have a curve towards it. This is one of the most common problems we see in poorly made logos.

Logo files are made up of many dots and lines. When the logo is small, these imperfections may not be significant, but as the logo gets bigger the issue becomes more obvious and problematic. You should have a graphic designer who will fix the curves and lines of the logo. Then use the new files to replace the problem logo.

2. Improper Alignment of Logo Elements

Since graphic designers create logos, they are composing letters and design elements. They have complete control over the sizing and alignment of objects. With all this control, and especially the number of elements or characters is likely to increase that something does not adjust as it should.

As with the "bad lines" example above, a small logo size can hide problems when compared to an extended version. But on the screen or in digital access, cutting your logo the wrong way causes it to look blurry (due to pixel interpolation, solid dark pixels are divided into multiple lighter pixels). Graphic designers can adjust the arrangement of elements using the Snap-to-Grid or Snap-to-Guide feature, functions available in Adobe Creative Cloud software. This process will ensure that items are arranged just like your logo.

3. Missing Font in Logo

A logo design should always be presented as a piece of artwork composed of lines and points or pixels. Unfortunately, this is not always the case. If a graphic designer used a particular font in your logo, you may not have that font on your, or your vendor’s, computer. A missing font often leads to it being substituted by another font available on the computer. It’s a major problem that prevents anyone who doesn’t have the font to see the logo properly. This even holds true for a graphic designer trying to fix the problem.

As a logo is designed, fonts are commonly used either as they are, or as a starting point to be modified for the design. The important step in the logo design process is to “outline” the letters being used in the logo so they become a piece of artwork rather than letters you can edit by typing. Once this process has been done, it is not reversible and the font will no longer be required to view and reproduce the logo. Be aware that fonts can cost between $20 and $150 or more just for one weight, such as Helvetica Neue Bold.

4. The Incorrect Logo File Format

Another one of the most common issues we see with logos that are supplied to us is that they are not in the correct file format. If your graphic designer comes to you and says “it’s not the right format” it can mean a few things. However, if your designer intends on using the logo, it is not going to work.

The most common incorrect file format we receive is a raster logo such as a .jpg rather than a vector logo, such as a .eps. A .jpg logo might be fine if the resolution is high enough and it does not require being produced on a color or transparent background. Vector logos will offer a graphic designer the most options, including saving the artwork to other file formats. A vector logo can be enlarged or reduced infinitely without losing quality.

5. The Incorrect Logo Color Format

A less common but potentially more challenging logo file format issue is the color mode. A logo that is being printed on paper, on a t-shirt, or being included on a website will have different color spectrum requirements. Some can be easily converted from one to another but others cannot. Again, a vector logo will offer a graphic designer the best chance to fix the issue.

Logo Design Done Right

We have recently developed a site into the gatsby.

We have a blog site and hosted it on a different domain but now we want to move to one place at our main site. now, we have challenges for displaying dynamic blogs on the gatsby site.

Finally, I found that gatsby provides support to render dynamic blogs as a static page. when build created that time fetch the blogs from the server and create a static page for all the blogs.

Gatsby is a very good platform and manages such a kind of thing easily.

So, I will show you how to create static pages from the API response into the Gatsby site.

Here are the steps you need to follow correctly.

Steps 1

Create a one blog file where you want to load a blog in your design.

For an ex. I created a file `blog/index.js` inside the component directory and the code looks like this,

Steps 2

Open a file `gatsby-node.js`

Declare the const for the API URL at the beginning of the file.

const blogURL = 'http://blog-api.com/api/posts';
We need to create an instance of the  `node-fetch` for fetching a data from API server.

const fetch = require(`node-fetch`);

Import the path for a resolve the page while creating a static page.

const path = require('path');
See the example how to create a static page from APIs. code look's like,
exports.createPages = (async ({graphql, actions}) => {
    const blogs = await fetch(blogURL);
    blogs.data.forEach((blog) => {
        createPage({
            path: 'blog/' + blog.slug,
            component: path.resolve(`./src/components/blog/index.js`),
            context: {
                // Data passed to context is available
                // in page queries as GraphQL variables.
                slug: blog.slug,
                blog: blog,
            },
        })
    })
Now we are done, and you can access blogpage via slug.

Create a Zoom Application

1. Go to Zoom marketplace and do sign in
2. Click Develop button on header and select Build App menu.
3. Choose the JWT and create an application with the app name that you want.
4. Input required information and click Continue until your app will be activated. 

composer require firebase/php-jwt
composer require guzzlehttp/guzzle

ZOOM_API_URL="https://api.zoom.us/v2/"
ZOOM_API_KEY="INPUT_YOUR_ZOOM_API_KEY"
ZOOM_API_SECRET="INPUT_YOUR_ZOOM_API_SECRET"

<?php

namespace App\Traits;

use GuzzleHttp\Client;
use Log;

/**
 * trait ZoomMeetingTrait
 */
trait ZoomMeetingTrait
{
    public $client;
    public $jwt;
    public $headers;

    public function __construct()
    {
        $this->client = new Client();
        $this->jwt = $this->generateZoomToken();
        $this->headers = [
            'Authorization' => 'Bearer '.$this->jwt,
            'Content-Type'  => 'application/json',
            'Accept'        => 'application/json',
        ];
    }
    public function generateZoomToken()
    {
        $key = env('ZOOM_API_KEY', '');
        $secret = env('ZOOM_API_SECRET', '');
        $payload = [
            'iss' => $key,
            'exp' => strtotime('+1 minute'),
        ];

        return \Firebase\JWT\JWT::encode($payload, $secret, 'HS256');
    }

    private function retrieveZoomUrl()
    {
        return env('ZOOM_API_URL', '');
    }

    public function toZoomTimeFormat(string $dateTime)
    {
        try {
            $date = new \DateTime($dateTime);

            return $date->format('Y-m-d\TH:i:s');
        } catch (\Exception $e) {
            Log::error('ZoomJWT->toZoomTimeFormat : '.$e->getMessage());

            return '';
        }
    }

    public function create($data)
    {
        $path = 'users/me/meetings';
        $url = $this->retrieveZoomUrl();

        $body = [
            'headers' => $this->headers,
            'body'    => json_encode([
                'topic'      => $data['topic'],
                'type'       => self::MEETING_TYPE_SCHEDULE,
                'start_time' => $this->toZoomTimeFormat($data['start_time']),
                'duration'   => $data['duration'],
                'agenda'     => (! empty($data['agenda'])) ? $data['agenda'] : null,
                'timezone'     => 'Asia/Kolkata',
                'settings'   => [
                    'host_video'        => ($data['host_video'] == "1") ? true : false,
                    'participant_video' => ($data['participant_video'] == "1") ? true : false,
                    'waiting_room'      => true,
                ],
            ]),
        ];

        $response =  $this->client->post($url.$path, $body);

        return [
            'success' => $response->getStatusCode() === 201,
            'data'    => json_decode($response->getBody(), true),
        ];
    }
    
    public function update($id, $data)
    {
        $path = 'meetings/'.$id;
        $url = $this->retrieveZoomUrl();

        $body = [
            'headers' => $this->headers,
            'body'    => json_encode([
                'topic'      => $data['topic'],
                'type'       => self::MEETING_TYPE_SCHEDULE,
                'start_time' => $this->toZoomTimeFormat($data['start_time']),
                'duration'   => $data['duration'],
                'agenda'     => (! empty($data['agenda'])) ? $data['agenda'] : null,
                'timezone'     => 'Asia/Kolkata',
                'settings'   => [
                    'host_video'        => ($data['host_video'] == "1") ? true : false,
                    'participant_video' => ($data['participant_video'] == "1") ? true : false,
                    'waiting_room'      => true,
                ],
            ]),
        ];
        $response =  $this->client->patch($url.$path, $body);

        return [
            'success' => $response->getStatusCode() === 204,
            'data'    => json_decode($response->getBody(), true),
        ];
    }
    
    public function get($id)
    {
        $path = 'meetings/'.$id;
        $url = $this->retrieveZoomUrl();
        $this->jwt = $this->generateZoomToken();
        $body = [
            'headers' => $this->headers,
            'body'    => json_encode([]),
        ];

        $response =  $this->client->get($url.$path, $body);

        return [
            'success' => $response->getStatusCode() === 204,
            'data'    => json_decode($response->getBody(), true),
        ];
    }

    /**
     * @param string $id
     * 
     * @return bool[]
     */
    public function delete($id)
    {
        $path = 'meetings/'.$id;
        $url = $this->retrieveZoomUrl();
        $body = [
            'headers' => $this->headers,
            'body'    => json_encode([]),
        ];

        $response =  $this->client->delete($url.$path, $body);
        
        return [
            'success' => $response->getStatusCode() === 204,
        ];
    }
}

const MEETING_TYPE_INSTANT = 1;
const MEETING_TYPE_SCHEDULE = 2;
const MEETING_TYPE_RECURRING = 3;
const MEETING_TYPE_FIXED_RECURRING_FIXED = 8;

<?php

namespace App\Http\Controllers;

use App\Models\ZoomMeeting;
use App\Traits\ZoomMeetingTrait;
use Illuminate\Http\Request;

class MeetingController extends AppBaseController
{
    use ZoomMeetingTrait;

    const MEETING_TYPE_INSTANT = 1;
    const MEETING_TYPE_SCHEDULE = 2;
    const MEETING_TYPE_RECURRING = 3;
    const MEETING_TYPE_FIXED_RECURRING_FIXED = 8;

    public function show($id)
    {
        $meeting = $this->get($id);

        return view('meetings.index', compact('meeting'));
    }

    public function store(Request $request)
    {
        $this->create($request->all());

        return redirect()->route('meetings.index');
    }

    public function update($meeting, Request $request)
    {
        $this->update($meeting->zoom_meeting_id, $request->all());

        return redirect()->route('meetings.index');
    }

    public function destroy(ZoomMeeting $meeting)
    {
        $this->delete($meeting->id);

        return $this->sendSuccess('Meeting deleted successfully.');
    }
}

Introduction

1. Improve your website

• Explain who you are and what you sell
• Entice a potential customer to buy
• Make it easy to buy a product or service
• There is a way to easily contact sales or customer support with questions

2. Invest in your business

3. Increase your advertising

4. Raising prices

• How much does it cost you to make a product
• How much does it cost to deliver
• Costs for running a business - including administration and employee salaries
• Competitive price
• The last time you raised a price

5. Follow the 80/20 rule

6. Cut costs

• Are there areas where you can improve efficiency?
• Negotiate cheap products or services?
• Will adopting new software or renting a service save you money in the long run?

Search Keys :

• Shift+Shift — Search Every Where
• Ctrl+F — Find Text within a Single File
• Ctrl+Shift+F-Find Text in All Files
• Ctrl+R — Replace Selected Text in a Single File
• Ctrl+Shift+R — Replace Selected Text in all Files (Be Careful while Using This)
• Ctrl+Shift+A —Search for IDE Commands

• Ctrl+N — Navigate to Class
• Ctrl+Shift+N — Navigate to a File
• Ctrl+B — Jump to Declarations
• Alt+ ↑ — Jump to the Previous Method
• Alt+↓ — Jump to Next Method
• Ctrl+G — Jump to Line
• Ctrl+E — Recent Files
• Ctrl+Shift+Back Space — Jump to Last Edited Location
• Ctrl+B — Find Declarations
• Ctrl+Left Mouse(or)Ctrl+Alt+F7— Show Usage
• Alt + F7 / Ctrl + F7 — Find usages /Find usages in file
• Ctrl+Shift+B — Find Implementations
• F3 — Find Next
• Shift+F3 — Find Previous

• F11 — Toggle bookmark
• Ctrl+F11 — Toggle bookmark with the mnemonic(0–9 or A-Z)
• Ctrl +(0–9) — Go to numbered bookmark
• Shift+F11 — Show all Bookmarks
• Ctrl + Shift + F7 — Highlight usages in file

• Ctrl + W — Extend selection (selects a word->line->method->Class )
• Ctrl +Shift+ W — Decrease Selection
• Alt + J — Select next occurrence
• Ctrl + Alt + Shift + J — Select all occurrences
• Alt + Shift + J — Unselect occurrence
• Ctrl+Shift+V — Paste from recent buffers (from a History of Copied Contents)

• Ctrl+F6  — Refractor Code
• Ctrl+D — Duplicate a Line/Selected part
• Ctrl+Y — Delete a Line/Selected part
• Ctrl+Q — Quick Documentation
• Ctrl + Space — Code completion
• Ctrl+Shift+Space — Smart code completion (by expected type removes unrelated suggestions)
• Alt+Insert — Generate Code
• Ctrl+J — Insert Live template
• Ctrl + O — Override methods
• Ctrl + I — Implement methods
• Ctrl + Alt + T — Surround with…
• Ctrl + / — Comment / uncomment with line comment
• Ctrl + Shift + / — Comment / uncomment with block comment
• Ctrl+Alt+L — Reformat code

• Ctrl + F9 — Compile and Run Make a project
• Ctrl + Shift + F9 — Compile selected file, package or module
• Shift + F10 — Run
• Shift + F9 — Debug
• Ctrl + Shift + F10 — Run context configuration from editor

• F8 / F7 — Step over / into
• Shift + F7 / Shift + F8 — Smart step into/Step out
• Alt + F9 — Run to cursor
• Alt + F8 — Evaluate expression
• F9 — Resume program
• Ctrl + F8 — Toggle break point
• Ctrl + Shift + F8 — View breakpoints