Video Link: Apache Kafka Crash Course | What is Kafka?
- Knowledge
- Node.JS Intermediate level
- Experience with designing distributed systems
- Tools
- Node.js: Download Node.JS
- Docker: Download Docker
- VsCode: Download VSCode
| REM Delete eval folder with licence key and options.xml which contains a reference to it | |
| for %%I in ("WebStorm", "IntelliJ", "CLion", "Rider", "GoLand", "PhpStorm", "Resharper", "PyCharm") do ( | |
| for /d %%a in ("%USERPROFILE%\.%%I*") do ( | |
| rd /s /q "%%a/config/eval" | |
| del /q "%%a\config\options\other.xml" | |
| ) | |
| ) | |
| REM Delete registry key and jetbrains folder (not sure if needet but however) | |
| rmdir /s /q "%APPDATA%\JetBrains" |
| # Simple Snake Game in Python 3 for Beginners | |
| # By @TokyoEdTech | |
| import turtle | |
| import time | |
| import random | |
| delay = 0.1 | |
| # Score |
Video Link: Apache Kafka Crash Course | What is Kafka?
| # Stage 1: Build | |
| FROM php:8.4-cli AS build | |
| # Setup build root | |
| WORKDIR /app | |
| # Install dependencies | |
| RUN apt-get update && apt-get install -y \ | |
| git \ | |
| unzip \ |
Resume claude after running out of usage limit. For Macos, it uses the automation scripts to resume usage.
For instance if your usage resets at 3pm
./resume_claude.sh "15:00"
A high-level approach to multiplexing multiple TCP connections over a single socket. Probably ignores a lot of queueing theory.
The CC3000 WiFi chip may be especially unreliable if more than one socket is in use. So the idea is to maintain a single connection with a proxy server, which will handle the actual simultaneous outbound connections on a client's behalf. (Inbound connections are lower implementation priority.)
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.
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.
Have you ever tried to merge two branches only to end up in conflict hell? You fix a bunch of conflicts only to run git merge --continue and be presented with the same conflicts. Repeat this process and after a few iterations you give up because it just isn't worth the pain and effort.
Would you be surprised to know that there is a git feature specifically for this problem? It's called rerere and I'm going to enrich your life with it now. (I'm going to talk specifically about merging but I think it also helps rebasing)
rerere stands for Reuse Recorded Resolution. The TL;DR version is you ask git to remember how you've resolved hunks in the past, and if the same one comes up for a file in future just redo what you did last time.
To enable this feature just run this lovely command git config --global rerere.enabled true. You can also turn it on by creating this directory in your projects .git/rr-cache, although the global setting is much clearer.
I'll try to take you through an example of how th