ES version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
100% Positive
Analyzed from 233 words in the discussion.
Trending Topics
#training#job#inference#course#should#since#model#every#own#start

Discussion (4 Comments)Read Original on HackerNews
I'm working through it on my own but would love any advice or feedback.
Or if this is an oversight and you intend this actually be a course that starts from zero, you shouldn't start with an article that's starts off talking about training loss, test loss, and overfitting, without defining those terms.
I'm on a totally different path for learning inference engineering. I self-host a voice AI app that has ~2000 monthly active users on my own GPU box.
This forces me to learn about production serving, KV cache, quantization, inference engine, observability and economics, prefill optimization since I'm optimizing for TTFT instead of decode speed, and many more.
It's fun since every optimization you do directly translate to a better user experience or allow you to serve more users using the same hardware.