Thinkkun

Day 11/60: PostgreSQL with Go. The useful shift was keeping postgresql with go honest about query boundaries, transactions, and data ownership. I wanted the rule clear: decide where transactions begin and end before mixing reads and writes together, then make query shape,

Day 11/60: String problems. The useful shift was making string problems work with JavaScript strings, indexing, and character handling without losing correctness. I wanted the rule clear: decide early whether indexing, slices, or character arrays are the right representation in

Day 11/60: String problems in Rust. The useful shift was making string problems in rust work with Rust slices, strings, and indices without losing correctness. I wanted the rule clear: decide early whether bytes, chars, or slices are the right representation in Rust, then keep

Day 11/75: String operations in Go. The useful shift was making string operations in go work with Go strings, bytes, and runes without losing correctness. I wanted the rule clear: decide early whether bytes, runes, or direct iteration is the right representation in Go, then keep

Day 11/75: String operations in C++. The useful shift was making string operations in c++ work with C++ strings, char access, and iterators without losing correctness. I wanted the rule clear: decide early whether string indexing, iterators, or views are the right representation

Day 11/75: String operations in Java. The useful shift was making string operations in java work with Java strings, char arrays, and indexing without losing correctness. I wanted the rule clear: decide early whether String, char array, or StringBuilder is the right representation

Day 11/75: String operations in Python. The useful shift was making string operations in python work with Python strings, slicing, and character handling without losing correctness. I wanted the rule clear: decide early whether indexing, slicing, or direct iteration is the right

Day 11/365: Prefix sums. The useful shift today was seeing precomputation pay off fast. One linear pass to store running totals turned repeated range checks, subarray-sum questions, and equilibrium-index reasoning into cleaner operations with less rescanning. #DSA #Arrays

Day 11/60: Log aggregation with Loki Loki indexes labels, not log content. That single design choice cuts storage costs 10-20x vs Elasticsearch. Key lesson: never promote high-cardinality fields to Loki labels. Query them with LogQL filters instead. #SRE #Observability

Writing custom modules is really about keeping Terraform honest when the state file, provider behavior, and module boundaries are all capable of hiding drift. I want the review to show where Terraform, Ansible, policy, or pipeline evidence lives in terraform plan output, remote

SQL injection still tops OWASP for a reason. The core trick: ' closes the string, -- comments out the rest. One quote turns your input from data into code. Test: ORDER BY 1,2,3... to find column count, then UNION SELECT to extract. #SQLi #Pentesting #Websec #Security #SysAdmin

Day 11/60: AWS Security Hub needs AWS Config running first or half your compliance controls silently fail. Enable cross-region aggregation or you only see findings from one region. #CloudSecurity #AWS #60DayChallenge #Security #SysAdmin #Linux #DevSecOps #CyberSecurity #InfoSec

Advanced text processing in Bash security is about turning noisy Linux text into security evidence you can defend later. Read the real Linux artifact, keep the shell strict, and leave enough evidence behind that another engineer can trust the output. grep, sed, awk, and files

Day 11/90: Web Scraping for OSINT Built a BeautifulSoup email harvester that strips script/style tags before regex extraction. Eliminates false positives from JS variables. Also parsed robots.txt to surface hidden admin paths orgs forgot they exposed. #OSINT #Python #InfoSec

IP Addressing: tie ipv4 to one real artifact and one real next step. That is how a security lesson becomes usable during triage, hardening, design review, or response. Evidence should beat confidence every time. #Cybersecurity #Infosec #Securityops #Dfir Good security notes make

Day 11/90: References. Today's hinge point was who owns the object so the C++ code still reads like a contract when the program or workflow grows. #Cpp #CPlusPlus The debugging path got shorter. The design felt easier to review. It finally stopped feeling like boilerplate.

Day 11/90: Result type and error handling. Today's hinge point was domain boundaries so the Rust code still reads like a contract when the endpoint or workflow grows. #Rust #RustLang The debugging path got shorter. The design felt easier to review. Useful in review.

Day 11/90: Methods and receivers. Useful shift: making methods and receivers feel like concrete data modeling and. Main check: make values, structs, and interfaces say one clear thing about. #GoLang #LearnGo It made the topic easier to explain. The debugging lens got cleaner.

Day 11/90: Enums and nullable types. Today's hinge point was clear value shapes so the C# code still reads like a contract when the endpoint or workflow grows. #CSharp #DotNet The debugging path got shorter. The design felt easier to review. Useful in review. Clearer now.

Day 11/90: Enums & constants. Today's hinge point was clear value shapes so the Java code still reads like a contract when the endpoint or workflow grows. #Java #JVM The debugging path got shorter. The design felt easier to review. It finally stopped feeling like boilerplate.