Julian Wiley

Technical Deep-Dive: [Topic Name]

February 14, 2026· 2 min readTechnical

A detailed technical walkthrough of [topic]. Replace this with your actual description.

Machine LearningPython
<!-- ============================================================ TEMPLATE: Technical Deep-Dive Post This is a starter template for technical blog posts. Duplicate this folder, rename it, and customize the content below. Remove `draft: true` from the frontmatter when ready to publish. ============================================================ -->

Problem Statement

<!-- Describe the problem you're solving. What motivated this work? Why does it matter? -->

In this post, I'll walk through [brief description of what you'll cover]. This is relevant because [explain why readers should care].

Background

<!-- Provide context the reader needs. Link to papers, docs, or prior posts if applicable. -->

Before diving in, here's a quick overview of the key concepts:

  • Concept A -- Brief explanation
  • Concept B -- Brief explanation

Approach

<!-- Describe your methodology. What tools, libraries, and techniques did you use? -->

Tools and Libraries

<!-- Use the tech-stack shortcode to display your stack -->

WARNING: Unported Hugo shortcode (manual conversion needed)

"} />

WARNING: Unported Hugo shortcode (manual conversion needed): {{< /tech-stack >}}

Methodology

<!-- Walk through your approach step by step. Include code samples. -->

The first step was data preprocessing:

import pandas as pd
import numpy as np

# Load and clean the dataset
df = pd.read_csv("data/raw_data.csv")
df = df.dropna(subset=["target"])
df["date"] = pd.to_datetime(df["date"])

Next, feature engineering:

# Create lagged features
for lag in [1, 5, 10, 20]:
    df[f"return_lag_{lag}"] = df["returns"].shift(lag)

Results

<!-- Present your findings with code, tables, or visualizations. -->
MetricBaselineOur Model
Accuracy0.520.73
Precision0.480.71
Recall0.500.68

Key Takeaways

<!-- Summarize the most important findings. -->
  1. Finding 1 -- Explanation
  2. Finding 2 -- Explanation
  3. Finding 3 -- Explanation

What's Next

<!-- Describe future work or related topics you plan to explore. -->

In a follow-up post, I'll explore [next topic]. If you have questions or suggestions, leave a comment below.

References

<!-- Link to papers, documentation, or related resources. -->

Related Posts

Traffic Tokenization for Security ML
May 10, 2026
How cybersec_dashboard tokenizes packet data into model-ready representations and why this design matters for transformer-based traffic analysis.
Collector Layer Design in CyberSec Dashboard
May 8, 2026
A practical look at how network, memory, logs, registry, and process collectors are structured and coordinated in cybersec_dashboard.
Inside the Planner-Worker Engine of CyberSec Dashboard
May 7, 2026
How the core planner-worker-pipeline architecture in cybersec_dashboard enables async security analysis across diverse telemetry streams.
Removing Langflow from Extras: A Dependency Conflict Postmortem
Apr 16, 2026
What we learned from removing Langflow from optional extras due to cachetools conflicts with MLflow and how to handle similar packaging tradeoffs.