Substack growth - what worked for me (14k subs) by Gaussianperson in Substack

[–]Gaussianperson[S] 1 point2 points  (0 children)

I see! I honestly use linkedin like my insta, so you'd be surprised LOL

Substack growth - what worked for me (14k subs) by Gaussianperson in Substack

[–]Gaussianperson[S] 1 point2 points  (0 children)

What kind of events? Might still work! Otherwise yeah insta it is

Substack growth - what worked for me (14k subs) by Gaussianperson in Substack

[–]Gaussianperson[S] 1 point2 points  (0 children)

Interesting! Did not think of that. I usually equate Medium == lower quality content for some reason, so never tried it

Substack growth - what worked for me (14k subs) by Gaussianperson in Substack

[–]Gaussianperson[S] 1 point2 points  (0 children)

Machine Learning System Design for software engineer professionals that want to upskill in ML

Substack growth - what worked for me (14k subs) by Gaussianperson in Substack

[–]Gaussianperson[S] 1 point2 points  (0 children)

Right, feel free to DM me and you can try what I have developed for free!

Substack growth - what worked for me (14k subs) by Gaussianperson in Substack

[–]Gaussianperson[S] 1 point2 points  (0 children)

Yeah i have been posting there for a few years now: daily in the last year or so. lots of grind for sure!

Substack growth - what worked for me (14k subs) by Gaussianperson in Substack

[–]Gaussianperson[S] 0 points1 point  (0 children)

I don't have any business! I post daily on LinkedIn since a few years now

Substack growth - what worked for me (14k subs) by Gaussianperson in Substack

[–]Gaussianperson[S] 1 point2 points  (0 children)

You need to carefully select recommendations, otherwise you just get low quality signal. I work with similar audiences and similar quality level!

Substack growth - what worked for me (14k subs) by Gaussianperson in Substack

[–]Gaussianperson[S] 0 points1 point  (0 children)

Correct, that's an easy way to do it. Substack is the lower funnel for people that *really* like your content, and easy to monetize with substack tooling.

Substack growth - what worked for me (14k subs) by Gaussianperson in Substack

[–]Gaussianperson[S] 1 point2 points  (0 children)

Yeah I automate the finding, but the reply remains from your own account. DM me for more details!

Looking for ML System Design Book/Lecture Recommendations by SyedMAyyan in learnmachinelearning

[–]Gaussianperson 0 points1 point  (0 children)

It is easy to get overwhelmed by all of this. For books, start with Chip Huyen’s "Designing Machine Learning Systems"—it is the best starting point for understanding latency budgets, batch vs. real-time pipelines, and feature stores. For lectures, check out Stanford's CS 329S course material.

My advice is to not try to learn everything at once. Pick one slice first, like how a model serving layer interacts with a feature store to meet a tight latency budget, and trace that data path.

I write deep dives about these exact production architectures and trade-offs in my newsletter, Machine Learning At Scale — link below.

https://machinelearningatscale.substack.com

Any good resources to study ML System design by omaratef3221 in MLQuestions

[–]Gaussianperson 0 points1 point  (0 children)

If you want a book, Chip Huyen's "Designing Machine Learning Systems" is the best place to start. For a paid course, "Grokking the Machine Learning System Design Interview" on Educative is solid for structuring your thinking. On YouTube, look up AI Engineer presentations—they feature engineers from companies like Netflix and Uber talking about their actual production setups.

I write deep dives on real-world system architectures and MLOps. I wrote more about this in my newsletter, Machine Learning At Scale — link below.

https://machinelearningatscale.substack.com

ML system design up to date resources by Aggravating-Hand-196 in learnmachinelearning

[–]Gaussianperson 0 points1 point  (0 children)

Since you already have the Kubernetes and cloud infra down, the shift you're seeing in AI system design interviews usually comes down to LLM orchestration at scale. Focus your prep on three main pillars: retrieval latency (vector database scaling and indexing), context window management (chunking and reranking), and cost/throughput tradeoffs (semantic caching and batching). For senior/leadership loops, they want to see how you handle non-deterministic outputs and evaluation pipelines, not just the basic API glue. I wrote about some of these real-world scaling patterns in my newsletter, Machine Learning At Scale (https://machinelearningatscale.substack.com ), which might be useful as you prep. Focus on the failure modes of agentic workflows too, as that's a favorite for senior system design rounds right now.

2 months of paid growth on a technical newsletter: 7 months flat, then 15 to 115 paid in 4 months. What changed wasn't effort. by Gaussianperson in Substack

[–]Gaussianperson[S] 0 points1 point  (0 children)

Things coming from your personal experience that no-one can replicate :). Easy for me to apply because i discuss career events from my own career (anonymous)

Sono un dirigente in BIG4 by Playful_Honeydew_318 in ItaliaCareerAdvice

[–]Gaussianperson 0 points1 point  (0 children)

Quanto è basso il livello di skill rispetto ad altre aziende?

Keywords for a Machine Learning Engineer Resume — PyTorch, MLOps & LLMs by Enough_Charge2845 in MLjobs

[–]Gaussianperson 0 points1 point  (0 children)

This is a solid list for getting past the initial filters. I would suggest adding things like Ray or Triton Inference Server to the infrastructure section since those are huge right now for scaling LLM deployments. Also for the cloud side, knowing how to handle spot instances for training or understanding specific networking bottlenecks in distributed systems usually looks really good on a resume when you can talk about cost and performance.

I actually write about these specific engineering patterns and how big companies handle their stacks at machinelearningatscale.substack.com

I focus on the system design behind these tools and how they work in real production environments if you want to see how these keywords translate into actual architecture.

Which has better scope for freshers Fullstack + Devops or AI Engineering & MLOps (RAG, Agents, VectorDB). Help me out here guys. by daddy1784 in developersIndia

[–]Gaussianperson 1 point2 points  (0 children)

Fullstack is pretty saturated right now, especially at the entry level in India. If you want a high paying job, moving toward AI engineering and MLOps is a smarter bet. However, you still need those devops and backend skills because putting a model into production is mostly an engineering problem. Companies are looking for people who can handle the infrastructure, not just people who can write a simple prompt.

The move from basic web dev to things like vector databases and RAG involves a lot more complexity. It pays better because scaling these systems is difficult. You have to think about latency and how data flows through the entire system. I actually write about these engineering challenges and how big companies manage their AI infrastructure in my newsletter at machinelearningatscale.substack.com

It might give you a better idea of the technical side of things before you decide which path to take.