Sujar Henry on Why Access Still Isn’t Enough in Tech

He grew an audience by treating machine learning less like a mystery and more like a path that beginners can actually follow.

The internet was supposed to solve the access problem.

A person with a laptop can now learn programming from YouTube, take online courses, read research papers, follow engineers, copy roadmaps, ask AI for help, and watch tutorials from almost anywhere. The gate is more open than it has ever been.

Still, many beginners remain stuck outside.

The problem is no longer only that they cannot find information. It is that they cannot tell which information belongs first, which advice applies to them, and which path leads somewhere real.

Sujar Henry understands that confusion from both sides.

He is a 21-year-old big tech software engineer and content creator based in Washington, DC, originally from the Turks and Caicos Islands. Across his platforms, he has grown to more than 50,000 followers by making content around software engineering, machine learning, and AI.

But the number is less interesting than the reason behind it.

Henry is building for people who do not just need motivation to enter tech. They need the field to become legible.

The hard part is no longer finding information

In a large tech market, the path into software can look obvious from the outside.

There are schools, internships, meetups, local mentors, bootcamps, career fairs, and people nearby who can make the industry feel normal. Even if the route is difficult, the existence of the route is visible.

Henry did not grow up around that version of tech.

In the Turks and Caicos Islands, he says, there were not many people working in software engineering, AI engineering, or machine learning. The closest visible tech work was more practical IT, like fixing printers and maintaining basic systems.

For a child interested in programming, that creates a strange kind of distance.

The internet is available, but the industry still feels far away.

“Trying to learn technology and engineering was really tough,” he says. “All you really had was YouTube and things online.”

He first became interested in technology through his father, then began taking online coding classes in middle school. HTML and CSS came first. Python followed. Eventually, he moved toward machine learning.

The path sounds simple when compressed into a few sentences.

It was not simple while he was inside it.

A beginner without local guidance has to make decisions before they have enough context to make them well. Which language first? Which tutorial is credible? Which project is worth building? Which field is actually interesting? Which advice is just someone else’s lucky path dressed up as a rule?

Henry’s work starts from that gap.

A roadmap is different from advice

Tech content often gives people fragments.

One creator says to learn Python. Another says to build projects immediately. Another says computer science fundamentals are the only serious path. Someone else says degrees are unnecessary. Then the market changes, AI accelerates, and the advice begins contradicting itself faster than beginners can process it.

Henry is not trying to add another loud opinion to that pile.

He is more interested in structure.

“I wanted to be that bridge,” he says, “between them getting the interest and them actually learning more about it.”

That sentence explains both his content and his next product. Henry is currently building Axon, an app designed to help people learn machine learning through a clearer roadmap. The idea came partly from audience demand. A video he made on a machine learning roadmap reached around 100,000 views, which gave him a small but meaningful signal that people were not just curious about AI. They wanted order.

Machine learning is especially vulnerable to confusion because it sits behind so many intimidating doors at once.

There is math. There are algorithms. There is programming. There are research papers. There are shifting model architectures, agent systems, small language models, tool use, and a constant stream of new terms that make the field feel more advanced than it may need to feel at the beginning.

Henry follows research papers to understand where the industry is moving. That habit gives his content a different center of gravity. He is not only reacting to whatever tool is trending. He is watching the source layer where many of those trends begin.

“If you follow the research papers,” he says, “a lot of times you’ll end up seeing where the market moves.”

The challenge is translating that movement for people who are not yet technical enough to follow it directly.

That is where the creator becomes useful.

Trying everything can be a serious strategy

Henry’s advice to younger beginners is simple: try everything.

It could sound unfocused. In his case, it is closer to a method.

He entered college thinking he wanted to focus specifically on software engineering. Then he moved through back end, front end, databases, and other parts of the field before landing more seriously on machine learning and AI engineering.

“What you think you may like may not always be the case,” he says. “You just got to see what sticks.”

That is a practical way to think about early technical identity.

Beginners often want a clean answer too soon. They want to know whether they should become a software engineer, AI engineer, data scientist, founder, content creator, or something else before they have touched enough of the work to know what kind of problems they actually enjoy.

The cleaner path may come later.

In the beginning, exploration is not a lack of discipline. It is how the field becomes real.

Henry’s own story also complicates the usual creator narrative. He is not presenting content as an escape from engineering. He still works as a software engineer and keeps that side separate from his social media presence. His content is not a replacement identity. It is a way to make the industry easier to approach for people standing at the edge of it.

That gives the brand a clearer function.

It is not only about being seen as technical.

It is about making technical work feel reachable without pretending it is easy.

Resilience looks ordinary while it is happening

The first serious hurdle Henry names is not dramatic.

It was trying to land his first internship in college.

He emailed people. He went on LinkedIn. He cold messaged recruiters and employees. Much of it did not work. At times, he felt like he was being annoying.

That feeling became part of the lesson.

“You really have to be annoying,” he says, “because no one else is going to go out there and do the work for you.”

There is a rough honesty in that line. It is not the polished language of personal branding. It is what early ambition often feels like before it becomes presentable.

The same rhythm later showed up in content.

A beginner posts one or two videos, watches them fail, and starts to wonder whether the whole thing is pointless. Henry kept making videos, studying what worked, seeing what did not, and letting the repetitions teach him.

That is the less visible part of audience growth.

From the outside, a creator crosses 50,000 followers and the milestone looks like proof of talent. From the inside, it is usually a longer chain of small adjustments, failed posts, better hooks, clearer explanations, and a slowly improving sense of what people need.

For Henry, the audience also creates responsibility.

He monetizes through sponsorships and brand deals, including developer tools and a Dell partnership. But the larger ambition is not only commercial. He wants to reach more than a million people and build something tangible for beginners trying to enter tech.

The obvious version of Henry’s story is that a young software engineer from a small island built an audience by teaching AI.

But that reading is too neat.

His work is really about the space between access and direction: the point where information is everywhere, but the path still feels hard to see.

The internet made technical knowledge available. It did not automatically make the path coherent. It gave beginners more material than any previous generation had, then left many of them to sort it alone.

Henry’s work sits there.

Between curiosity and competence.

Between scattered advice and a sequence someone can follow.

Not everyone needs another reason to believe tech is possible. Some people need the first step, then the second, then enough clarity to keep going when the field stops looking simple.