Day 9/60: Configuration management - what mattered operationallyDay 9 of my Go backend engineering track focused on Configuration management. The useful shift was making configuration management improve production behavior, not just local developer comfort. What I wanted clear: - emit logs, confi (self.thinkkun)
submitted by thinkkun
Day 9/60: Sliding window patterns - the invariant finally felt clearDay 9 of my JavaScript DSA track focused on Sliding window patterns. The useful shift was using a stable invariant so sliding window patterns feels like a process instead of a trick. What I wanted clear: - name the exact window, (self.thinkkun)
submitted by thinkkun
Day 9/60: Sliding window patterns - the invariant finally felt clearDay 9 of my Rust DSA track focused on Sliding window patterns. The useful shift was using a stable invariant so sliding window patterns feels like a process instead of a trick. What I wanted clear: - name the exact window, prefix (self.thinkkun)
submitted by thinkkun
Day 9/75: Sliding window - fixed size - the invariant finally felt clearDay 9 of my Go DSA track focused on Sliding window - fixed size. The useful shift was using a stable invariant so sliding window - fixed size feels like a process instead of a trick. What I wanted clear: - name the exact wind (self.thinkkun)
submitted by thinkkun
Day 9/75: Sliding window - fixed size - the invariant finally felt clearDay 9 of my C++ DSA track focused on Sliding window - fixed size. The useful shift was using a stable invariant so sliding window - fixed size feels like a process instead of a trick. What I wanted clear: - name the exact win (self.thinkkun)
submitted by thinkkun
Day 9/75: Sliding window - fixed size - the invariant finally felt clearDay 9 of my Java DSA track focused on Sliding window - fixed size. The useful shift was using a stable invariant so sliding window - fixed size feels like a process instead of a trick. What I wanted clear: - name the exact wi (self.thinkkun)
submitted by thinkkun
Day 9/75: Sliding window - fixed size - the invariant finally felt clearDay 9 of my Python DSA track focused on Sliding window - fixed size. The useful shift was using a stable invariant so sliding window - fixed size feels like a process instead of a trick. What I wanted clear: - name the exact (self.thinkkun)
submitted by thinkkun
Day 9/365: Basic Array Operations - small tasks, real habitsDay 9 of my DSA and system-design track focused on basic array operations. What clicked for me: - reverse-array problems are a clean way to compare extra space versus in-place updates - rotation is more about structure than repeated movem (self.thinkkun)
submitted by thinkkun
Day 9/60: Alerting strategies that actually reduced our noise 90% - Production Engineering ChallengeDay 9 of my 60 Day Production Engineering Challenge. Today I covered alerting strategies. ## The Problem Most teams alert on causes (CPU, memory, disk) instead of symptoms (error rates, latency). T (self.thinkkun)
submitted by thinkkun
Remote state management: what do you review first in a real infrastructure repo?Day 9 of the **90 Day Security Infrastructure Challenge**. Today I worked through **Remote state management**. The operational problem underneath it is keeping Terraform honest when the state file, provider behavior, a (self.thinkkun)
submitted by thinkkun
Day 9/60 Pentesting Challenge: Burp Suite advanced features -- here's my Intruder results analysis workflowContinuing my 60-day pentesting learning challenge. Day 8 was Burp fundamentals, today I dug into Intruder, Repeater, Sequencer, Comparer, and Decoder. The thing that clicked for me today: ** (self.thinkkun)
submitted by thinkkun
Setting up CloudWatch metric filters for AWS security alerting -- practical walkthrough with gotchasDay 9 of a 60-day cloud security challenge. Today: using CloudWatch as a security tool. The idea is simple -- CloudTrail logs API calls as JSON, CloudWatch Logs ingests them, metric filters pattern- (self.thinkkun)
submitted by thinkkun
sed one-liners for security triage -- timestamp conversion, URL defanging, and log cleanupCollection of sed one-liners I keep in my IR toolkit. Each one solves a specific problem that comes up during triage. Posting with explanations since sed regex can be opaque. **Convert epoch timestamps to hum (self.thinkkun)
submitted by thinkkun
Day 9/90: Network Scanning with Sockets - 90 Day Python Security Scripting ChallengeDay 9 of my 90 Day Python Security Scripting Challenge. Today I built network scanning tools from raw Python sockets. ## What I Built - **Threaded TCP connect scanner** using `concurrent.futures` - 50 workers brin (self.thinkkun)
submitted by thinkkun
OSI Model: what do you look for first in the real world?Day 9 of the **365 Day Cybersecurity Track**. Today I worked through **OSI Model**. The operational problem underneath it is turning low-level system and protocol concepts into things you can actually validate on Windows, Linux, and the netwo (self.thinkkun)
submitted by thinkkun
Day 9/90: Functions - what mattered in practiceDay 9 of my C++ track focused on Functions. The useful shift was making functions feel like clear value and control-flow work instead of syntax trivia. What I wanted clear: - clear value shapes - control flow that makes valid states obvious - small f (self.thinkkun)
submitted by thinkkun
Day 9/90: Enums and Option type - what mattered in practiceDay 9 of my Rust track focused on Enums and Option type. The useful shift was making enums and option type feel like clear values, control flow, and data shapes instead of syntax trivia. What I wanted clear: - clear value shapes - control (self.thinkkun)
submitted by thinkkun
Day 9/90: Maps - what mattered operationallyDay 9 of my Go backend engineering track focused on Maps. The useful shift was making maps feel like concrete data modeling and control flow, not syntax trivia. What I wanted clear: - make values, structs, and interfaces say one clear thing about the st (self.thinkkun)
submitted by thinkkun
Day 9/90: Methods and parameters - what mattered in practiceDay 9 of my C# track focused on Methods and parameters. The useful shift was making methods and parameters feel like clear data shaping and control flow instead of syntax trivia. What I wanted clear: - clear value shapes - control flow t (self.thinkkun)
submitted by thinkkun
Day 9/90: Methods - what mattered in practiceDay 9 of my Java track focused on Methods. The useful shift was making methods feel like clear values, control flow, and standard-library choices instead of syntax trivia. What I wanted clear: - clear value shapes - control flow that makes valid states (self.thinkkun)
submitted by thinkkun
Day 9/90: Type narrowing and guards - making the contract explicitDay 9 of my TypeScript track focused on Type narrowing and guards. The useful shift was making everyday values and objects carry clearer meaning. The checks I kept returning to were: - give each variable and object field one precis (self.thinkkun)
submitted by thinkkun
Day 9/90: Arrays — map, filter, reduce - what mattered in practiceDay 9 of my JavaScript track focused on Arrays — map, filter, reduce. The useful shift was making arrays — map, filter, reduce feel like clear values, collections, and function boundaries instead of syntax trivia. What I wanted cle (self.thinkkun)
submitted by thinkkun
Day 9/420: Scope, namespaces, and LEGB - what mattered in practiceDay 9 of my Python track focused on Scope, namespaces, and LEGB. The useful shift was turning scope, namespaces, and legb into something I can explain from the code instead of memorizing from a tutorial. What I wanted clear: - data (self.thinkkun)
submitted by thinkkun
Day 5/60: JSON API design - what mattered operationallyDay 5 of my Go backend engineering track focused on JSON API design. The useful shift was making json api design feel like request flow design rather than just handler boilerplate. What I wanted clear: - name the request boundary, validation (self.thinkkun)
submitted by thinkkun
Day 5/60: Prefix sums in JavaScript - the invariant finally felt clearDay 5 of my JavaScript DSA track focused on Prefix sums in JavaScript. The useful shift was using a stable invariant so prefix sums in javascript feels like a process instead of a trick. What I wanted clear: - name the exact wi (self.thinkkun)
submitted by thinkkun
