Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Intelligence View
⚡ tsecurity.de Intelligence

I'm a Younger Builder. I've Failed 4 Times. Here's why I'm Still Going.

This is the first post in a series where I document everything — the ideas, the failures, the process, and the journey Who Am I? My name is Basit. I'm a younger builder, from Pakistan, and I'm an engineering student who spends more time b…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

This is the first post in a series where I document everything — the ideas, the failures, the process, and the journey



Who Am I?

My name is Basit. I'm a younger builder, from Pakistan, and I'm an engineering student who spends more time building products than studying for exams.

I see the world like a lens. Always observing. Always framing. Always looking for what others miss.

I don't have a computer science degree. I don't have a mentor sitting next to me. I don't have a community around me that thinks the way I do. Most people in my environment don't understand what I'm trying to do and honestly, that includes my family.

But I'm building anyway.

The Honest Part Nobody Talks About

Here's something most "young builder" stories skip:

I've worked on 4 ideas. None of them made it past the prototype stage. Not because the ideas were terrible some of them were actually decent but because I kept finding reasons to stop before I ever reached real users.

That's not failure. That's something worse: quitting before you even get to fail.

I realized this recently when I read about Pieter Levels the indie hacker behind Nomad List, Remote OK, and a dozen other products. The man failed 90+ times before anything worked. Ninety. And he kept going. Not because every idea was brilliant, but because he treated each one as an experiment, not an identity.

I was treating my ideas like they were me. So when an idea felt shaky, I felt shaky. And I stopped.

That ends here.

What I'm Actually Doing Now

I'm not launching a product today. I'm not announcing a startup.

What I am doing is this: I'm spending 3 days observing my own life every frustration, every "I wish there was something for this" moment and writing it down. No filtering. No immediately googling if it exists. Just raw observation.

Because the builders I respect Pieter Levels, Kumar Shah they didn't start with ideas. They started with problems they genuinely felt.

I want to find something I genuinely feel.

Why I'm Writing This Publicly

Two reasons.

One: Accountability. If I document this publicly, I can't quietly disappear when things get hard. You'll notice.

Two: I want to find my people.

Right now, I exist in an environment where nobody around me thinks like this. Not my classmates. Not my family. The conversations I want to have about building, about systems, about why certain companies win I can't have them in my daily life.

So I'm building that community here. One post at a time.

If you're someone who obsesses over founder stories, who reads about how Pinterest or Airbnb survived their early days, who thinks about product and distribution at 2am this blog is for you. And honestly, it's for me too.

What's Next

I don't have a clean answer to where this goes.

A year from now, I want someone to ask me "what did you build?" and have a real answer. Right now, I don't. And that gap between who I am and who I'm trying to become is exactly what this blog is about.

I'm going to document every step. Every idea. Every dead end. Every small win.

Follow along if that sounds interesting.

— bjumani

Builder. Observer. Work in progress.

1. Sofort-Triage & Abwehrmaßnahmen

SOC Incident Playbook: Vulnerability Remediation & Verification
Syntax validiert (0 Fehler)
title: Detect Exploitation - I'm a Younger Builder. I've Failed 4 Times. Here's why I'm Still Going.
id: bd4e6014-8edb-4419-b3a5-31bb21f6bc45
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-26
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
Syntax validiert (0 Fehler)
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-26"
        description = "YARA Signature for "
    strings:
        $str = "I\'m a Younger Builder. I\'ve Fa" ascii wide
    condition:
        any of them
}
Syntax validiert (0 Fehler)
index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("Im a Younger Builder Ive Failed 4 Times ")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count
Syntax validiert (0 Fehler)
message: "*Im a Younger Builder Ive Failed 4 Times *"
Syntax validiert (0 Fehler)
CommonSecurityLog
| where Message has "Im a Younger Builder Ive Failed 4 Times "
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

2. Cyber Threat Intelligence & Forensik

CTI Threat Relationship Graph2 Knoten / 1 Relationen
CVE / Incident Software MITRE ATT&CK CWE Weakness IoC
🎯
MITRE ATT&CK Matrix Navigator 14 Taktiken
Reconnaissance
-
Resource Development
-
Initial Access
Execution
Persistence
-
Privilege Escalation
Defense Evasion
Credential Access
-
Discovery
-
Lateral Movement
-
Collection
-
Command and Control
Exfiltration
-
Impact
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich I'm a Younger Builder. I've Failed 4 Tim.... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten I'm a Younger Builder. I've Failed 4 Times. Here's why I'm Still Going.

Thematisch verwandte Begriffe: Younger, Builder, Failed, Times · 6 Treffer

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

💬 Kommentare werden geladen…
Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-100620 | Capgo CLI (npm package @capgo/cli) through 7.98.2 is affected by an ove…
Advisory →
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag