delete: useless sections

Author: danieldanielecki

data/blog/software-development/web-development/frontend/javascript/slice-vs-substring-vs-substr-complete-javascript-string-methods-comparison.mdx

@@ -1174,18 +1174,6 @@ If you prefer video-based learning and want to learn JavaScript from industry ex
 
 This video-based course provides insights into how JavaScript is used at scale in professional environments. It includes hands-on projects and assessments that help you build a portfolio of real JavaScript applications, perfect for visual learners who benefit from watching demonstrations and explanations.
 
-### Why Continue Learning?
-
-Understanding string methods like `slice()`, `substring()`, and `substr()` is important, but JavaScript is a vast language with many powerful features. These courses will help you:
-
-- **Build Complete Applications**: Move beyond individual methods to full-stack development
-- **Understand Modern JavaScript**: Learn ES6+, async/await, modules, and more
-- **Work with Real Projects**: Apply your knowledge to build actual web applications
-- **Follow Industry Standards**: Learn best practices used by professional developers
-- **Prepare for Career Growth**: Gain skills that are in high demand in the job market
-
-Whether you're a beginner looking to start your JavaScript journey or an experienced developer wanting to fill knowledge gaps, these courses provide structured, comprehensive learning paths that complement the detailed knowledge you've gained about string manipulation methods.
-
 ## Best Practices
 
 ### 1. Prefer slice() Over substring() and substr()
@@ -1309,43 +1297,3 @@ Understanding the differences between `String.prototype.slice()`, `String.protot
    - All methods coerce non-number types to numbers
    - `slice()` and `substring()` handle undefined differently (slice defaults better)
    - NaN becomes 0 in all methods
-
-### Practical Guidelines
-
-- **Always use `slice()`** for new code and migrations
-- **End index is exclusive**: `slice(0, 5)` includes indices 0,1,2,3,4 (not 5)
-- **Negative indices are powerful**: `slice(-3)` gets last 3 characters elegantly
-- **Consistency matters**: Use `slice()` consistently across your codebase
-- **Unicode awareness**: All methods work with UTF-16 code units (not always code points)
-- **Performance**: Differences are negligible; choose based on functionality
-- **Migration**: Replace `substr()` and `substring()` with `slice()` when refactoring
-
-### Quick Reference Table
-
-| Scenario | `slice()` | `substring()` | `substr()` |
-|----------|-----------|---------------|------------|
-| Get last 3 chars | `str.slice(-3)` ✅ | `str.substring(str.length-3)` ❌ | `str.substr(-3)` ⚠️ |
-| Extract middle | `str.slice(2, 5)` ✅ | `str.substring(2, 5)` ✅ | `str.substr(2, 3)` ⚠️ |
-| Start > End | `""` (empty) ✅ | Swaps args ⚠️ | Works (length based) ⚠️ |
-| Negative start | Works ✅ | Becomes 0 ❌ | Works ✅ |
-| Negative end | Works ✅ | Becomes 0 ❌ | N/A (length param) |
-
-**Legend**: ✅ Recommended | ⚠️ Works but not recommended | ❌ Problematic
-
-### Memory Aid
-
-Think of `slice()` like slicing bread:
-- You specify where to start cutting and where to stop
-- Negative numbers mean "from the end"
-- It's precise and predictable
-
-Think of `substring()` like a helpful but sometimes too-helpful assistant:
-- It tries to fix your mistakes (swaps arguments)
-- But this can hide real bugs
-- It's less predictable
-
-Think of `substr()` as outdated equipment:
-- It uses a different measurement system (length vs index)
-- Still works, but confusing
-- Best to upgrade to modern tools (`slice()`)
-