Skip to content

Instantly share code, notes, and snippets.

View jcoding09's full-sized avatar
🌴
I may be slow to respond.

jcoding09

🌴
I may be slow to respond.
View GitHub Profile
@jcoding09
jcoding09 / kill_vlc.sh
Created September 20, 2026 15:45
Linux Mint scripts
#!/bin/bash
pkill -9 -x vlc

1. THE CORE THESIS

Infrastructure is currently at a critical inflection point, requiring a massive $106 trillion investment by 2040 to support global GDP growth and economic shifts. This expanding definition of infrastructure—moving beyond traditional roads and bridges to include digital assets, energy systems, and sustainable technology—necessitates a strategic transition toward increased private capital involvement alongside public sector efforts.

2. CRITICAL TAKEAWAYS & INSIGHTS

  • Broadening Definition of Infrastructure: The definition has expanded to include aerospace, defense, and agriculture, as these sectors now possess "infrastructure-like" characteristics essential for the global economy (1:40).
  • The $106 Trillion Requirement: Investment needs have doubled compared to the last 15 years, with the majority of growth concentrated in Asia and driven by the need for both modernization in developed economies and basic development in emerging markets (3:14).
  • **The Rise of Priva
@jcoding09
jcoding09 / how-to-learn-coding-with-ai.md
Created August 12, 2026 17:50
Learn how to use AI as a coding tutor while developing the skills to understand, debug, and maintain software yourself.

Learning to Code in the Age of AI

Artificial intelligence has transformed the way developers write software. Tasks that once took hours can now be completed in minutes with the help of AI tools. While this shift brings incredible opportunities, it also introduces a new challenge: learning how to use AI without becoming dependent on it.

The Illusion of Progress

One of the biggest traps for new programmers is relying on AI to generate entire projects from scratch. It can feel productive to watch a chatbot produce hundreds of lines of code, but that feeling can be misleading.

The real test comes when something breaks. If you don't understand how the code works, debugging becomes frustrating and nearly impossible. You may have a functioning application, but without understanding the underlying logic, you're left maintaining software you didn't truly build.

Competitive programming requires a mix of theoretical math proofs and highly optimized implementation tricks, a single platform or book rarely covers everything perfectly.

To master the topics outlined in the roadmap (cp_dsa_roadmap.pdf) and the master syllabus (complete_cp_master_syllabus.pdf), you should use a targeted mix of the following world-class sources depending on what type of topic you are studying:


1. For Advanced Data Structures & Offline Techniques (e.g., CDQ, Segment Tree Beats, Mo's)

  • CP-Algorithms (cp-algorithms.com): This is the definitive holy grail for competitive programming. It explains highly complex topics with exact mathematical breakdowns and optimized C++ code implementations. It is ideal for mastering range query modifications and dimensional reductions like CDQ Divide and Conquer.

The Three Mental Traps:

  1. "I'll start when I feel ready" (0:10-0:37): The speaker explains that waiting for a feeling of readiness is a mistake because readiness is not a feeling—it is a result of action. Starting creates the necessary momentum and confidence.

  2. "I need more clarity before I start" (0:38-1:03): This trap often masks itself as being strategic or organized. The speaker notes that true clarity comes from testing and taking action (getting "reps" in) rather than just thinking or planning, which can become a form of stalling.

  3. "I'll be consistent when life calms down" (1:04-1:30): Life rarely stops being chaotic; instead, it simply changes forms. The speaker emphasizes the importance of building structure and consistency within the chaos rather than waiting for a perfect, quiet moment that never arrives.

Provide a highly detailed breakdown using this exact structure:

  1. THE CORE THESIS: In 2-3 sentences, what is the main purpose or argument of this video?
  2. CRITICAL TAKEAWAYS & INSIGHTS: What are the top 5-7 most important concepts, frameworks, or insights shared? Explain the "why" behind each one.
  3. ACTIONABLE STEPS: Create a step-by-step checklist of things the viewer can actually implement or apply based on this video.
  4. CASE STUDIES & EXAMPLES: Detail any real-world stories, data, or examples the speaker used to prove their points.
  5. COUNTER-INTUITIVE IDEAS: Did the speaker mention anything that goes against common belief or wisdom?
  6. KEY QUOTES: Extract 3 of the most powerful or memorable quotes from the transcript with their context.

Do not summarize. Extract the deep knowledge so I don't miss anything important.

@jcoding09
jcoding09 / llm-wiki.md
Created April 4, 2026 17:52 — forked from karpathy/llm-wiki.md
llm-wiki

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

Location
https://jwl-7.github.io/leetcode-cheatsheet/#array-two-pointers-one-input
https://github.com/bhavul/System-Design-Cheatsheet
https://bhavul.github.io/System-Design-Cheatsheet/
https://github.com/avgspacelover/Reddit-wiki-programming
https://github.com/seanprashad/leetcode-patterns
https://seanprashad.com/leetcode-patterns/
https://github.com/jcoding09?tab=repositories
https://github.com/karanpratapsingh/system-design
@jcoding09
jcoding09 / amazon.md
Created March 29, 2025 13:58 — forked from terabyte/amazon.md
Amazon's Build System

Prologue

I wrote this answer on stackexchange, here: https://stackoverflow.com/posts/12597919/

It was wrongly deleted for containing "proprietary information" years later. I think that's bullshit so I am posting it here. Come at me.

The Question

Amazon is a SOA system with 100s of services (or so says Amazon Chief Technology Officer Werner Vogels). How do they handle build and release?