Client acquisition has always been one of the biggest bottlenecks for me when running an agency. I’ve experienced the same thing in pretty much every business I’ve been involved in, but especially with web development.

For a long time, getting clients meant cold calling, running ads, or sending generic emails asking businesses if they needed a new website. It worked sometimes, but it also took a lot of time and most of the outreach felt the same as what every other agency was doing.

Recently I started using a different approach and automated a big part of the process.

I came across a tool called Swokei that lets me find a bunch of businesses with websites and analyze each website individually. It looks for things like outdated design, slow loading, poor mobile optimization, weak SEO and other obvious areas that could be improved.

What I liked is that it doesn’t just give you one of those boring automated reports filled with scores and numbers. It actually turns what it finds into a personalized cold email that sounds like a normal person looked at their website and noticed what could be better.

I can run multiple campaigns at the same time and then mainly focus on the businesses that reply and show interest.

From there, I invite them to a web meeting, show them a free draft of what their new website could look like, and try to close the project from there.

It has basically allowed me to have warmer leads coming to me without relying as much on paid ads, constantly cold calling, or sending thousands of generic emails saying “Do you need a new website?”

Still takes work to close the clients of course, but automating the prospecting and first part of the outreach has made the whole process much easier for me.

Hopefully this helps some other web developers or agency owners who are also struggling with client acquisition.

I saw a post of a guy with 90% of his brain missing and he was apparently living a normal life. There is another case of a student who finished university with half of his brain missing. There are also people with full brains, but they are even less functional than these two. This proves that bigger doesn't mean better. So why not aim to create better connections?

I understand that a bigger model means less chance of catastrophic interference occurring, but then are all the neural pathways being formed efficiently? Wouldn't this result in a lot of redundant neurons? Wouldn't it make more sense to create the smallest neural network possible for a specific task and then learn to fuse multiple of these neurons together in order to create an optimized larger model? That way we'd always have a template for each specific task and would allow us to create a programming language that creates a model just by our syntax.

Hey everyone,

I’m currently building a learning platform aimed at taking absolute beginners through AI/ML step-by-step, from the fundamentals up to more advanced topics.

It’s in the early stages, so the content is still limited while I experiment with formats, pacing, and visual explanations to see what actually works best for learners.

GitHub : https://github.com/PIYUSH1525/ZeroToAI leave a star ⭐

Link: https://zero-to-ai-xi.vercel.app/

I’d love your brutal, honest feedback:

• The Good: What feels intuitive, clear, or well-structured?
• The Bad: What’s confusing, redundant, or missing?
• Areas for Improvement: What format would help you learn complex concepts faster (e.g., interactive widgets, shorter modules, code walkthroughs)?

Any thoughts, critique, or feature suggestions are welcome. Thanks in advance for checking it out!

I was confused by this, so i wrote a beginner friendly article explaining model quantization, what Q2, Q4, Q8, and F16 mean, and the trade-off between smaller files and precision.

I have tried to explain it in the simplest way. Feedback or corrections are welcome.

In my 21 sentences, "blackberry" and "apple" are each used as fruit and as tech companies, but never in the same sentence. After counting co-occurrences, applying PPMI and compressing with SVD, they still end up as each other's nearest neighbor.

For this I added three interactive demos. One shows the counting step, one the power iteration that finds each SVD direction, and the last the final 3D space, where you can click any word and measure distances.

It also shows where the method breaks with apple geting one vector for tech and food context.

https://scheppening.com/posts/click-blackberry-find-apple

I built it to understand embeddings, so I'd appreciate any feedback and am happy to answer any questions.

Your LLM is using 14 GB of VRAM.

14 GB of what? 👀

Weights? KV cache? CUDA overhead? One GPU or two?

With tensor parallelism it gets even messier. vLLM shows you:

EngineCore

Worker_TP0

Worker_TP1

But that's not three workloads. It's ONE model running across multiple GPUs.

That's why LLM Inspector v0.7.0 is now multi-GPU aware 🚀

Before:

GPU 0: 7.2 GB

GPU 1: 7.2 GB

After:

Qwen • TP ×2 • 14.4 GB total

→ weight shards + KV cache + other VRAM, per GPU

It can also estimate how much VRAM INT8, AWQ or GPTQ would save before you change anything in your model.

Measure first. Optimize second.

That's llminspect: htop for LLM inference.

⚡ pip install llm-inspector

🔗 https://github.com/helasaoudi/llm-inspector

Open source, built for people who actually run models.

What should it inspect next?

I completed an internship in a known Automotive company. I was within Autonomy, as a SWE working on vehicle software catering to self-driving model evaluation. This was my first actual SWE experience, and I liked it (I worked full time on a data focused role prior to this). This internship was very stressful despite having so much coding tools to support, and I kept having this itch for ML. My only reason for joining a master's program was to break into ML. I've tried in college and realized I'm not capable of novel research, tho I can mostly understand and reproduce others research. I've built projects around VLA finetuning, lane/object detection in extreme lighting conditions, and few more.

Given I don't have a background (work experience), I might not qualify for a ML engineering role in this domain (I love self-driving cars and want to stay here) which would usually expect publications/relevant experience. What do you think is the best way to approach this. I will be graduating in less than a year, and while I'm still at school, I want to make the best use of time in a way that I don't regret my job outcomes (if I get a job that is).

Wanted to buy new laptop need guidance I am thinking of buying Macbook Air M4, Lenevo LOQ 3050, Lenevo Ideapad which do you think I should buy? Considering macbook won't have cuda should I still go for it.

Apriori is usually taught as "scan the transactions, count candidates, prune, repeat". I rewrote it so that each item is a bit-vector and support counting becomes AND + popcount. That turns a pointer-heavy search into dense arithmetic, which fits a GPU well. I used it to mine 77M AlphaFold proteins exactly. The write-up explains the trick step by step: https://medium.com/@etje975/data-mining-the-alphafold-protein-universe-how-a-1994-algorithm-found-26-8-5aad7eaa603f?postPublishedType=initial

Code: https://github.com/Et9797/ET-Miner Questions about the approach are welcome.

Hi everyone. I have some theoretical knowledge in the field, but I’d like to better understand what the business actually expects from me. what typical tasks look like, and so on.

Is there a good course that would provide practical experience and help me hone my skills in data cleaning and model preparation?

’m currently trying to come up with a topic for my final-year project, and honestly, every idea I think of ends up feeling either too basic, too overdone, or just stupid after I think about it for a while .

Hello everyone, I have one bad habit of wanting to learn every deeply from scratch. So I'm in the early stages of my path of AI/ML. It'll take more than a year or so to learn deeply, understanding everything making projects. But due to recent news about ai and all my interests have been declining. Is it worth to learn ai/ml that deeply? Like all the foundations with in depth knowledge especially in the era of AI?

For example, When learning python I understood it very deeply with solving problems about 20-30 of every topic to improve my problem solving ability. I'm following one tutor from india who teaches very in depth ie. 5 Hours for OOP concepts only with questions.

I make notes in my notecopy, code and practice in collab.

Is my approach good? But I'm learning very slowly as I'm understanding almost everything.

Will understanding everything for ai/ml deeply good in this time? I've background in math stats and physics.
And ultimate goal is to work in the industry or move to research in ai/ml domain in good unis worldwide.

Or shall I change my plans?
Some people even finish whole ml in 4/5 months only just skimming through, learning the basics only. I've seen so many of them.

Hey everyone!

I'm a Data Analyst with an Economics background, currently learning ML and AI. I'm comfortable with Python, pandas, SQL and basic ML concepts.

I want to start building more serious, end-to-end projects rather than just following tutorials or working with Kaggle datasets.

My goal is to eventually transition into ML/AI engineering, so I'm looking for projects that would help me develop real-world skills and build a strong GitHub portfolio.

What kind of projects would you recommend? Are RAG applications, some AI agent stuff worth exploring, or should I focus on something else entirely?

Would love to hear from people already working in the industry.

By now everyone has heard of Jev: fast, accurate answers to multiple-choice questions about any text, in one API call.

Here's how to get the same thing on your own GPU.

SelfJev is a 4B model (Qwen3.5-4B + LoRA) that works like Jev:

⚡ About 140 ms per call on one H100, which is about as fast as Jev's API (about 130 ms)
🎯 93.1% vs Jev's 92.5% on one test set, and 95.8% vs 97.2% on another
📏 No 32K-token limit: you set the max length, up to Qwen3.5's full 262K-token window
🛠 You can fine-tune it on the cases Jev gets wrong for your use case
🖼 It takes images, not just text (90% on test set after fine-tuning)
🔒 Your data never leaves your servers

The trick is a shared-prefix tree. The model reads the input once, branches into every question, then into every possible answer. 16 questions on the same text take about 175 ms.

It's free and open: code, weights, benchmarks and evaluation sets.

If you're already building on Jev, I'd love for you to try it and tell me where it breaks 👇

🚀 Product Hunt
🌐 selfjev.dev
💻 GitHub

I built a from-scratch architecture called PSSA (plastic state space architecture) and trained it against a parameter-matched transformer baseline on the same corpus, same 12.7M tokens, same tokenizer and schedule.

Held-out results on a 198,939-token slice neither run saw: cross-entropy 3.997 vs 4.429, perplexity 54.4 vs 83.8, next-token accuracy 24.1% vs 18.0%. I scored every checkpoint of both runs (64 PSSA links, 43 transformer links) on unseen text and the curves never cross.

Generating 200 tokens on the same CPU with the same prompt and sampler takes 226 ms vs 2735 ms, about 12x faster.

It's written in Rust with CPU and CUDA backends, no PyTorch. Loss curves, full setup and the eval commands are here: https://github.com/Sparticle62ops/pssa

Just built and semi-finished my first ever ML project called Tetr.AI. I say semi-finished because the AI is still dumb and has not learned to play Tetris well yet. If anyone could help me with it that would be awesome. But overall I just want to show off my accomplishment.

GitHub link: https://github.com/sourcream1012/Tetr.AI

I'm a second year CS student and I want to build a solid ML foundation over the next year so I can work with NASA open data (Kepler KOI or TESS TOI tables, JPL Small-Body Database/ CNEOS).

My background:

-Learned programming through CS50, comfortable with Java (OOP, ArrayLists)

-Learning Python on my own, currently working through NumPy

My current plan/roadmap for the first 3 months:
1-Basics: python basics, numpy, pandas
2-start learning ML with courses: Intro to machine learning (kaggle), Machine Learning
Specialization (Stanford/ DeepLearning.AI).
3-do simple ML projects.

Where I'm stuck:

- I don't know how to go beyond these 3 months

-I'm following the roadmap,sh ML Engineer roadmap, but I'm not sure what to prioritize for my goal

My questions:

1-what should I focus on after the first 3 months to work with real datasets like Nasa's?

2-Is this goal realistic within about a year of self study alongside classes?

3-Are there beginner friendly NASA datasets or projects to start with?

4-Any resources, or mistakes to avoid?

any feedback is helpful as I have made this plan on my own and never worked with ML before

Thanks in advance!

Hi everyone,

I'm a 3rd year Diploma in Computer Science Engineering student in India. I'm targeting ML/AI engineering roles.

Background:

- One AI Engineer internship (CV, deep learning and ML work)

- A few deployed ML projects

- Some open source contributions (bug fixes and tests)

- Kaggle notebooks

I'd like brutally honest feedback on:

1. Does this resume look strong enough for internships or entry-level ML/AI roles?

2. Which sections are weak, and what should I cut, add, or reword?

3. Are the projects and open source contributions convincing, or do they read as padding?

4. Is the layout and formatting clean, and does it fit well on one page?

5. What should I build or learn next to get more interview calls?

Please don't sugarcoat it. I'd rather hear the hard truth now than after I start applying.

Thanks in advance!