SShortSingh.
Back to feed

Developer shares 3-month FAANG interview prep method built on teaching back solutions

0
·2 views

A software developer writing on DEV Community describes a structured approach to preparing for FAANG coding interviews after struggling with rote memorization of LeetCode solutions. The core technique, called the 'teach-back method,' involves verbally explaining each solved problem step-by-step as if teaching a beginner, covering the problem statement, approach, edge cases, pseudocode, and a manual test. The author credits the method with shifting their preparation from copying solutions to genuinely understanding and rebuilding them under pressure. Inspiration came from watching a friend explain a dynamic programming problem by focusing on intuition and asking 'what if' variations rather than just presenting code. The article includes annotated Python code examples to illustrate how the method changes the depth of engagement with even a basic problem like Two Sum.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Developer shares how to build a privacy-first Astro site with strict security headers

A developer has published a detailed guide on building a secure, privacy-respecting website using the Astro framework, achieving a green rating on securityheaders.com by default. The approach centers on a strict Content-Security-Policy that blocks inline scripts, effectively neutralizing a broad class of cross-site scripting attacks. To eliminate third-party privacy leaks, the guide recommends self-hosting web fonts instead of loading them from Google's CDN, which exposes visitor IP addresses to an external server. Additional HTTP security headers — including HSTS, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy — are configured to close remaining attack vectors. Astro's build-time rendering and zero-JavaScript-by-default architecture are highlighted as key factors that make enforcing these strict policies practical for most sites.

0
ProgrammingDEV Community ·

JavaScript Variable Scope Explained: Global, Function, and Block Levels

In JavaScript, a variable's scope determines where it can be accessed within a program. Global variables are declared outside any function or block and are accessible throughout the entire codebase. Function-scoped variables exist only within the function they are declared in, while block-scoped variables using let or const are confined to the curly-brace block they appear in. The older var keyword is function-scoped and not block-scoped, unlike the modern let and const. JavaScript also supports hoisting for var and function declarations, but not for let and const.

0
ProgrammingDEV Community ·

Developer builds custom language compiler in Rust, shares progress on DEV Community

A developer has announced they are building a compiler in Rust for a custom programming language with a simple syntax. The language currently supports variable declarations for unsigned 64-bit integers and strings, along with basic print functions. The developer is actively working on the code generation phase but has hit a roadblock due to limited Assembly knowledge. They plan to learn Assembly to overcome this hurdle and expect to complete the project within a few days. The source code has been made publicly available in a repository for anyone interested in following the project.

0
ProgrammingDEV Community ·

GitHub Launches Private Security Advisories for Enterprise Internal Packages

GitHub made innersource security advisories generally available on July 8, giving enterprise teams a private channel to disclose vulnerabilities in internal packages without exposing them publicly. The feature, part of GitHub Advanced Security, lets enterprises publish advisories scoped exclusively to their own repositories via a new REST API. Once an advisory is filed, Dependabot automatically notifies affected internal repositories and opens pull requests to upgrade vulnerable dependencies where a fix exists. Previously, teams had no scalable way to handle internal CVEs, often resorting to Slack messages or spreadsheets that failed to reach all downstream consumers. The capability is limited to GitHub Advanced Security enterprise customers and depends on teams actively filing advisories to be effective.