Puzzle Thinking

Assumption made:

You work for 24 hours on the weekend

How much do you earn for the entire weekend?

Babysit the entire weekend

Saturday:24 hours

Sunday:24 hours

Total hours = 48 hours

If 1 hour = 12 GHS
48 hours

48hours*12 GHS/1 HOUR= 576 GHS

How much do you pay your brother and his wife?

Brother: 10*576/100=57.60 GHS

How much do you keep?

Total earning - Paid to your brother

576GHS - 57.60 GHS=518.40GHS

As of 2021, YouTube has over 2 billion logged-in monthly users. On average, users spend over 1 billion hours watching YouTube videos.

Procedures;

Divide the total number of hours watched by the average length of a YouTube video.

Assuming An average video length of 10 minutes(600 seconds), the calculations would be;

Total hours watched per day = 1 billion users

Average video length = 600 seconds

Total videos watched per day = (1 billion hours x 3600 seconds)/600 seconds.

Considering the 2020 statistics, where Google Store generated approximately $38.6 billion in gross revenue.

This includes in-app purchases, app purchases, and subscriptions.

This figure represents gross revenue; the net revenue would be lower after deducting the 30%
commission Google takes from app developers.

Driverless cars, also known as Autonomous cars or self-driving cars, are vehicles that consist of sensors to sense the environment and software to control and navigate it and perceive their surrounding. It can operate without human involvement.
The market size of driverless cars by 2028 is estimated to be substantial based on different factors such as advancements, regulatory changes, and consumer consumption.
According to various industrial reports and market research, the global market size for autonomous cars is expected to range from $60 billion to $250 billion by 2028, considering the market size of 2022, which was $21.98 billion.

To go about this, we would do the following;

Ask the supervisor or other team members to provide initial information about the technology, its applications, and how it will be used in the project.
Search for online tutorials, documentation, blogs, or community forums related to the technology to understand its functionality, limitations, and best practices.
We would first understand how this technology will benefit the project and what challenges might arise from using it.
Identify colleagues in the company who have experience with the technology, either internally or through established partnerships, to ask for their insights and guidance.
Begin with small, manageable tasks using the technology to gain hands-on experience and build confidence.
Embrace continuous learning from mistakes and experimentation to improve skills and understanding of the technology.
We will keep the supervisor informed about any progress and share learnings and insights with the team to promote a collaborative environment where everyone can benefit from our expertise.
Lastly, connect with other professionals who are working with the technology to learn from their experience and gain insights.

Quickly and accurately determining the nature of the issue. Is it a simple bug, a larger system problem, or a complete system failure?
Communicating the issue to the team, stakeholders, and the audience causes transparency to be key.
If the problem is a simple one, we immediately work on solving the issue, and if not, we decide to either delay the launch or launch with partial functionalities.
After a potential fix, we carefully monitor the product and use the experience to ensure that the issue has been resolved and there are no further problems.
After the conference, we review the situation to identify the root cause of the failure and implement changes to prevent similar issues in the future.