What's Next?¶
Congratulations!
You've completed the Seeknal Quick Start.
You've learned the pipeline builder workflow and run your first pipeline. Now what?
Choose Your Learning Path¶
Seeknal supports three main personas. Choose the one that matches your role:
Data Engineer Path¶
Build production data pipelines at scale.
- Chapter 1: Build an ELT Pipeline — Ingest data from APIs, transform with DuckDB, output to warehouses
- Chapter 2: Add Incremental Models — Handle change data capture and schedule automated runs
- Chapter 3: Production Environments — Virtual environments, change categorization, and promotion
Time commitment: 3 chapters × 20-30 minutes
Perfect for: Data Engineers, ETL Developers, Pipeline Engineers
Analytics Engineer Path¶
Create semantic models and business metrics for self-serve analytics.
- Chapter 1: Define Semantic Models — Create entities, dimensions, and measures
- Chapter 2: Create Business Metrics — KPIs, ratios, cumulative metrics
- Chapter 3: Deploy for Self-Serve Analytics — StarRocks deployment and BI tool integration
Time commitment: 3 chapters × 20-30 minutes
Perfect for: Analytics Engineers, Data Analysts, BI Developers
Start Analytics Engineer Path →
ML Engineer Path¶
Build feature stores with point-in-time joins for ML applications.
- Chapter 1: Build Feature Store — Feature groups, point-in-time joins, training data
- Chapter 2: Second-Order Aggregation — Multi-level features and window functions
- Chapter 3: Training-to-Serving Parity — Online serving and model integration
Time commitment: 3 chapters × 20-30 minutes
Perfect for: ML Engineers, Data Scientists, MLOps Engineers
Not Sure Which Path?¶
Can't decide?
Here's a quick guide:
- Start with Data Engineer if you want to understand the fundamentals
- Choose Analytics Engineer if you care about business metrics and BI
- Choose ML Engineer if you're building ML models and need features
Pro tip
You can always come back and complete multiple paths! Each one reinforces the core concepts.
Explore Concepts¶
Want to understand how Seeknal works under the hood?
- Pipeline Builder Workflow — Deep dive on init → draft → apply → run
- YAML vs Python — When to use each approach
- Virtual Environments — Isolated development workflows
- Change Categorization — Understanding breaking vs non-breaking changes
- Glossary — All Seeknal terminology
Reference Material¶
Looking up specific commands or syntax?
- CLI Reference — All 40+ commands with examples
- YAML Schema Reference — Complete schema documentation
- Configuration Guide — Project settings and profiles
- Python API — Full API documentation
Community & Support¶
Join the Seeknal community:
- GitHub Discussions — Ask questions, share ideas
- Discord Server — Chat with other users
- GitHub Issues — Report bugs, request features
Track Your Progress¶
Want to keep track of what you've learned?
- Quick Start (completed!)
- Data Engineer Path
- Analytics Engineer Path
- ML Engineer Path
- Concepts review
- Building Blocks deep dive
Quick Reference¶
| Command | Purpose |
|---|---|
seeknal init <name> |
Create a new project |
seeknal draft <kind> |
Generate a template |
seeknal apply <file> |
Add to project |
seeknal run |
Execute pipeline |
seeknal status |
View applied resources |
seeknal --help |
All commands |
You're ready to continue your Seeknal journey! Choose your path above and let's build something great.