Thinkkun

[Thinkkun @think_kun]

Day 13/60: GORM basics. The useful shift was keeping gorm basics 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, connection usage, and

[Thinkkun @think_kun]

Day 13/60: Set operations. The useful shift was using JavaScript maps, objects, and sets deliberately instead of treating them like magic storage. I wanted the rule clear: make the key and the stored meaning explicit before the map or object starts growing, then update the hash

[Thinkkun @think_kun]

Day 13/60: HashSet patterns. The useful shift was using Rust hash-based collections deliberately instead of treating them like magic storage. I wanted the rule clear: make the key and the stored meaning explicit before the map starts growing, then update the hash state in the

[Thinkkun @think_kun]

Day 13/75: Map patterns in Go. The useful shift was using a stable invariant so map patterns in go feels like a process instead of a trick. I wanted the rule clear: name the exact window, prefix, or pointer region each variable owns, then reuse prior work instead of recomputing

[Thinkkun @think_kun]

Day 13/75: Unordered map patterns. The useful shift was using unordered_map and unordered_set deliberately instead of treating them like magic storage. I wanted the rule clear: make the key and the stored meaning explicit before the unordered_map or unordered_set starts growing,

[Thinkkun @think_kun]

Day 13/75: HashMap patterns in Java. The useful shift was using a stable invariant so hashmap patterns in java feels like a process instead of a trick. I wanted the rule clear: name the exact window, prefix, or pointer region each variable owns, then reuse prior work instead of

[Thinkkun @think_kun]

Day 13/75: Hash map patterns in Python. The useful shift was using Python dicts and sets deliberately instead of treating them like magic storage. I wanted the rule clear: make the key and the stored meaning explicit before the dict or set starts growing, then update the hash

[Thinkkun @think_kun]

Day 13/365: Dutch National Flag. The useful shift today was seeing the array as three regions, not random swaps. `low`, `mid`, and `high` each protect an invariant, and `mid` only advances when the current value is resolved. That made partitioning much cleaner. #DSA #Arrays

[Thinkkun @think_kun]

Day 13/60: Deployed Zipkin with Elasticsearch storage for distributed tracing across our 20+ microservices.

B3 headers propagate trace context. Brave auto-instruments Spring Boot. Set sampling to 0.1 in prod or your collector drowns.

#SRE #DistributedTracing #Zipkin

[Thinkkun @think_kun]

Terraform workspaces 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

[Thinkkun @think_kun]

AWS KMS key policies override IAM policies. If the key policy doesn't grant access, no IAM policy can fix it. Miss the root account statement and you'll call AWS Support to unlock your own key. #CloudSecurity #AWS #KMS #Security #SysAdmin #Linux #DevSecOps #CyberSecurity #InfoSec

[Thinkkun @think_kun]

Cron jobs and scheduling in Bash security is about proving which scheduled jobs really run, who owns them, and what command they launch. Read the real Linux artifact, keep the shell strict, and leave enough evidence behind that another engineer can trust the output. /etc/cron.*

[Thinkkun @think_kun]

Day 13/90: Secure REST API consumption in Python

Built a credential-rotating client, paginated threat feed puller, and rate-limit backoff handler. Getting blocked mid-incident because you ignored Retry-After headers is a career lesson you only need once.

#Python #InfoSec

[Thinkkun @think_kun]

Key protocols: DNS: tie dns hierarchy 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

[Thinkkun @think_kun]

Day 13/90: Enums & constants. Today's hinge point was clear value shapes 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.

[Thinkkun @think_kun]

Day 13/90: Interfaces fundamentals. Useful shift: making interfaces fundamentals 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.

[Thinkkun @think_kun]

Day 13/90: Properties and indexers. Today's hinge point was constructors that lock in valid state 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.

[Thinkkun @think_kun]

Day 13/90: Input/Output basics. 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.

[Thinkkun @think_kun]

Day 13/90: Generics fundamentals. The useful part was keeping shared boundaries stable while the app evolves. Main check: type the seam, not every detail. That made the next change easier to reason about. #TypeScript #SoftwareEngineering It made the next refactor calmer.

[Thinkkun @think_kun]

Day 13/90: Closures and scope. Today's hinge point was who owns state and lookup behavior so the JavaScript code still reads like a contract when the endpoint or workflow grows. #JavaScript #WebDev The debugging path got shorter. The design felt easier to review. Clearer now.