Forem: Siti Aisyah Mat Zainal

Pour Decisions: An April Fools Anti-Game About Futile Effort

Siti Aisyah Mat Zainal — Thu, 02 Apr 2026 07:08:56 +0000

This is a submission for the DEV April Fools Challenge

What I Built

Pour Decisions — an interactive anti-game where you try to pour tea into a teapot… that absolutely refuses to cooperate.

It starts like a calm, elegant tea ritual.
Soft colors. Peaceful vibe. Simple task.

Then the teapot moves.

Then it runs.

Then it judges you.

The entire experience is designed to feel:

Almost doable
Slightly unfair
Increasingly ridiculous

There is no real “win”.

Only effort.
And regret.

Demo

🌐 Live Demo: https://pourdecision.netlify.app/

Try it yourself… if you think you can beat a teapot.

Code

💻 GitHub Repo: https://github.com/aisyahz/Pour-Decision

How I Built It

This project is a mix of UI playfulness, real-time interaction, and just enough chaos to make users question their life choices.

Tech Stack
React 19 (functional components + hooks)
Vite for fast dev/build
TypeScript
Tailwind CSS 4 for styling
motion/react for smooth, physics-based animations
Lucide React for icons
canvas-confetti for the fake “victory”
Key Technical Ideas
🫖 Teapot Avoidance Logic

The teapot constantly tracks the cursor position and moves away when you get close.

Global mousemove listener
Distance-based reaction
Increasing difficulty (aka frustration scaling)
☕ Pouring System

Click and hold = pouring tea.

State-driven pouring (isPouring)
Interval loop updates progress + triggers effects
Tea stream rendered via SVG/Canvas component
🔊 Procedural Audio (no files!)

Used the Web Audio API to generate sound in real-time:

OscillatorNode
GainNode

So the pouring sound is actually synthesized, not imported.

🎬 Animation System

Using motion/react:

Spring-based transitions (for smooth but playful movement)
AnimatePresence for UI elements appearing/disappearing
Teapot movement feels slightly alive (and annoying)
🧠 State & “Frustration Engine”

Tracked things like:

Mouse position
Pouring state
Progress
Hidden “frustration level”

As frustration increases:

Teapot reacts faster
UI becomes less trustworthy
Success becomes… questionable
🎨 Design Language

Theme: Elegant Frustration

Soft tea-inspired palette (porcelain, tea-brown, warm tones)
Serif typography → feels calm & refined
But behavior → chaotic, uncooperative, slightly evil

The contrast is the joke.

Prize Category

🏆 Community Favorite

Because this is:

Highly relatable (we’ve all fought UI like this)
Shareable (“I lost to a teapot” energy)
Simple concept, but strong emotional reaction (frustration + laughter)

Also… I think everyone deserves to experience being outplayed by a teapot at least once.

Final Thoughts

This project is basically a tribute to:

forms that almost submit
buttons that move away
bugs that disappear when you debug
and systems that almost work

You did everything right.
Productivity: 0%.

If you tried it…
be honest:

Did you actually think you could win? 😭

Choose Your Burnout

Siti Aisyah Mat Zainal — Thu, 02 Apr 2026 06:25:15 +0000

This is a submission for the DEV April Fools Challenge

Choose Your Burnout
The inevitable simulation of modern work culture.
What I Built

I built a game that solves absolutely nothing.

Choose Your Burnout is a dark, choice-based simulation where every path leads to the same destination: a slow, optimized collapse.

You start by selecting your career:

The Corporate Labyrinth
The Disruptive Alchemist (Startup)
The Freelance Mirage
The Academic Basement
The Gig Economy Engine

From there, you make decisions that trade:

Sanity
Sleep
Energy

…for:

Money
Ego
and the illusion of progress

There is no winning state.

Only different versions of “this seemed like a good idea at the time.”

Demo

🔗 Live Demo:
[👉https://ai.studio/apps/321d42d6-cfd6-4624-89dc-ed8934b60f87?fullscreenApplet=true]

Code

🔗 GitHub Repository:
[👉 https://github.com/aisyahz/Choose-Your-BurnOut.git]

How I Built It

This project is powered by:

React + Vite – for fast iteration and a clean component structure
Tailwind CSS – for brutalist, high-contrast UI control
Framer Motion (motion/react) – for cinematic transitions, glitches, and subtle tension
SVG + layered rendering – to build the “Digital Mask” face system
The Burnout Engine

At the center of the experience is a reactive face:

A pseudo-3D Digital Mask that evolves based on your stats.

Sleep ↓ → eyes droop and blink irregularly
Sanity ↓ → asymmetry, glitches, red flickers
Energy ↓ → head tilts, movement slows
Ego ↑ → forced, unsettling smile
Money ↓ → structural fragmentation

It doesn’t just display stats.
It becomes them.

Key Features
🧠 The Burnout Engine

A living, degrading face that reacts to every decision.

🧭 Thematic Career Paths

Each path has its own visual and psychological identity:

Corporate → structured, grid-like, suffocating
Startup → chaotic, pulsing, unstable
Freelance → fragmented, isolated
Academic → slow decay, heavy inertia
Gig → fast, repetitive, algorithm-driven
🧪 Premium Glitch Aesthetic

A sculpted dark UI with:

chromatic aberration
flickering overlays
system logs
subtle instability

Everything feels… almost under control.

📸 The Screenshot Weapon

At the end, you receive a final report:

A dramatic “digital eulogy” of your decisions.

Designed to be shared.
Designed to hurt.

The Vibe

Polished.
Cold.
Slightly accusatory.

It looks like a productivity tool.
It behaves like a breakdown.

Why I Built This

I wanted to explore a simple idea:

What if we treated burnout like a system…
and optimized it?

Not to fix it.
Just to measure it. Beautifully.

Prize Category
🎯 Community Favorite

This project is designed to be:

instantly understandable
visually memorable
screenshot-worthy
painfully relatable
Final Line

“You did everything right.”
Productivity: 0%

Hashtags

ChooseYourBurnout #GameDev #IndieGame #UIUX #BurnoutEngine #DigitalArt #WebDev

One security alert changed how I think about dependencies

Siti Aisyah Mat Zainal — Wed, 01 Apr 2026 02:46:40 +0000

In 2026, we saw something that many developers don’t expect to deal with early in their career:

👉 A supply chain attack on a popular npm package.

This package is widely used for making HTTP requests — something almost every frontend project depends on.

⚠️ What happened?

A malicious version was briefly published to npm.

For projects using:

"package-name": "^x.x.x"

npm could automatically install a newer version — including the compromised one — during npm install.

That means:

👉 You don’t need to change your code
👉 You don’t need to update anything manually
👉 Just installing dependencies could pull in malicious code

🧠 What I learned

This incident made me realize:

Dependency management is security

Using ^ feels harmless… until it isn’t.

Auto-upgrading dependencies can introduce:

breaking changes
vulnerabilities
or even malicious code

Not all “vulnerabilities” are equal

After running npm audit, there were many warnings.

But the real question is:

👉 Which ones actually matter?

Some are dev-only tools
Some are indirect dependencies
Some have no real runtime impact

Understanding context is more important than blindly fixing everything.

Don’t rush to “fix everything”

It’s tempting to run:

npm audit fix

But in real projects:

it may introduce breaking changes
it may conflict with production versions
it may override controlled dependencies

Sometimes the correct action is:
👉 do nothing — and escalate properly

Align with production, not assumptions

Instead of upgrading to the “latest version”, the safer move was:

👉 Pin to a known safe version already used in production

🛡️ Final takeaway

Security isn’t just about backend or infrastructure.

Sometimes it’s as simple as:

👉 a single line in package.json

"dependency": "^x.x.x"
💡 As developers, we should:
Be careful with version ranges (^, ~)
Understand what our dependencies actually do
Treat npm install as a potential risk surface
Think before upgrading — not just react
🚀 Personal note

This was one of those moments where I realized:

Being a developer is not just about writing code…
It’s about understanding the system, the risks, and the impact of small decisions.

SoftwareEngineering #WebDevelopment #FrontendDeveloper #JavaScript #ReactJS #NodeJS

My SV Was Right Again… And I Finally Get It

Siti Aisyah Mat Zainal — Mon, 30 Mar 2026 04:01:35 +0000

I had one of those moments today.

The kind where you think you're solving the requirement…
but your senior is actually thinking 3 steps ahead.

At first, I was focused on:

👉 “Can we do this feature or not?”

Simple.

User deletes a Workgroup → system reassigns everything to default.
Done. Works. Ship it. 🚀

Then my SV raised a concern.

Not about implementation.
But about impact.

😶 The moment it hit me

What if the user made a mistake?

They delete a Workgroup…
everything silently moves to default…

Then later:

“Eh… can I revert back?”

And suddenly you realize:

❌ No history
❌ No undo
❌ No tracking
❌ No easy recovery

💥 The real problem

👉 We allowed a destructive action without a safety net

😭 Who handles it next?

Not the system.

👉 Support team
👉 Developer (me 🥲)
👉 SV

User:

“Can help fix my data?”

Me:

“...let me open DB manually”

🧠 That’s when it clicked

Being a developer is not just:

👉 Can we build this?

It’s:

👉 Should we build this?

🔥 Why this matters (real world)

Big systems don’t allow silent data movement.

Because:

data ownership matters
audit trail matters
mistakes are expensive
users don’t always realize impact
🎯 What I learned today

There are always options:

Option A — Safe

Block deletion if in use

Option B — Convenient

Auto reassign (risky)

Option C — Thoughtful

Allow it, but:

show impact
warn user
track changes
🧠 The real upgrade

Today I didn’t learn new code.

I learned how to think like:

👉 system owner
👉 not just developer

🙌 Final thought

Your senior isn’t blocking you.

They’re protecting the system
from problems you haven’t seen yet.

And yeah…

My SV was right. Again 😂🔥

Before the Code, There Was Curiosity - The Mind of a Woman Developer

Siti Aisyah Mat Zainal — Tue, 10 Mar 2026 16:04:00 +0000

This is a submission for the 2026 WeCoded Challenge: Frontend Art

Show us your Art

🌌 Live Interactive Experience

Explore the installation here:

👉 https://womenmind.netlify.app

This piece is designed to be experienced interactively.

Users navigate a living neural constellation where each node represents a cognitive force that shapes how developers think and create.

The journey begins with curiosity and expands into a constellation of ideas, ultimately connecting modern developer mindsets to the pioneers who helped shape computing history.

The artwork combines:

• interactive constellations

• neural network metaphors

• cinematic motion

• generative particle systems

The goal is to transform abstract developer traits into something visual, explorable, and alive.

Inspiration

Technology history is filled with brilliant pioneers whose contributions shaped modern computing. Many of these innovators—like Ada Lovelace, Grace Hopper, and others—pushed the boundaries of what technology could become.

This project was inspired by a question:

What if we could visualize the mindset behind innovation itself?

Instead of representing developers through resumes or technical skills, I wanted to represent the cognitive forces that drive innovation:

• curiosity that sparks discovery

• creativity that imagines new possibilities

• logic that structures ideas into systems

• empathy that keeps technology human-centered

• collaboration that turns ideas into reality

By visualizing these forces as a living constellation, the experience becomes less about individual achievement and more about shared lineage and collective progress in technology.

The constellation metaphor also reflects how ideas travel through time—how today's developers are influenced by the pioneers who came before them.

My Code

The full source code for this project is available here:

🔗 GitHub Repository

https://github.com/aisyahz/women-mind-developer

Key technologies used:

• Next.js 15 (App Router)

• React 19

• TypeScript

• Framer Motion for cinematic animation

• SVG + Canvas rendering for constellation visualization

• Tailwind CSS for styling

Core component:

NeuralConstellation.tsx

This component orchestrates the constellation system, including:

• dynamic node rendering

• orbital particle systems

• neural thread connections

• curiosity-triggered expansion animation

• insight shard discovery system

The project focuses on combining interactive storytelling with modern web animation techniques to create an experience closer to digital art than traditional UI.

A cinematic interactive constellation exploring curiosity, creativity, and the shared lineage of women in technology.

wecoded

frontend

webdev

javascript

showdev

One Sentence From My Senior Engineer Changed How I Think About Software

Siti Aisyah Mat Zainal — Mon, 09 Mar 2026 03:36:02 +0000

This is a submission for the 2026 WeCoded Challenge: Echoes of Experience

One Sentence From My Senior Engineer Changed How I Think About Software

When I first started working as a developer, my knowledge was everywhere.

Some notes were in notebooks.
Some were in sticky notes.
Some were in screenshots.
Some were buried inside ChatGPT conversations.

And when I needed to remember how something worked… I had to search through chaos.

At the time, I thought this was normal. I was learning fast, solving problems, writing code, fixing bugs. I believed the important part was simply getting things to work.

Then one small comment from my senior engineer changed how I think about development.

The Moment I Realized Something Was Missing

One day my senior reviewed how I tracked development information and said something simple:

“Your notes are scattered.”

It wasn’t criticism in a harsh way. It was more like an observation from someone who had spent 20 years designing systems and architectures.

I started paying attention to how she worked.

Everything she did had structure.

Documentation.
Functional specifications.
Technical notes.
System flow explanations.

When she needed to revisit something months later, she didn’t search randomly.

She knew exactly where the information lived.

That moment made me realize something important.

Being a developer is not just about writing code.

It’s about building systems that your future self and your team can understand.

Learning to Think Like an Engineer

As a junior developer, most of my energy went into solving immediate problems:

• Why is this API failing?
• Why is the database returning this value?
• Why is this UI component breaking?

But experienced engineers think differently.

They think about:

• traceability
• documentation
• architecture decisions
• long-term maintainability

I started reorganizing everything.

Instead of scattered notes, I began structuring information by:

Development tasks
System flows
Backend services
Frontend behaviors
Database logic

Even ideas from debugging sessions or conversations with colleagues were captured and categorized.

Slowly, things started to change.

When I returned to a problem weeks later, I could understand it immediately.

A Quiet Skill Many Developers Ignore

Something I noticed while working in tech is that documentation is often underestimated.

Many developers focus only on writing code.

But good documentation does something powerful.

It turns knowledge into something shareable and reusable.

It helps teammates understand decisions.

It helps future developers maintain systems.

And most importantly, it helps you grow faster, because you can see patterns in your own learning.

What This Means for Underrepresented Developers

For many of us entering tech without traditional guidance, we often learn through trial and error.

We pick up skills piece by piece.

But mentorship — even small moments of guidance — can change everything.

One sentence from a senior engineer made me rethink how I approach my entire workflow.

Not because she gave a lecture.

But because she demonstrated what experience looks like in practice.

The Lesson I Carry Forward

Today, I still make mistakes.

I still get stuck debugging.

I still ask questions.

But one thing changed permanently.

I no longer see development as just writing code.

I see it as building systems of knowledge.

And sometimes the biggest growth in your career doesn't come from a complex algorithm or a new framework.

Sometimes it comes from a simple moment when someone more experienced quietly shows you a better way to think.

And you decide to learn from it.

If you're early in your developer journey, here's something I wish someone told me earlier:

Write code, yes.

But also write down why the code exists.

Your future self will thank you.

[Boost]

Siti Aisyah Mat Zainal — Fri, 06 Mar 2026 14:39:19 +0000

Join the Notion MCP Challenge: $1,500 in Prizes!

Jess Lee for The DEV Team ・ Mar 4

#notionchallenge #devchallenge #mcp #ai

[Boost]

Siti Aisyah Mat Zainal — Fri, 06 Mar 2026 08:20:23 +0000

🐾FurEver Care AI — Turning Pet Health Observations into Vet-Ready Timelines with Notion + AI

Siti Aisyah Mat Zainal ・ Mar 6

#notionchallenge #ai #mcp #devchallenge

🐾FurEver Care AI — Turning Pet Health Observations into Vet-Ready Timelines with Notion + AI

Siti Aisyah Mat Zainal — Fri, 06 Mar 2026 08:00:28 +0000

This is a submission for the Notion MCP Challenge

Quick Summary

FurEver Care AI is an AI-assisted pet health observation system built with Next.js, Notion, and Google Genkit + Gemini.

The system helps caregivers:

• record daily health observations
• detect wellness patterns
• generate structured veterinary summaries

By turning simple daily notes into structured Notion records, the system helps veterinarians understand symptom timelines more clearly.

What I Built

This project continues from my previous FurEver Log challenge entry.

In this version, I expanded the idea into a full system that combines:

• structured observation logging
• AI pattern analysis
• veterinary briefing tools

The goal is simple: help caregivers capture daily observations, organize them in Notion, and generate vet-ready summaries automatically.

The Problem

When a pet becomes sick, something unexpected happens.

You become a full-time observer.

You start noticing things you never paid attention to before:

• How much they eat
• Whether they still play
• If they used the litter box
• How long they stay inside it
• Whether their breathing feels faster
• If their energy feels “different”

But when the veterinarian asks questions like:

“When did the appetite change?”
“How many times did vomiting occur?”
“Has the energy been declining over the last few days?”

Many caregivers struggle to answer accurately.

Not because they don't care.

But because stress makes memory unreliable.

Information ends up scattered across:

• chat messages
• photos
• notes apps
• memory
• vet receipts

Reconstructing the timeline becomes incredibly difficult.

The Inspiration

This project was inspired by caring for my cat Abu.

When Abu got sick, I started writing small daily observations:

• appetite
• energy
• vomiting
• medications
• vet notes

But those records were scattered everywhere.

And when things became serious, I realized something painful:

The most important information about Abu's health was the hardest to organize.

So I built FurEver Care AI.

A system that helps caregivers turn everyday care observations into structured health timelines and vet communication tools.

What FurEver Care AI Does

FurEver Care AI is a Notion-powered health observation system for pet caregivers.

It transforms daily observations into structured health records and AI-assisted insights.

Features
🫀 Vitals Tracking

A real-time heart rate timer allows caregivers to tap along with their pet’s pulse to automatically calculate BPM.

This allows monitoring heart rate changes without needing special equipment.

🚽 Bathroom Monitoring

Daily tracking for important health signals:

• Poo presence
• Pee frequency
• Time spent in litter box
• Straining or accidents

These are often early indicators of illness but are rarely documented consistently.

📓 Daily Health Logs

Caregivers record:

• appetite level
• energy level
• symptoms
• medications
• observations
• notes

Each entry becomes a timestamped health record inside Notion.

🧠 AI Risk Assessment

Using Google Genkit + Gemini, the system evaluates each log and assigns a status:

• Normal
• Monitor
• Urgent

This helps caregivers quickly understand when a pattern might require attention.

Important note:

The AI does not diagnose illness or recommend treatment.
It only organizes observations.

📊 Trend Detection

The system compares recent logs and identifies patterns like:

• declining appetite
• persistent vomiting
• energy drops

These patterns appear as AI observations for the caregiver.

📈 Health Trend Visualizer

One challenge with daily observations is that patterns are difficult to see in plain text.

A small appetite change today may not feel important.

But across several days, a pattern might emerge.

To help detect gradual changes, I added a Health Trend Visualizer.

The chart maps:

• appetite levels
• energy levels

across recent logs.

If a specific pet is selected (for example Abu), the system switches to a Pet-Specific Trend View showing recovery or decline over time.

If no pet filter is applied, the chart shows a global overview of recent observations.

This turns simple logs into visual wellness trajectories.

📄 Vet Brief Generator

Before a veterinary visit, caregivers can generate a structured briefing document containing:

• symptom timeline
• observation patterns
• medication history
• AI-generated questions to ask the vet

The brief can also be exported as a professional PDF for clinic visits.

🤍 Care Moments

Illness monitoring can be emotionally exhausting.

So the app also allows recording small care moments, such as:

• extra cuddle time
• quiet companionship
• comfort routines

Because caregiving isn’t only clinical.

It’s emotional.

Screenshots
Daily Health Log

AI Insights Dashboard

Health Trend Visualizer

Vet Assistant

Live Demo

You can test the application here:

Demo:
https://furever-careai.netlify.app/

Try the following flow:

1️⃣ Record a Daily Health Log
2️⃣ View the record syncing to Notion
3️⃣ Run AI wellness analysis
4️⃣ View the health trend chart
5️⃣ Generate a Vet Brief
6️⃣ Export the summary as PDF

Video Demo

demo

jumpshare.com

Suggested walkthrough:

Record a Daily Health Log

Show the entry syncing into Notion

Run AI wellness analysis

Show trend visualization

Generate a Vet Brief

Export the report as PDF

Repository

GitHub:

https://github.com/aisyahz/FurEver-Care-AI--Pet-Health-Copilot-

The project includes:

• Notion API integration
• Genkit AI workflows
• real-time observation logging
• wellness trend visualization
• vet briefing generation
• PDF export

System Architecture

The system follows a simple architecture:

Caregiver Input (Next.js UI)
↓
API Routes
↓
Notion Database (Source of Truth)
↓
AI Analysis (Genkit + Gemini)
↓
Insights Dashboard + Vet Brief

This keeps the caregiver in control of the raw data while AI assists with interpretation.

How I Used Notion MCP

Notion MCP enables AI agents to interact directly with structured Notion databases.

In this project, Notion serves as the source of truth for all health records.

Using MCP, the AI agent can:

• read Daily Health Logs
• analyze recent entries
• tag records as Normal / Monitor / Urgent
• generate follow-up caregiving tasks
• create structured Vet Visit Briefs

All outputs are written back into Notion, keeping the system transparent and editable.

This makes the system human-in-the-loop rather than AI-controlled.

Challenges I Faced

One challenge was ensuring the Notion database remained the single source of truth.

Because AI observations are written back into the same database, the schema had to be carefully designed so that:

• caregiver inputs remain editable
• AI fields remain distinguishable
• system metadata does not interfere with manual records

Another challenge involved managing AI rate limits when generating vet summaries and analysis.

To avoid excessive API usage, the system analyzes only the most relevant recent health logs.

Why Notion Works So Well Here

Notion provides:

• structured databases
• flexible schema design
• relational data
• API access
• AI workflow compatibility

This makes it ideal for human-centered caregiving systems.

Instead of replacing human judgment, the system:

• organizes observations
• highlights patterns
• improves communication with professionals

The Bigger Goal

This project isn't about replacing veterinary care.

It's about solving a quieter problem:

When someone is caring for a sick animal, the hardest part is remembering everything accurately.

FurEver Care AI helps caregivers turn daily observations into reliable timelines, allowing veterinarians to focus on treatment instead of reconstructing history.

And maybe, just maybe, it helps caregivers feel a little less overwhelmed.

Inspired by Abu

FurEver Care AI was inspired by caring for a cat named Abu.

Abu reminded me that careful observation, patience, and presence matter more than perfect records.

This project simply tries to make those observations easier to keep.

If it helps even one caregiver communicate their pet's condition more clearly to a veterinarian, then it has already served its purpose.

Why I Started Structuring My Development Notes (After Getting Called Out 😅)

Siti Aisyah Mat Zainal — Wed, 04 Mar 2026 02:18:04 +0000

Early in my career as a software engineer, my notes were… chaos.
My Supervisor Said My Notes Were Scattered. She Was Right.

Some were in notebooks.
Some in sticky notes.
Some were screenshots.
Some were in Slack messages.
And honestly a lot of them were inside ChatGPT conversations.

Whenever I solved something during development I would write it down somewhere.

The problem was that “somewhere” was never the same place.

So when the same problem appeared again, I had to search everywhere.

Or worse, ask my supervisor again.

One day during a discussion my supervisor casually pointed something out.

She said my notes were scattered.

She has more than 20 years of experience as an architect engineer, software engineer and solution analyst. When she said that, I started paying attention to how she works.

Whenever we needed to check something she didn’t search chats or scroll messages.

She simply opened documentation.

FRS
Technical documentation
System notes

Everything was structured and traceable.

Need to check a system flow. Open the document.
Need to confirm a requirement. Open the document.
Need to understand logic. Open the document.

It looked effortless.

And honestly, I was amazed.

After that I started observing how other developers around me keep track of their knowledge.

One of my colleagues showed me something very simple.

Google Keep.

Just clean notes organized by sections. Things like project setup, debugging notes, configuration steps and useful commands. Everything searchable.

That was the moment something clicked for me.

The real problem was not forgetting.

The real problem was not being able to find what I already learned.

So I changed one small habit.

Whenever ChatGPT helps me solve something during development like debugging an error, understanding a framework or fixing configuration I extract the useful parts and save them into my own structured notes.

Now my notes look something like this.

Project Setup
Environment configuration and installation steps

Common Errors
Error message, root cause and solution

Debugging Notes
Things that broke and how I fixed them

Architecture Understanding
Service flow and system logic

Database Notes
Important tables and queries

Useful Commands
Terminal commands and scripts

The difference has been huge.

When I return to a project after a few days or weeks I don’t need to remember everything from scratch. I just search my notes.

It also reduced how often I interrupt my supervisor with questions like “how did we fix this last time”.

Something I didn’t expect is that organizing my notes made me feel more like an engineer building knowledge over time instead of someone solving the same problems again and again.

Good developers don’t just write code.
They build systems to remember what they learn.
Sometimes growth starts with a simple comment.

“Your notes are scattered.”

And that small sentence quietly changed how I work.

Tools and references:
Google Keep
https://keep.google.com

Notion
https://www.notion.so

Obsidian
https://obsidian.md

Functional Requirement Specification explanation
https://www.geeksforgeeks.org/functional-requirement-specification/

Software documentation guide
https://www.atlassian.com/work-management/knowledge-sharing/documentation

I’m still improving how I document things.

How do you organize your development knowledge?
Notes app, documentation, personal wiki or something else?
I would love to learn how other developers manage this.

Forem: Siti Aisyah Mat Zainal

Pour Decisions: An April Fools Anti-Game About Futile Effort

Choose Your Burnout

ChooseYourBurnout #GameDev #IndieGame #UIUX #BurnoutEngine #DigitalArt #WebDev

One security alert changed how I think about dependencies

SoftwareEngineering #WebDevelopment #FrontendDeveloper #JavaScript #ReactJS #NodeJS

My SV Was Right Again… And I Finally Get It

Before the Code, There Was Curiosity - The Mind of a Woman Developer

Show us your Art

Inspiration

My Code

wecoded

frontend

webdev

javascript

showdev

One Sentence From My Senior Engineer Changed How I Think About Software

One Sentence From My Senior Engineer Changed How I Think About Software

The Moment I Realized Something Was Missing

Learning to Think Like an Engineer

A Quiet Skill Many Developers Ignore

What This Means for Underrepresented Developers

The Lesson I Carry Forward

[Boost]

Join the Notion MCP Challenge: $1,500 in Prizes!

Jess Lee for The DEV Team ・ Mar 4

[Boost]

🐾FurEver Care AI — Turning Pet Health Observations into Vet-Ready Timelines with Notion + AI

Siti Aisyah Mat Zainal ・ Mar 6

🐾FurEver Care AI — Turning Pet Health Observations into Vet-Ready Timelines with Notion + AI

demo

Why I Started Structuring My Development Notes (After Getting Called Out 😅)

productivity

softwareengineering

beginners

learning

career

[Boost]

Happening Now: DEV Weekend Challenge!! Submissions due March 2 at 7:59am UTC.

Jess Lee for The DEV Team ・ Feb 27

[Boost]

🐾 FurEver Log — The App I Built After Losing Abu

Siti Aisyah Mat Zainal ・ Feb 28