Jaxon Smith's profile on Product Hunt

About

IT professional specializing in cloud infrastructure, virtualization, and server management. Skilled in system hardening, vulnerability management with Tenable, and patching strategies that strengthen security and ensure compliance. Certified in RHCSA, CCNA, AZ-104, ITIL 4, Security+, Network+, and A+, with a focus on optimizing hybrid environments, improving security posture, and aligning IT with organizational goals. Currently deepening expertise in Red Hat administration and cloud security, with a long-term focus on infrastructure innovation, automation, and the evolving intersection of AI and cybersecurity.

Badges

Tastemaker

Gone streaking

Forums

•

17h ago

Would you trust AI to design your hiring strategy?

AI tools can now analyze years of employee performance reviews, retention metrics, and project outputs to generate hiring profiles and team structures: "hire for X trait," "keep teams under Y size."

I ve spent over a decade leading cross-functional teams, and I m skeptical. Not because the AI can t spot correlation, but because I ve seen how easily corporate data misrepresents human dynamics. A team can look high-performing on paper while burning out its best people behind closed doors. If the AI learns from that HR record, it standardizes burnout with total confidence.

Here s where I ve landed so far. I d need three things before acting on an AI-generated organizational lesson:

The qualitative feedback, visible. Skip-level notes, team sentiment, and anonymous feedback loops. Not just productivity charts.
The market context at the time. A hyper-aggressive growth playbook from a bull market will backfire in a retention-focused downturn. The lesson should state when it applies.
A leadership sign-off. A manager who navigated the human side confirms the nuance before it becomes an algorithmic hiring filter.

•

17h ago

Do you trust upvotes when picking a new tool to try?

I discover a lot of tools through Product Hunt, and the upvote count is usually the first thing I look at. But it doesn t always match how useful a tool turns out to be for me.

Last month I signed up for a #1 product of the day because of its huge upvote count. I used it twice and forgot about it. A few weeks earlier I had tried a small launch with barely 50 upvotes, a simple tool for organizing browser tabs, and I still use it every single day.

It made me wonder if I give upvotes too much weight. Maybe the comments and the maker s replies say more about quality than the ranking does.

When you decide what to try, what do you look at first: upvotes, comments, the demo, or something else? Has a low-ranked launch ever surprised you?

•

2d ago

When your dashboard doesn't have enough data, what do you show?

Something I changed my mind about while building a finance app for freelancers.

Say someone made $2,000 last month and $0 this month. The math says -100%. A big red number.

It's correct and it's still misleading. For a freelancer, an empty month often just means a payment is late. So in my app, when a month is at zero, that comparison doesn't show at all. Same with small samples: if there isn't enough history to say something, the screen says that instead of guessing.

The rule I ended up with: