<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Godand on Medium]]></title>
        <description><![CDATA[Stories by Godand on Medium]]></description>
        <link>https://medium.com/@Godand?source=rss-3c870041504c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Cxeugn70bsbpzrEn.jpg</url>
            <title>Stories by Godand on Medium</title>
            <link>https://medium.com/@Godand?source=rss-3c870041504c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:25:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Godand/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building a DDoS Detection Engine From Scratch — No Libraries, Just Basic Statistics]]></title>
            <link>https://medium.com/@Godand/i-built-a-real-time-ddos-detection-engine-from-scratch-heres-how-it-works-a825dbd69956?source=rss-3c870041504c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a825dbd69956</guid>
            <dc:creator><![CDATA[Godand]]></dc:creator>
            <pubDate>Tue, 28 Apr 2026 13:49:49 GMT</pubDate>
            <atom:updated>2026-04-30T22:12:14.785Z</atom:updated>
            <content:encoded><![CDATA[<p>A few months ago I got obsessed with a question: what would it actually take to build your own DDoS detection system from scratch — no Cloudflare, no Fail2Ban, no magic third-party library — just you, Python, and the Linux kernel?</p><p>I decided to find out. The result is a daemon that runs continuously alongside a web server, watches every incoming HTTP request, learns what normal traffic looks like, and automatically drops attackers at the firewall level within seconds of detection. It sends Slack alerts, unbans IPs on a progressive schedule, and serves a live metrics dashboard.</p><p>This post is the guide I wish I had when I started. I’ll explain every concept from first principles, show you the actual code with file references, and walk you through putting it all together. If you’ve never touched security tooling before, that’s fine — I’ll explain the math too.</p><h3>What Problem Are We Actually Solving?</h3><p>When you run a public web server, you’re exposed. At any moment, someone can point a bot army at your IP and flood you with thousands of requests per second. Your server spends all its resources responding to garbage traffic. Real users time out. Your app goes down.</p><p>The standard advice is “use Cloudflare” or “use Fail2Ban.” But those are black boxes. I wanted to understand the actual mechanics — how do you decide what’s an attack and what’s just a busy afternoon? How do you avoid banning legitimate users? How does the firewall actually drop packets?</p><p>The answer turns out to be statistics. Not machine learning, not signatures, not pattern matching — just a rolling mean, a standard deviation, and a z-score. Once I understood that, everything else was just plumbing.</p><h3>Architecture</h3><p>Before writing a single line of code, it helps to see how the pieces fit together:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c-P8nbmo6VaPputElrbzMA.png" /></figure><pre>Internet<br>    │<br>    ▼<br>Host Nginx (SSL/443)<br>    │  proxies to<br>    ▼<br>Docker Nginx (port 8080) ──── writes JSON logs ────▶ /var/log/nginx/hng-access.log<br>    │                                                         │ (shared Docker volume)<br>    ▼                                                         │<br>Nextcloud (port 80, internal)                                 ▼<br>                                                    Detector Daemon (Python)<br>                                                         │          │<br>                                                         ▼          ▼<br>                                                    iptables    Slack + Dashboard</pre><p>The key insight in this design: Nginx and the detector never talk to each other directly. Nginx writes to a log file. The detector reads that log file. They’re completely decoupled — you could swap either one out without touching the other.</p><h3>Project Structure</h3><p>Here’s the full folder layout before we build anything:</p><pre>project/<br>├── docker-compose.yml          # Spins up everything together<br>├── .env                        # Secrets and config (never commit this)<br>├── nginx/<br>│   └── nginx.conf              # JSON logging + reverse proxy config<br>├── detector/<br>│   ├── Dockerfile              # How to containerise the detector<br>│   ├── requirements.txt        # Python dependencies<br>│   ├── config.yaml             # All tunable thresholds in one place<br>│   ├── main.py                 # Entry point — wires all modules together<br>│   ├── monitor.py              # Tails and parses the Nginx access log<br>│   ├── baseline.py             # Rolling 30-min baseline (mean + stddev)<br>│   ├── detector.py             # Z-score and rate-multiplier anomaly checks<br>│   ├── blocker.py              # iptables DROP rule management<br>│   ├── unbanner.py             # Progressive backoff auto-unban scheduler<br>│   ├── notifier.py             # Slack webhook alerts<br>│   ├── dashboard.py            # Flask live metrics dashboard<br>│   └── audit.py                # Structured event log (ban/unban/recalc)<br>└── README.md</pre><p>One rule I followed throughout: <strong>every tunable number lives in </strong><strong>config.yaml</strong>. Not hardcoded in the Python files. This makes it easy to adjust thresholds without touching logic code.</p><h3>Step 1: Getting Nginx to Write JSON Logs</h3><p>The detector can only work if it has structured data to read. Nginx’s default log format is a human-readable string — great for reading, terrible for parsing in code. The first thing to do is switch it to JSON.</p><p><strong>nginx/nginx.conf</strong></p><pre># Define a JSON log format. escape=json handles special characters safely.<br>log_format json_log escape=json<br>    &#39;{&#39;<br>        &#39;&quot;timestamp&quot;:&quot;$time_iso8601&quot;,&#39;<br>        &#39;&quot;source_ip&quot;:&quot;$remote_addr&quot;,&#39;<br>        &#39;&quot;x_forwarded_for&quot;:&quot;$http_x_forwarded_for&quot;,&#39;<br>        &#39;&quot;method&quot;:&quot;$request_method&quot;,&#39;<br>        &#39;&quot;path&quot;:&quot;$request_uri&quot;,&#39;<br>        &#39;&quot;status&quot;:$status,&#39;<br>        &#39;&quot;response_size&quot;:$body_bytes_sent,&#39;<br>        &#39;&quot;request_time&quot;:$request_time&#39;<br>    &#39;}&#39;;<br># Write to the shared volume. buffer=4k flush=1s means lines hit disk within 1 second.<br>access_log /var/log/nginx/hng-access.log json_log buffer=4k flush=1s;</pre><p>The flush=1s part is important. Without it, Nginx buffers log lines in memory and writes them in batches. Your detector could be sitting there waiting while an attack is already underway.</p><p>Now each log line looks like this — one clean JSON object per request:</p><pre>{&quot;timestamp&quot;:&quot;2025-04-26T10:00:01+00:00&quot;,&quot;source_ip&quot;:&quot;1.2.3.4&quot;,&quot;method&quot;:&quot;GET&quot;,&quot;path&quot;:&quot;/&quot;,&quot;status&quot;:200,&quot;response_size&quot;:1234}</pre><h3>Step 2: The Log Monitor — Reading Lines as They Arrive</h3><p>monitor.py does one job: behave like tail -f in Python. It keeps the log file open and calls a callback function every time Nginx writes a new line.</p><p><strong>detector/monitor.py — </strong><strong>tail_log() function</strong></p><pre>def tail_log(log_file: str, callback) -&gt; None:<br>    # Wait for the file to exist — nginx might take a few seconds to create it<br>    while not os.path.exists(log_file):<br>        time.sleep(1)<br><br>    with open(log_file, &#39;r&#39;) as f:<br>        # seek(0, 2) = move to 0 bytes from the END of the file.<br>        # This skips all historical entries — we only want new traffic.<br>        f.seek(0, 2)<br><br>        while True:<br>            line = f.readline()<br><br>            if not line:<br>                # No new data yet. Sleep 50ms to avoid burning CPU in a busy loop.<br>                time.sleep(0.05)<br>                continue<br><br>            try:<br>                entry = json.loads(line.strip())<br>                callback(entry)  # hand the parsed dict to main.py<br>            except json.JSONDecodeError:<br>                pass  # skip malformed lines (e.g. partial writes during log rotation)</pre><p>The callback is process_log_entry from main.py — we&#39;ll get there. The key design decision here is that the monitor is dumb: it just parses and hands off. All the logic lives elsewhere.</p><h3>Step 3: The Baseline — Teaching the System What “Normal” Means</h3><p>This is the most important part of the whole system, and the part most people would get wrong by hardcoding a number.</p><p><strong>The problem with hardcoding:</strong> a threshold of “100 req/s = attack” is useless. For a busy e-commerce site, 100 req/s is a quiet Tuesday. For a personal server at 3am, it’s definitely an attack. The threshold needs to reflect <em>actual recent traffic</em>, not someone’s guess.</p><p><strong>The solution:</strong> a rolling 30-minute window of per-second request counts, from which we compute a live mean and standard deviation.</p><p><strong>detector/baseline.py — the core data structure</strong></p><pre># maxlen=1800 means the deque holds at most 1800 entries (30 min × 60 sec).<br># When it&#39;s full and you append, the oldest entry automatically falls off the left.<br>self.counts_window = deque(maxlen=1800)</pre><p>Every second, we flush the current second’s request count into this window:</p><pre># baseline.py — _flush_second()<br>def _flush_second(self, second, count, errors):<br>    self.counts_window.append(count)    # Also store in the current hour&#39;s slot<br>    hour = time.localtime(second).tm_hour<br>    if hour not in self.hourly_slots:<br>        self.hourly_slots[hour] = deque(maxlen=3600)<br>    self.hourly_slots[hour].append(count)</pre><p>Every 60 seconds, a background thread wakes up and recomputes the baseline:</p><p><strong>detector/baseline.py — </strong><strong>_recalculate()</strong></p><pre>def _recalculate(self):<br>    current_hour = time.localtime().tm_hour<br>    hour_data = self.hourly_slots.get(current_hour, deque())<br>    # Prefer the current hour&#39;s data if we have at least 5 minutes of it.<br>    # This stops a quiet 3am baseline from contaminating a busy 4am detection window.<br>    if len(hour_data) &gt;= 300:<br>        data = list(hour_data)<br>    else:<br>        data = list(self.counts_window)  # fall back to full 30-min window<br>    if len(data) &lt; 2:<br>        return  # not enough data yet<br>    mean   = statistics.mean(data)<br>    stddev = statistics.pstdev(data)<br>    # Apply floor values to prevent division by zero at low traffic periods<br>    self.effective_mean   = max(mean,   1.0)<br>    self.effective_stddev = max(stddev, 0.1)</pre><p>The hourly_slots dict is the clever bit. Traffic at midnight looks nothing like traffic at noon. Without it, the 30-minute window would mix data from both hours at the boundary and produce a baseline that doesn&#39;t represent either. By keeping separate buckets per hour, once the current hour has 5 minutes of data, we use it exclusively.</p><h3>Step 4: The Sliding Window — Measuring Current Rate</h3><p>The baseline tells us what normal looks like. Now we need to measure what <em>right now</em> looks like.</p><p>For every IP address, we maintain a deque of <strong>timestamps</strong> — one per request. This is the sliding window.</p><p><strong>detector/detector.py — data structures</strong></p><pre>from collections import deque, defaultdict<br># Each IP gets its own deque of timestamps<br>self._ip_windows     = defaultdict(deque)<br>self._ip_err_windows = defaultdict(deque)  # only 4xx/5xx timestamps<br># One global window across all IPs<br>self._global_window  = deque()</pre><p>Every time a request comes in, we append the timestamp and evict anything older than 60 seconds:</p><p><strong>detector/detector.py — </strong><strong>record() method</strong></p><pre>now       = time.time()<br>ip_cutoff = now - 60  # our 60-second window<br># Add the new timestamp<br>self._ip_windows[ip].append(now)<br># Evict old ones from the left (oldest end of the deque)<br>while self._ip_windows[ip] and self._ip_windows[ip][0] &lt; ip_cutoff:<br>    self._ip_windows[ip].popleft()<br># Rate = how many timestamps remain / window length<br>ip_rate = len(self._ip_windows[ip]) / 60</pre><p>Why deque and not a list?</p><p>list.pop(0) is O(n) — it has to shift every element left by one. If you have 10,000 entries during an attack, that&#39;s 10,000 memory operations per eviction, thousands of times per second. deque.popleft() is O(1) — constant time regardless of size. It&#39;s not a premature optimisation here; it&#39;s the reason the system stays responsive during the exact moment it&#39;s needed most.</p><h3>Step 5: Detection — Making a Decision</h3><p>Now we have everything we need:</p><ul><li>ip_rate — how fast this IP is requesting right now</li><li>effective_mean — average rate over the last 30 minutes</li><li>effective_stddev — how much normal traffic varies</li></ul><p>Two checks run on every request. Whichever fires first triggers the alert:</p><p><strong>detector/detector.py — anomaly checks</strong></p><pre>mean, stddev = self.baseline.get_baseline()<br># Check 1: Z-score<br># How many standard deviations above normal is this rate?<br>ip_zscore = (ip_rate - mean) / stddev if stddev &gt; 0 else 0.0<br># Check 2: Rate multiplier<br># Is this rate more than 5× the average regardless of stddev?<br>ip_anomalous = (ip_zscore &gt; 3.0) or (ip_rate &gt; 5.0 * mean and ip_rate &gt; 1.0)</pre><p><strong>Why two checks?</strong> The z-score is powerful but has a blind spot: if traffic is extremely flat and predictable (stddev is near zero), even a doubled rate produces a huge z-score. The rate multiplier catches cases where the math says “technically normal” but 5× the average is clearly wrong.</p><p><strong>Error surge — the third signal:</strong></p><p>Attackers often generate lots of 4xx errors. They’re probing for hidden endpoints, trying credentials, scanning for vulnerabilities. We track this separately:</p><pre># detector/detector.py<br>tightened = (error_mean &gt; 0 and ip_err_rate &gt;= 3.0 * error_mean)<br>if tightened:<br>    z_threshold = 3.0 * 0.7   # 30% tighter — suspicious IPs get less benefit of the doubt<br>    rate_mult   = 5.0 * 0.7</pre><h3>Step 6: Blocking with iptables</h3><p>When an IP is flagged, we need to stop it at the network level — not just refuse it at the application level. The difference matters: application-level rejection still uses server resources to process the request. iptables drops the packet in the kernel before it ever reaches your app.</p><p><strong>detector/blocker.py — </strong><strong>block() method</strong></p><pre>import subprocess<br><br>def block(self, ip: str) -&gt; bool:<br>    result = subprocess.run(<br>        [&#39;iptables&#39;, &#39;-I&#39;, &#39;INPUT&#39;, &#39;-s&#39;, ip, &#39;-j&#39;, &#39;DROP&#39;],<br>        capture_output=True,<br>        timeout=5<br>    )<br>    if result.returncode == 0:<br>        self._blocked[ip] = time.time()<br>        return True<br>    return False</pre><p>Breaking down the iptables command:</p><pre>iptables  -I      INPUT    -s   1.2.3.4   -j   DROP<br>   │       │        │       │      │        │     │<br>   │    Insert    Chain  Source  The IP   Jump  Action:<br>   │    at top                           to    silently<br>firewall                                        discard</pre><p>-I (insert) vs -A (append) matters. -A adds the rule at the bottom of the chain — every packet still has to be checked against all preceding rules first. -I puts it at the top so the DROP fires immediately. During an attack with 10,000 packets per second, this is the difference between the rule being effective and being too slow.</p><p>To unban:</p><p><strong>detector/blocker.py — </strong><strong>unblock() method</strong></p><pre>subprocess.run(<br>    [&#39;iptables&#39;, &#39;-D&#39;, &#39;INPUT&#39;, &#39;-s&#39;, ip, &#39;-j&#39;, &#39;DROP&#39;]<br>)</pre><p>-D deletes that specific rule. Everything else stays intact.</p><h3>Step 7: Auto-Unban with Progressive Backoff</h3><p>Permanent bans on the first offence are too harsh. The attacker might be a misconfigured app, a scraper that got aggressive, or a legitimate user’s browser that went haywire. Progressive backoff gives grace to accidents while escalating punishment for repeat offenders.</p><p><strong>detector/unbanner.py — schedule</strong></p><pre># From config.yaml: [600, 1800, 7200] seconds<br># 1st ban → 10 minutes<br># 2nd ban → 30 minutes  <br># 3rd ban → 2 hours<br># 4th ban → permanent (no entry in the list)def schedule_unban(self, ip: str):<br>    count    = self._ban_counts.get(ip, 0)<br>    if count &gt;= len(self._schedule):<br>        return None  # permanent — no unban scheduled    duration           = self._schedule[count]<br>    self._pending[ip]  = time.time() + duration<br>    self._ban_counts[ip] = count + 1<br>    return duration</pre><p>A single background thread handles all unbanning. It wakes every 10 seconds and processes whoever is overdue:</p><p><strong>detector/unbanner.py — </strong><strong>_scheduler_loop()</strong></p><pre>def _scheduler_loop(self):<br>    while True:<br>        time.sleep(10)<br>        now = time.time()<br>        due = [ip for ip, t in self._pending.items() if now &gt;= t]        for ip in due:<br>            self._blocker.unblock(ip)<br>            self._detector.unflag_ip(ip)  # allow re-detection if they reoffend<br>            del self._pending[ip]<br>            self._on_unban(ip, self._ban_counts.get(ip, 1))</pre><p>Running one loop instead of spawning a separate timer thread per IP is intentional. During an attack where you’ve banned 500 IPs, you don’t want 500 threads sleeping simultaneously.</p><h3>Step 8: Slack Alerts</h3><p>Every meaningful event — ban, unban, global anomaly — sends a Slack message. The webhook URL lives in config.yaml and can be overridden by the SLACK_WEBHOOK_URL environment variable (so you&#39;re not committing secrets to git).</p><p><strong>detector/notifier.py — </strong><strong>send_ban_alert()</strong></p><pre>def send_ban_alert(self, ip, rate, mean, stddev, condition, duration_seconds):<br>    duration_str = f&quot;{duration_seconds // 60} minutes&quot; if duration_seconds else &quot;PERMANENT&quot;    msg = (<br>        f&quot;:rotating_light: *IP BANNED*\n&quot;<br>        f&quot;&gt;*IP:* `{ip}`\n&quot;<br>        f&quot;&gt;*Condition:* {condition}\n&quot;<br>        f&quot;&gt;*Current Rate:* `{rate:.3f} req/s`\n&quot;<br>        f&quot;&gt;*Baseline:* mean=`{mean:.3f}` stddev=`{stddev:.3f}`\n&quot;<br>        f&quot;&gt;*Ban Duration:* {duration_str}&quot;<br>    )<br>    requests.post(self._url, json={&quot;text&quot;: msg}, timeout=5)</pre><p>The alert always includes: what fired, the current rate, the baseline it was compared against, and how long the ban lasts. That’s everything you need to decide whether to investigate or ignore it.</p><h3>Step 9: Tying It All Together in main.py</h3><p>This is where everything gets wired up. main.py creates each component and connects them through callbacks — functions that one module calls when something happens, triggering action in another module.</p><p><strong>detector/main.py — full wiring</strong></p><pre># 1. Create components<br>audit    = AuditLogger(config[&#39;audit_log_file&#39;])<br>baseline = BaselineTracker(config, on_recalc=lambda m, s, n, sl: audit.log_baseline_recalc(m, s, n, sl))<br>blocker  = IPBlocker()<br>notifier = SlackNotifier(config[&#39;slack_webhook_url&#39;])# 2. Define what happens when each event fires<br>def on_ip_anomaly(ip, rate, mean, stddev, condition):<br>    blocked  = blocker.block(ip)              # add iptables rule<br>    if not blocked:<br>        return<br>    duration = unbanner.schedule_unban(ip)    # schedule auto-release<br>    notifier.send_ban_alert(...)              # ping Slack<br>    audit.log_ban(...)                        # write to audit logdef on_global_anomaly(rate, mean, stddev, condition):<br>    notifier.send_global_alert(...)           # Slack only — no IP to bandef on_unban(ip, ban_count):<br>    notifier.send_unban_alert(ip, ban_count)  # notify Slack<br>    audit.log_unban(ip, ban_count)# 3. Create detector and unbanner (they need the callbacks above)<br>detector = AnomalyDetector(config, baseline, on_ip_anomaly, on_global_anomaly)<br>unbanner = UnbanScheduler(config, blocker, detector, on_unban)# 4. This runs on every log line<br>def process_log_entry(entry):<br>    ip       = parse_source_ip(entry)<br>    is_error = int(entry.get(&#39;status&#39;, 200)) &gt;= 400    baseline.record_request(is_error=is_error)  # update the rolling window<br>    detector.record(ip, is_error=is_error)       # check for anomalies# 5. Start background threads<br>threading.Thread(target=tail_log, args=(log_file, process_log_entry), daemon=True).start()<br>threading.Thread(target=run_dashboard, args=(detector, baseline, blocker, unbanner, 8888), daemon=True).start()</pre><p>Read this top to bottom and the whole system becomes clear. A log line comes in → baseline gets updated → detector checks thresholds → if anomalous, blocker fires → unbanner schedules release → Slack gets notified → audit log gets written. Every module does one thing. main.py just connects them.</p><h3>Running It Yourself</h3><p><strong>Prerequisites:</strong> A Linux VPS (Ubuntu 22.04 recommended), Docker, Docker Compose, a Slack workspace with an incoming webhook URL.</p><p><strong>1. Clone and configure</strong></p><pre>git clone https://github.com/Godhanded/HNG14.git<br>cd HNG14/Stage3/Devops<br>cp .env.example .env<br>nano .env  # fill in your VPS IP, DB passwords, and Slack webhook</pre><p><strong>2. Launch the stack</strong></p><pre>docker-compose up -d --build</pre><p>This starts four containers: MariaDB, Nextcloud, Nginx, and the detector. The HNG-nginx-logs volume is created automatically — Nginx writes to it, the detector reads from it.</p><p><strong>3. Verify everything is up</strong></p><pre>docker-compose ps<br># All four services should show &quot;Up&quot;<br>curl http://localhost:8888/health<br># {&quot;status&quot;: &quot;ok&quot;, ...}</pre><p><strong>4. Watch the detector live</strong></p><pre>docker logs -f devops-detector-1</pre><p>You’ll see the heartbeat every 60 seconds and any anomaly events as they fire.</p><p><strong>5. Test it</strong></p><p>From a separate machine, send a burst of traffic:</p><pre>ab -n 2000 -c 100 http://YOUR_VPS_IP:8080/</pre><p>Within seconds you should see an anomaly line in the detector logs, an iptables rule appear (sudo iptables -L -n), and a Slack message hit your channel.</p><h3>What I Realized While Building This</h3><p>The thing that surprised me most: this isn’t really a security problem. It’s a statistics problem dressed up as a security problem. Once I framed it that way — “is this value statistically unusual?” — the right tools became obvious. Mean, standard deviation, z-score. Three numbers that have been around for over a century, applied to server logs.</p><p>The second thing: <strong>don’t hardcode thresholds</strong>. What looks like an attack at 3am is normal traffic at noon. The system has to learn from its own history. Anything you hardcode is a lie you’re telling yourself about how your traffic behaves.</p><p>The architecture pattern here — write structured logs, have a separate process read them — is genuinely useful beyond security tooling. It’s how most observability systems work. Learning it here means you’ll recognise it everywhere.</p><p><strong>Full source code:</strong> <a href="https://github.com/Godhanded/HNG14/tree/main/Stage3/Devops">https://github.com/Godhanded/HNG14/tree/main/Stage3/Devops</a></p><p><strong>Live dashboard:</strong> <a href="https://godand.duckdns.org/">https://godand.duckdns.org</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a825dbd69956" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The SDR’s Secret Weapon: Unlocking Success with Top Marketing Specialists]]></title>
            <link>https://medium.com/@Godand/the-sdrs-secret-weapon-unlocking-success-with-top-marketing-specialists-f2835e9ec1c1?source=rss-3c870041504c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2835e9ec1c1</guid>
            <dc:creator><![CDATA[Godand]]></dc:creator>
            <pubDate>Wed, 29 Jan 2025 13:35:52 GMT</pubDate>
            <atom:updated>2025-01-29T13:38:27.605Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A diverse group of professionals collaborating around a digital dashboard, featuring data visualizations and subtle HNG branding" src="https://cdn-images-1.medium.com/max/1024/1*ARHr9MpaNAFEdLwI5NoA_g.jpeg" /><figcaption>A diverse group of professionals collaborating around a digital dashboard, featuring data visualizations and subtle branding</figcaption></figure><p>In today’s competitive sales landscape, Sales Development Representatives (SDRs) are constantly battling to capture prospects’ attention. Yet, 65% of SDRs report challenges in aligning their outreach with broader marketing strategies, while 72% struggle with maintaining team morale in high-pressure environments (Source: 2023 Sales Efficiency Report). The modern consumer is flooded with marketing messages, making it harder than ever to stand out. To succeed, SDRs must go beyond cold calls and emails — they need strong marketing support to drive engagement and warm up leads before they even reach a sales call.</p><p>That’s where hiring the right marketing professionals makes all the difference. Whether it’s an SEO expert driving organic traffic or a brand-building specialist crafting compelling narratives, a skilled team behind the scenes can amplify an SDR’s efforts. Fortunately, platforms like <strong>HNG Hire</strong> make it easy to connect with world-class marketing specialists who can help SDRs increase conversions and boost pipeline growth.</p><h3>The Role of Marketing in SDR Success</h3><p>SDRs are at the forefront of business growth, identifying and qualifying leads for account executives. However, without a strong marketing strategy supporting them, their outreach efforts can fall flat. Here are some key marketing functions that empower SDRs:</p><ul><li><strong>SEO Optimization</strong>: Driving organic traffic to product pages or lead magnets makes it easier for SDRs to follow up with interested prospects.</li><li><strong>Brand Building</strong>: Creating a strong, trustworthy brand identity makes it easier for SDRs to engage potential customers.</li><li><strong>Content Strategy</strong>: Engaging content nurtures leads and answers common objections before SDRs even reach out.</li><li><strong>Email Marketing</strong>: Automated yet personalized email sequences improve response rates and warm up leads.</li><li><strong>Digital Advertising</strong>: Paid marketing campaigns ensure SDRs have access to highly targeted leads, maximizing efficiency.</li><li><strong>Social Media Engagement</strong>: Consistently engaging with an audience through LinkedIn and other platforms keeps a brand top-of-mind.</li></ul><p>Investing in specialists for these areas creates a smoother journey for potential customers, allowing SDRs to work smarter rather than harder.</p><h3>Supercharge Outreach with a Brand Building Specialist</h3><p>One of the biggest challenges for SDRs is making a memorable impression on potential customers. A <a href="https://hng.tech/hire/brand-building-specialists"><strong>Brand Building Specialist</strong></a> helps companies create compelling narratives that enhance trust and recognition in their industry.</p><p>Imagine an SDR reaching out to a prospect who has already interacted with a company’s thought leadership content, social media presence, or case studies. The conversation is no longer cold — it’s informed and meaningful. A strong brand presence built by an expert makes it easier for SDRs to generate interest and close more deals.</p><p>A brand-building expert also ensures that the messaging SDRs use is cohesive and aligns with the company’s overall strategy. When SDRs can rely on a well-crafted brand identity, they experience higher engagement rates and more productive conversations.</p><p>Platforms like <strong>HNG Hire</strong> allow businesses to connect with top-tier brand strategists who can position a company as an industry leader, ensuring SDRs have a solid foundation for their outreach efforts.</p><h3>Driving More Sales with a Digital Marketing Specialist</h3><p>Another crucial way to enhance SDR effectiveness is by investing in <a href="https://hng.tech/hire/digital-marketing-specialists"><strong>Digital Marketing Specialists</strong></a>. These experts handle everything from paid ad campaigns to multi-channel engagement, ensuring SDRs always have a fresh supply of high-quality leads.</p><p>Misalignment between sales and marketing costs companies up to 10% in annual revenue (HubSpot, 2023). SDRs thrive when strategies are unified, which is why collaborating with a <strong>Marketing Strategist</strong> is non-negotiable.</p><p>A well-targeted digital marketing strategy brings the right audience directly to a company, allowing SDRs to focus on interested prospects instead of cold calling lists. More engaged leads mean higher response rates, shorter sales cycles, and increased conversion potential.</p><p>Digital marketing specialists leverage data analytics to optimize campaigns in real-time, ensuring that marketing budgets are spent efficiently. They also implement retargeting strategies, ensuring SDRs don’t lose potential customers who showed initial interest but didn’t convert immediately.</p><p><em>Lately</em>: A tech startup saw a 40% increase in SQLs (sales-qualified leads) after hiring a HNG Digital Marketing Specialist to revamp their LinkedIn ad strategy.</p><p>By leveraging the expertise of digital marketing professionals from <strong>HNG Hire</strong>, businesses ensure SDRs have a steady pipeline of potential customers who are already interested in their services.</p><h3>Integrating SDR Efforts with Innovative Communication Tools</h3><p>Beyond hiring marketing experts, integrating the right tools can significantly enhance SDR efficiency. Two powerful solutions built by hires from <strong>HNG Hire</strong> for streamlined communication and prospect engagement are <a href="https://telex.im/"><strong>Telex.im</strong></a> and <a href="https://delve.fun/"><strong>Delve.fun</strong></a>.</p><ul><li><strong>Telex.im</strong>: An innovative messaging platform designed for seamless business communication, enabling SDRs to interact with leads instantly and efficiently.</li><li><strong>Delve.fun</strong>: A research and analytics tool that helps teams uncover deeper insights into target markets, allowing for more informed prospecting and engagement strategies.</li></ul><p>Using data-backed insights from <strong>Delve.fun</strong>, SDRs can personalize their outreach more effectively. Meanwhile, <strong>Telex.im</strong> allows SDRs to manage conversations without delays, improving response times and increasing engagement levels</p><h3>Elevate Your SDR Team with Expert Marketing Support</h3><p>SDRs don’t have to go it alone. By hiring specialists in brand building and digital marketing, companies create an environment where leads are nurtured even before outreach begins. The result? SDRs spend less time chasing uninterested prospects and more time closing deals.</p><p>Platforms like <a href="https://hng.tech/hire/brand-building-specialists"><strong>HNG Hire</strong></a> simplify the process of finding top-tier marketing professionals. Combined with cutting-edge tools from them like <a href="https://telex.im/"><strong>Telex.im</strong></a> and <a href="https://delve.fun/"><strong>Delve.fun</strong></a>, SDR teams can operate at peak efficiency, achieving outstanding sales outcomes.</p><p>Invest in expert marketing support today and watch your SDR team’s results skyrocket!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2835e9ec1c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beginner? Setting Up Your Solution For Tests In Visual Studio And Setting Sights On HNG]]></title>
            <link>https://medium.com/@Godand/beginner-setting-up-your-solution-for-tests-in-visual-studio-and-setting-sights-on-hng-4f81f2c08e0b?source=rss-3c870041504c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f81f2c08e0b</guid>
            <dc:creator><![CDATA[Godand]]></dc:creator>
            <pubDate>Fri, 28 Jun 2024 19:46:43 GMT</pubDate>
            <atom:updated>2024-06-29T17:31:13.547Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been in the software space for a while now with my focus on blockchain and backend web development predominantly with Python and the Flask framework as my main tools. One thing that’s bothered me a lot was having to learn something completely new or different whenever the platform I’m building on changes, why cant I just learn one thing and iterate on it or just reuse it on at least most of the platforms I’d work with. The I discover the .Net Ecosystem and I’m wowed! Just what I was looking for, It provides a truly mature, robust framework for software development.</p><p>HNG is a your accountability partner when learning new tech, I’d talk about them in detail at the end.</p><p>https://hng.tech/premium</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*lQ2mawcmkMseo3fH" /><figcaption><a href="https://imgs.search.brave.com/aEb7kdUAOKUYD8ziqx8-l9J95C9uBf1IzWZV5-nfG5M/rs:fit:860:0:0:0/g:ce/aHR0cHM6Ly9sZWFy/bi5taWNyb3NvZnQu/Y29tL2VuLXVzL3Zp/c3VhbHN0dWRpby90/ZXN0L21lZGlhL3Zz/LTIwMjIvc3RhcnQt/bGl2ZS11bml0LXRl/c3RpbmcucG5nP3Zp/ZXc9dnMtMjAyMg">https://imgs.search.brave.com/aEb7kdUAOKUYD8ziqx8-l9J95C9uBf1IzWZV5-nfG5M/rs:fit:860:0:0:0/g:ce/aHR0cHM6Ly9sZWFy/bi5taWNyb3NvZnQu/Y29tL2VuLXVzL3Zp/c3VhbHN0dWRpby90/ZXN0L21lZGlhL3Zz/LTIwMjIvc3RhcnQt/bGl2ZS11bml0LXRl/c3RpbmcucG5nP3Zp/ZXc9dnMtMjAyMg</a></figcaption></figure><p>Setting up Visual studio for test driven devekopment(TDD) can be a bit overwhelming when you just start using it, The truth is once you get it once, it just gets sooo easy. So Today lets walk through a typical Problem a newbie might experience when using visual studio especially coming from other frameworks and IDEs that are not as mature as .NET and Visual studio.</p><p>Say you’ve built you’ve created your solution, added a project into it and built it, all seems great now its time to write tests, coming from other not so mature IDEs it might be a bit confusing, you see everything comes built in with Visual Studio so you don’t need a lot to get started with your tests, here&#39;s a step by step guide:</p><ol><li>To get started, right-click on the solution and choose Add New Project. In the dialog box, use the dropdown to pick UnitTest, then select xUnit Test Project.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*bBcywH1uw-B8CNC6euPUFg.png" /></figure><ul><li>Click Next and fill in the name and location of your new project. Typically, the name will be the name of the solution followed by .Tests.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/555/1*Cz__ghFDNBWri7YvDiTYXQ.png" /></figure><ul><li>Click next and select your .NET Platform</li></ul><p><strong>2. Setting the project reference:</strong></p><p>So you’ve created your test project but this is a completely separate project from the one I want to unit test, how do i access the project to test? To do that we need to add a project reference, so from our test project we will reference our main projects, now you can access the main project from the test project, here&#39;s how.</p><ul><li>right-click on the test project and select Add | ProjectReference, and check the box next to the name of your main project</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/405/1*Ho96M2xZ4DG6BXzpyRcqqA.png" /></figure><p>With all that set up, we are ready to write our first unit test, the testing structure is in place and working.</p><p><strong>3. Creating the first unit test:</strong></p><p>To make sure all is right , open UnitTest1.cs file that was created when you added the test project and add a test method that must pass.</p><pre>namespace SolutionName.Tests<br>{<br> public class UnitTest1<br> {<br>     [Fact]<br>     public void MustBeTrue()<br>     {<br>       Assert.True(true);<br>     }<br>  }<br>}</pre><p>xUnit tests comes in two types:</p><ul><li>Facts: These are invariants — they always take the same data and should always pass</li><li>Theories: These are a suite of tests that execute the same code but are given different input arguments.</li></ul><p>Let’s examine our code:</p><ul><li>The first test we created, MustBeTrue, simply asserts that the value true is true. This makes a good first test, as it will test that your unit testing is set up correctly.</li></ul><p>4. <strong>Running the test:</strong></p><ul><li>go to the menu and select Test | Test Explorer</li><li>Click the green Play button to run all your tests.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/277/1*LIP0UEaA7OhcDIdu-UneEQ.png" /></figure><ul><li>Your project will build and Test Explorer will run your tests.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*lUQbD2Cnfh0ro1-o3WNyEw.png" /></figure><p><strong>My HNG Internship Adventure:</strong></p><p>So that was a brief summary but where does HNG come into the picture? you clearly mentioned it in the title, didn’t you? Yes! take a look <a href="https://hng.tech/premium">https://hng.tech/premium</a></p><p>HNG is the best place learn by building, HNG is a company that works with those who wish to be or already are the very best in tech to help them enhance their skills through their internship program and build their network. They also work with clients to find them the best technical talent across the globe.</p><p>I could watch all the YouTube tutorials, read all the .NET tutorial books and documentation but we all know that’s nothing compared to actually building and shipping a real world project, HNG always provides for me an environment that fast tracks my learning, They’d give me real projects and deadlines with penalties for not meeting these deadlines, the environment is competitive and is fast paced, you’d be surprised just how much your brain understands and learns when its under pressure. I look forward to the journey ahead and might give a feed back after 8 weeks once the internship is done on just how much of .NET I’ve become comfortable with. This internship will be my springboard into the world of mobile development. I’m eager to learn, grow, and contribute my skills.</p><p>You’d probably want to know more about what exactly HNG is and how to get started id leave some links here just in case.<br><a href="https://hng.tech/internship">https://hng.tech/internship</a> , <a href="https://hng.tech/hire">https://hng.tech/hire</a>, <a href="https://hng.tech/premium">https://hng.tech/premium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f81f2c08e0b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decided to Learn .NET Maui: My Journey into Mobile Development with HNG]]></title>
            <link>https://medium.com/@Godand/decided-to-learn-net-maui-my-journey-into-mobile-development-with-hng-a1546ec9ab7e?source=rss-3c870041504c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1546ec9ab7e</guid>
            <dc:creator><![CDATA[Godand]]></dc:creator>
            <pubDate>Fri, 28 Jun 2024 18:07:27 GMT</pubDate>
            <atom:updated>2024-06-28T18:16:59.864Z</atom:updated>
            <content:encoded><![CDATA[<h3>Decided to Learn .NET Maui: My Journey into Mobile Development with HNG</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZkXRS4wzlj6Z-Z3v.png" /><figcaption><a href="https://cdn.prod.website-files.com/645b9abe6a218233e4ac7428/65798c3510a2213cb6367acb_maui-hero.png">https://cdn.prod.website-files.com/645b9abe6a218233e4ac7428/65798c3510a2213cb6367acb_maui-hero.png</a></figcaption></figure><p>I’ve been in the software space for a while now with my focus on blockchain and backend web development predominantly with Python and the Flask framework as my main tools. One thing that&#39;s bothered me a lot was having to learn something completely new or different whenever the platform I&#39;m building on changes, why cant i just learn one thing and iterate on it or just reuse it on at least most of the platforms I&#39;d work with. The I discover the Net Ecosystem and I&#39;m wowed! Just what I was looking for, while trying to pick it up I decided I might as well pick up mobile on the way especially because .NET Maui promised native-cross platform development from a single code base, Cant be that hard right?</p><p><strong>The Playground: Mobile Development Platforms:</strong></p><p>Such a big word! its basically the approach used for building mobile applications, so <strong>tools and resources to streamline the development process.</strong> broadly divided into;</p><ul><li><strong>Native Development:</strong> A separate codebase is required for each operating system e.g.. XCode for iOS and Android Studio for Android. This offers the best performance and user experience tailored to each platform. <strong><em>Pros</em></strong>: access to all native features. <strong><em>Cons</em></strong>: Requires more development time and resources (separate codebases).</li><li><strong>Cross-Platform Development:</strong> here the app is built with a single code base that works on both platforms (Android and iOS). Popular examples are React Native, Flutter, Xamarine, .NET Maui. This saves development time but might have slight performance drawbacks when compared to native apps. <strong><em>Pros</em></strong>: saves resources, easier maintenance. <strong><em>Cons</em></strong>: Potential performance limitations, might not fully utilize platform-specific features.</li></ul><p>There&#39;s no right or wrong choice between them, you just have to put a few things into consideration when building an app to make a choice, such as;</p><ul><li>Your app’s complexity: For highly complex apps, native development might be better suited. For simpler apps, cross-platform can be efficient.</li><li>Your app’s Performance: If top-tier performance is crucial, native development might be preferred.</li><li>Your Budget and resources: Cross-platform development can be faster and more cost-effective.</li></ul><p><strong>The Architecture: Blueprints for Building Apps:</strong></p><p>Now, let’s talk about the software architecture patterns that organize how our app functions. Another big word, This is basically how files and folders should be arranged or put together when building a mobile app. The point for this is to promote code maintainability, scalability, and enable easier collaboration.</p><p>Here are the big three:</p><p><strong>Model-View-Controller (MVC):</strong> Separates the app into three parts: <em>Model</em>: Handles data and business logic. <em>View</em>: Represents the user interface (UI). <em>Controller</em>: Mediates between Model and View, processing user interactions.</p><ul><li><strong>Pros:</strong> Simple to understand, easy to implement.</li><li><strong>Cons:</strong> Tightly coupled code, complex UI updates.</li></ul><p><strong>Model-View-Presenter (MVP):</strong> This is similar to MVC, but the Presenter manages the View, making it more testable and decoupled.</p><ul><li><strong>Pros:</strong> Improved code separation, easier testing.</li><li><strong>Cons:</strong> More complex architecture, additional layer to manage.</li></ul><p><strong>Model-View-ViewModel (MVVM): </strong>This Architecture<strong> </strong>is<strong> o</strong>ften used with cross-platform frameworks(e.g .NET Maui). A ViewModel is introduced that acts as a data source for the View and handles communication with the Model.</p><ul><li><strong>Pros:</strong> Best separation of concerns, simplifies UI development.</li><li><strong>Cons:</strong> Steeper learning curve, might be overkill for simple apps.</li></ul><p>The choice mostly depends on your app’s complexity and your development preferences.</p><p><strong>My HNG Internship Adventure:</strong></p><p>So that was a brief summary but where does HNG come into the picture? you clearly mentioned it in the title, didn&#39;t you? Yes! take a look <a href="https://hng.tech/premium">https://hng.tech/premium</a></p><p>HNG is the best place learn by building, HNG is a company that works with those who wish to be or already are the very best in tech to help them enhance their skills through their internship program and build their network. They also work with clients to find them the best technical talent across the globe.</p><p>I could watch all the youtube tutorials, read all the .NET Maui books from Packt but we all know that&#39;s nothing compared to actually building and shipping a real world project, HNG always provides for me environment that fast tracks my learning, They’d give me real projects and deadlines with penalties for not meeting these deadlines, the environment is competitive and is fast paced, you’d be surprised just how much your brain understands and learns when its under pressure. I look forward to the journey ahead and might give a feed back after 8 weeks once the internship is done on just how much of .NET Maui I&#39;ve become comfortable with. This internship will be my springboard into the world of mobile development. I’m eager to learn, grow, and contribute my skills.</p><p>You’d probably want to know more about what exactly HNG is and how to get started id leave some links here just in case.<br> <a href="https://hng.tech/internship">https://hng.tech/internship</a> , <a href="https://hng.tech/hire">https://hng.tech/hire</a>, <a href="https://hng.tech/premium">https://hng.tech/premium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1546ec9ab7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web 2.0 Web 3.0, The one I’d pick!]]></title>
            <link>https://medium.com/@Godand/web-2-0-web-3-0-the-one-id-pick-cecf9961f9da?source=rss-3c870041504c------2</link>
            <guid isPermaLink="false">https://medium.com/p/cecf9961f9da</guid>
            <category><![CDATA[metaverse]]></category>
            <category><![CDATA[zuri-training]]></category>
            <category><![CDATA[web2]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Godand]]></dc:creator>
            <pubDate>Tue, 08 Mar 2022 02:00:22 GMT</pubDate>
            <atom:updated>2022-03-11T22:17:59.886Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*XPnzYhOfnTjBaaVF.jpg" /><figcaption>Image source: <a href="https://dev.to/lokky19/disparity-of-web-20-and-web-30-116a">https://dev.to/lokky19/disparity-of-web-20-and-web-30-116a</a></figcaption></figure><p>As someone as enthusiastic as I am especially in the area of technology, I cannot help but appreciate these two versions of the web, the powerful functions of web2.0 for instance the social media, micro blogging and networking sites like; Facebook, Clubhouse, Quora. It has never been so easy to interact with resources and other people on the web, I can share my thought and opinions so easily and everyone can see it. The mind boggling concept of a Semantic web where my searches are understood by robots, making research so much easier, a network where the number of machines on it exceeds that of Humans by a whopping 10:1 as expected in the web3.0. Truly great technologies the both of them are but I wonder what makes them different, lets find out!</p><p>Web 2.0 is referred to as the social web and is the current state of the Internet you and I are using right now, We can think of web3.0 as its next iteration. Before Web2.0 surfing the web1.0 internet meant going through a lot of ugly static web pages, you could do nothing other than just consume information that was all, Web2.0 solved this issue, it allowed interaction with these webpages and improvement in their designs through web development languages like HTML, CSS and JAVASCRIPT(DOM: Document object Model ). One of the key Innovations that drove Web2.0 where social networks, it enabled people create their own blog content, the problem here is that all user data is stored or harvested by companies providing this service this causes a major breach of privacy as some of these data are sold to third parties.Web3.0 on the other hand eliminates the need for these companies and allows users decide what data they want to make public, this is achieved through decentralized networks. Web3.0 is Trustless and Permissionless, meaning we can interact without permission from a trusted intermediary or governing body as in the case of Web2.0. applications in web3.0 run on decentralized peer to peer networks hence Dapps, unlike Web2.0 that runs web applications hosted by a single entity, giving them power over you and your data. Web3.0 promises greater connectivity than Web2.0 as even machines would be able to communicate with it and its Dapps. Web2.0 offers 2dimensional experience while the Web3.0 offers a 3Dimensional one through technologies such as virtual and augmented reality giving users full emersion experience. Web3.0 doesn’t come without its own dark sides, a major concern would be the lack of governance or rules, giving too much freedom for unhealthy practices such as hate crimes, illegal transactions , harassment and so on. all these would go unpoliced, unlike in web2.0 where such practices are policed.</p><p>For now Web3.0 is in its infancy and can be considered as an idea for a new Iteration of Web2.0. it took years to fully transition from web1.0 to Web2.0, so I expect the same for the finalization and adoption of Web3.0 and its short comings addressed. Personally Web3.0 sounds really cool and I cant wait for it. (I’m tired of making a random searching about clothes and two minutes later seeing an Ad that says, “the best places to buy the best clothes at the best prices”).</p><p>Don’t forget to give a clap and drop a comment bellow if you enjoyed this write-up.</p><p>A thank you to blockgames, Nestcoin and zuri teams efforts for empowering youths through blockchain. pay their sites a visit!</p><ul><li><a href="https://blockgames.gg/">Blockgames</a></li><li><a href="https://nestcoin.com/">Nestcoin | Unlock Wealth with Crypto</a></li><li><a href="https://zuri.team/">ZURI | Learn, Build, Grow.</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cecf9961f9da" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>