I have two Github accounts: oanhnn (personal) and superman (for work). I want to use both accounts on same computer (without typing password everytime, when doing git push or pull).
Use ssh keys and define host aliases in ssh config file (each alias for an account).
| // Predict is output with reasoning | |
| const xyzPromise = () => { | |
| return new Promise((resolve) => { | |
| resolve('A') | |
| }); | |
| }; | |
| console.log('B'); | |
| setTimeout(() => console.log('C'), 0); | |
| xyzPromise() |
| Given an m x n 2D binary grid grid which represents a map of '1's (land) and '0's (water), return the number of islands. | |
| An island is surrounded by water and is formed by connecting adjacent lands horizontally or vertically. You may assume all four edges of the grid are all surrounded by water. | |
| Example 1: | |
| Input: grid = [ | |
| ["1","1","1","1","0"], |
| FLATTEN FUNCTION | |
| // [1,2,3,[4,5, [6, 9]]] | |
| // [1,2,3,4,5, 6, 9] | |
| // [] | |
| // [] | |
| // [[], 1, [[]]] | |
| // [1] |
| /* Given an m x n 2D binary grid grid which represents a map of '1's (land) and '0's (water), return the number of islands. | |
| An island is surrounded by water and is formed by connecting adjacent lands horizontally or vertically. You may assume all four edges of the grid are all surrounded by water. | |
| Example 1: | |
| Input: grid = [ | |
| ["1","1","1","1","0"], |
| Hi Steve, | |
| I have encountered some challenges that I believe require re-evaluation of the current approach. Different tables have distinct requirements, which inherently limit the scope for code reuse. Ideally, updating data for these tables may warrant separate components or pages altogether. | |
| While the functionality for the courses table has been implemented as expected, extending the solution to other tables in a generic manner is proving to be infeasible. The variations in update requirements across tables cannot be effectively generalized. | |
| For instance, the employer table requires sectorIds during updates, which should not be mandatory but is enforced by the API. Such nuances introduce additional complexities, making it difficult to work with a one-size-fits-all approach. | |
| The basic UI for courses is functional, but the unique characteristics of each table highlight the inherent complexity. A more tailored solution may be necessary to address these challenges effectively. |
This project allows users to hover over a paragraph (<p>) element, where a play button appears. Upon clicking the button, the text is read aloud using the Web Speech API, and the words being spoken are highlighted in real-time.
Project: Hoory.com
As the Senior Full-Stack Engineer and Lead Developer on the Hoory project, I played a pivotal role in designing and implementing key features of the platform, which includes customer support tools such as live chat, chatbot builders, AI assistants, and omnichannel inboxes. My primary focus was on API integration and creation to ensure seamless interactions between the platform's backend and various customer touchpoints.
| // useDeepLinker.ts | |
| import { useCallback, useEffect, useRef } from "react"; | |
| export type DeepLinkOptions = { | |
| onIgnored?: () => void; | |
| onFallback?: () => void; | |
| onReturn?: () => void; | |
| /** | |
| * Time to wait before deciding the browser "ignored" the deep link. | |
| * Default: 500ms (same as original code) |
