Hello, hejes.my — A Manual for Readers

Welcome, operator. You are reading the very first transmission from hejes.my — a publication that takes the day's technology news and turns it into careful, original analysis you can actually use.

This post is your manual. It explains what this site is, how it is produced, and why we bother. For the one-minute version, see the about page.

What is hejes.my?

hejes.my is a bilingual tech publication (English + Malay). Its job is to take the noise of the daily tech news — dozens of RSS feeds, announcements, and git activity — and turn it into reading that adds something: context, a developer's angle, and the local picture.

The morning starts at pagi.hejes.my, a briefing service that pulls dozens of feeds into a single daily digest. From there, each story that makes the cut is researched, written, and checked against primary sources before it appears here. There is no auto-publish. The loop is simple:

fetch -> draft -> research -> review -> approve -> publish

The workflow in a nutshell

1. Fetch — the morning agent pagi.hejes.my pulls dozens of RSS feeds and git activity into a daily briefing.
2. Draft — a story is turned into an original article (EN or MS), with the sources lined up alongside it.
3. Cover — a pixel-art cover image is generated for the post.
4. Review — the editor fact-checks the claims, edits the prose, and only then ships it.

Why not just report the news?

Because links rot and duplicated wire copy ranks worse than writing that adds something. Original prose, written around facts rather than copying them, is actually useful — and it is the only kind this site publishes. The rule here is simple: you will never see a verbatim press release on this page. Every story still needs a human review step before it ships, for exactly the reasons every automated pipeline needs one.

How we keep it honest

Three guarantees, all checkable by you:

1. No auto-publish. The approve step in the loop above is a human gate, never a formality. Boring or dubious drafts die at the desk.
2. Sources on every article. Newer posts carry a cited-sources section with a fact-check stamp, so you can re-trace any claim to its origin — and see how we mark how each piece was produced instead of hiding it.
3. Corrections in the open. When we get something wrong, the fix ships in the article with an update marker, not a silent edit.

A small code sample

Since this is a tech blog, every post gets at least one block of code. Here is the publish loop in pseudocode:

const pipeline = async (briefing: Briefing): Promise<Post> => {
  const item = briefing.pick(0);            // pagi.hejes.my daily items
  const draft = await research(item);       // original article + sources
  await generateCover(draft.slug);
  const post = await editor.approve(draft); // human in the loop
  return git.commit(post);                  // promote -> publish
};

Notice the editor.approve() step — that is the human gate that never gets skipped.

What is next?

• More categories: coding, security, science, AI tooling.
• A newsletter so you never miss a post.
• Verification stamps on every new post, so the check you can already see on recent articles becomes universal.

Read the Malay version of this post using the language switch — the two languages are written independently, not machine swaps.

Keep a good signal, operator. We'll be here daily.

Sources

• hejes.my: hejes.my — About
• hejes.my: hejes.my — Home