Return to DSA: a practical story

A Principal Engineer at Atlassian posted a short, practical thread about how they returned to daily data‑structures-and‑algorithms (DSA) practice after years away. (x.com 1) (x.com 2) They described a disciplined routine: small, daily problems, deliberate review of patterns, and steady repetition until solutions felt familiar rather than mysterious. (x.com 1) (x.com 2) The mechanic behind that routine is pattern recognition. When you solve dozens of sliding‑window or graph‑traversal problems, you stop inventing fresh approaches each time and instead map a new prompt to a known pattern and its implementation details. Mapping problems to patterns shortens the path from prompt to code. It replaces long, uncertain search with a handful of reliable moves: choose the structure, pick the traversal or recurrence, and optimize by pruning or memoizing. That is the practical point the thread made: small daily inputs accumulate into intuition. (x.com) (x.com) This matters for students aiming at Big Tech because interviews reward quick, correct pattern application as much as raw inventiveness. Companies like Atlassian, and many peers in the industry, still use algorithmic rounds to measure those skills. (glassdoor.com) If you want to make the thread operational, use three concrete tools the engineer’s routine implies. First, pick a daily problem source that organizes by topic so you can cycle through patterns—LeetCode is the obvious hub for that. (leetcode.com) Second, follow a curated sheet of high‑value problems to ensure coverage of the common patterns employers expect; Striver’s SDE Sheet is a compact roadmap many candidates use. (takeuforward.org) Third, record your work publicly so repetition grows into evidence: a GitHub repo with one solved problem per day makes your progress visible and gives you a place to revisit old solutions. Public daily‑DSA repos show how small, steady commits add up. (github.com) (dsadaily.com) Turn the engineer’s advice into a minimal, repeatable schedule: 30–60 minutes a day; start with one easy problem to warm up, then one medium that forces pattern selection, then 10 minutes reviewing the optimum approach and writing a clean README explaining the pattern. When interview season arrives, this steady practice does two things at once: it hardens recall for live coding and it builds a record you can point to in interviews and on your resume. Begin today by opening one problem on LeetCode in the pattern area you feel weakest in, solve it, push a clean solution to a GitHub repo, and add a one‑line note saying which pattern you practiced. (leetcode.com) (github.com)