<?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 Oğuzhan Tursun on Medium]]></title>
        <description><![CDATA[Stories by Oğuzhan Tursun on Medium]]></description>
        <link>https://medium.com/@oguzhantursun?source=rss-4ba222987a0d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*PHsRWFs4jyisNkoJ5vLJmA.png</url>
            <title>Stories by Oğuzhan Tursun on Medium</title>
            <link>https://medium.com/@oguzhantursun?source=rss-4ba222987a0d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:07:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@oguzhantursun/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[Your Startup’s Security Shouldn’t Depend on Good Intentions]]></title>
            <link>https://oguzhantursun.medium.com/your-startups-security-shouldn-t-depend-on-good-intentions-bdf05bd9efad?source=rss-4ba222987a0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdf05bd9efad</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Oğuzhan Tursun]]></dc:creator>
            <pubDate>Tue, 29 Apr 2025 08:01:33 GMT</pubDate>
            <atom:updated>2025-04-29T08:01:33.808Z</atom:updated>
            <content:encoded><![CDATA[<p>Good intentions won’t prevent disaster. Explore how real companies protect themselves against mistakes, accidents, and insider threats.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cADmkzxNk6y-fmhZN83RTg.png" /></figure><blockquote>Imagine waking up to find your startup’s database wiped clean overnight.<br>No error. No hacker. Just one developer — frustrated, reckless, or worse.</blockquote><p>We’ve all shipped code past midnight under pressure — a single slip can erase millions in value. Good intentions alone won’t build a secure system — and in tech, that difference can kill your company.</p><h3><strong>Developers’ Good Intentions Are Not Enough</strong></h3><p>No one sets out to break a system they believe in.</p><blockquote>Case in point: <a href="https://aws.amazon.com/message/41926/">on February 28, 2017, a routine debugging command misconfigured by an engineer brought down a significant portion of the internet by crippling Amazon S3’s us-east-1 region.</a></blockquote><p>Good intentions matter. Secure systems require more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/0*n3wCtyXo7w9SA33K.gif" /></figure><h4>Accidents Happen — Even with Good People</h4><p>Even the most skilled and well-intentioned developers make mistakes.</p><p>A misplaced semicolon in a database migration script can wipe critical tables.<br>A misconfigured security rule can leave an entire server exposed to the public internet.<br>A rushed deployment late at night can push incomplete, vulnerable code into production.</p><p>These accidents aren’t signs of bad people — they’re part of being human.<br>That’s why secure systems are designed not to eliminate mistakes, but to contain and minimize their impact.</p><h4>Negligence Amplifies Risk</h4><p>Accidents are inevitable, but negligence makes them catastrophic.</p><p>In one infamous incident, check the <a href="https://www.strongdm.com/what-is/equifax-data-breach">Equifax Data Breach (2017)</a>.</p><p>When deadlines loom, developers might bypass critical steps — skipping code reviews, disabling security checks, pushing incomplete features into production.</p><p>Small shortcuts taken under pressure often open big vulnerabilities.</p><p>In many cases, it’s not malicious intent but simple haste or fatigue that leaves systems exposed.<br>Without strong processes and safeguards, even a tiny oversight can escalate into a disaster far greater than the original mistake.</p><blockquote>For a practical blueprint on strict environment separation, see StrongDM’s <a href="https://www.strongdm.com/zero-trust">Zero Trust Security Guide</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*Z7qDWSl8tDrvdy3k.gif" /></figure><h4>Malicious Intent Is Rare — But Devastating</h4><p>Most developers join your team because they believe in your mission and want to build something great.</p><p>Yet even the slightest opportunity can be exploited. Imagine a platform with its own virtual currency: a single line of SQL injected into a payment-processing endpoint could allow an insider to reroute small amounts from hundreds of accounts into a collaborator’s wallet — never touching the money directly, and making it look like legitimate transactions.</p><p>Although true insider attacks are uncommon, their impact is outsized: user trust evaporates, financial losses mount, and recovery can take months or years.</p><p>Forward-thinking companies treat “insider risk” as seriously as external threats. They enforce strict separation of duties, limit who can run queries in production, monitor transaction patterns for anomalies, and require multi-party approval for sensitive changes.</p><h4>Good Systems Assume Mistakes Will Happen</h4><p>In a secure system, mistakes are not viewed as rare exceptions — they are expected.</p><p>Strong companies don’t just hope that developers will never slip up.<br>They assume that accidents, negligence, and even rare malicious actions will happen — and they build layers of defenses to catch and contain the damage before it spreads.</p><p>This means enforcing code reviews, limiting database permissions, using automated vulnerability scans, maintaining audit trails, and applying the principle of least privilege at every level.</p><p>Good security isn’t about trusting people more.<br>It’s about trusting the systems that protect you when people inevitably fail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*rpHa2AzvZ1qrd8ch.gif" /></figure><p>Building secure systems means accepting this uncomfortable truth — and preparing for it.</p><p><strong>This preparation isn’t complex, but it must be deliberate.</strong></p><ul><li>Enforce mandatory code reviews before deployment</li><li>Apply the principle of least privilege to database and system access.</li><li>Use automated vulnerability scanning in your CI/CD pipelines.</li><li>Maintain detailed audit logs and monitor for unusual activity</li><li>Separate environments (development, staging, production) with strict boundaries.</li></ul><p>These steps won’t eliminate risk — but they make disasters far less likely.</p><p>Today, take 30 minutes to review your CI/CD pipeline: Are your code reviews automated? Is least privilege enforced?</p><p>Trust your people.<br>Trust their intentions.</p><p><strong>But trust your systems more.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdf05bd9efad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fast Today, Costly Tomorrow: You’re Paying to Kill Your Startup]]></title>
            <link>https://oguzhantursun.medium.com/fast-today-costly-tomorrow-youre-paying-to-kill-your-startup-8ac5602f41af?source=rss-4ba222987a0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ac5602f41af</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[scalability]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technical-debt]]></category>
            <dc:creator><![CDATA[Oğuzhan Tursun]]></dc:creator>
            <pubDate>Wed, 23 Apr 2025 08:02:30 GMT</pubDate>
            <atom:updated>2025-04-23T08:02:30.668Z</atom:updated>
            <content:encoded><![CDATA[<h4>Shortcuts feel cheap — until the bill arrives.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nIIEXscDYNllga_dlrrEBw.png" /></figure><h4>Fast results can feel like progress — but are they really?</h4><p>Startups often prioritize speed, especially under pressure from impatient customers or looming deadlines. But shortcuts today can quickly become crippling problems tomorrow, causing delays, cost overruns, and endless frustration. This phenomenon, known as <strong>technical debt</strong>, isn’t just theoretical — it’s actively harming startups by consuming money, time, and resources.</p><h3>Technical Debt vs. Financial Debt: Similarities and Crucial Differences</h3><blockquote>You can compare technical debt to a loan, but...</blockquote><p>If you’re familiar with technical debt, you’ve likely heard the loan metaphor before. Simply put, the loan analogy emphasizes the “interest” that continually grows on technical debt. If you leave technical debt unresolved, it will keep increasing every time you add a new feature or enhance an existing one.</p><p>But technical debt is worse. With a loan, it’s the bank that increases your debt. Technical debt, however, is different — you actively pay to increase your own debt.</p><h3>The Hidden Costs of Speed: A Real-Life Example</h3><p>Imagine you’ve hired two developers at your startup, each earning $20 per hour. Your biggest client requests a new feature that requires integrating data from a third-party app. One developer estimates they can build this feature in 5 days using a robust, high-quality approach. The other developer says they can complete the task in just 2 days — but only by adopting a quicker, lower-quality method. Working standard 8-hour days, the faster method costs you $320, whereas the high-quality option costs $800 — and risks frustrating your impatient client.</p><p>You choose the quicker solution, thinking, “We’ll switch to the better approach later — right now, customer satisfaction comes first.” This sounds reasonable in theory. But in practice, your impatient client won’t suddenly become patient. Instead, they’ll continue expecting rapid turnarounds, pushing you repeatedly toward shortcuts and deeper technical debt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*xCDIJQWDnV8q6ERA.gif" /></figure><h3>Inside the Shortcut: How Technical Debt Accumulates</h3><p>To put this in technical terms, the quicker approach involves directly making API requests inside each feature function using built-in or third-party libraries, often hardcoding payloads and skipping proper testing. And, realistically, that’s probably the solution you chose.</p><p>As expected, your client continually asks for new features. Each time, your developers find themselves hardcoding fresh API requests, repeatedly re-implementing similar functionality. Even in this isolated scenario, technical debt clearly accumulates. But the problem doesn’t end there. When new developers join your team, they naturally follow the established practices, reinforcing and amplifying these inefficient methods.</p><p>Then imagine this scenario: after 150 hardcoded API requests, you decide it’s time to log each response. Suddenly, you’re faced with revisiting every single request to manually insert logging. And since you initially skipped writing automated tests, you now have to manually verify 150 separate features — costing weeks of additional effort. You’re forced to buy more developer time, delay new work, and ask your increasingly impatient client to wait even longer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/0*TkqlnHfjy1Q2UJie.gif" /></figure><h3>Two Higher-Quality Alternatives to Avoid Technical Debt</h3><p><strong>Option 1: Create your own request library</strong></p><p>You could wrap the built-in or third-party library in a reusable function:</p><pre>function sendRequest(url, payload) {<br>    const response = builtIn.sendRequest(url, payload);<br>    return response.json();<br>}</pre><p>When logging becomes necessary, developers only need to add it once — directly within this function.</p><p><strong>Option 2: Implement Feature Configurations via a Database</strong></p><p>You could design a generic function like runFeatureFromDB(), storing feature configurations as database entries accessible through your CMS. With this approach, you won&#39;t even need developers for similar future feature requests. Your client could get new functionality in just a few hours, without repeated coding effort.</p><h3>Short-Term Savings, Long-Term Disaster</h3><p>By applying this second method, your initial investment might be just three additional days. Afterward, similar features could be added in under two hours each time.</p><p>In short, the three days you initially saved by incurring technical debt could eventually cost you hundreds of days — and tens of thousands of dollars — in unnecessary development and maintenance. Remember, you didn’t just accumulate debt; you actively spent money to grow it!</p><p>Technical debt isn’t merely a passive loan. It’s an expensive liability that you’re continually funding.</p><h3>The Takeaway: Invest Wisely from Day One</h3><p>Technical debt isn’t just an abstract concept; it’s a real, active threat to your startup’s sustainability. Choosing quick fixes over thoughtful solutions may seem economical at first, but in reality, you’re paying for the privilege of making your own debt grow.</p><p>This doesn’t mean you must always select the perfect solution. However, it does mean choosing solutions you can gradually improve over time.</p><p><strong>Invest wisely from the start</strong>, because the cost of short-term convenience might just be your startup’s long-term survival.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*XFme4zdR-dyqQAU4" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ac5602f41af" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>