2018-11-24
2144
#typescript
Dmitry Pashkevich
327
Nov 24, 2018 ⋅ 7 min read

7 bad excuses for not using TypeScript

Dmitry Pashkevich Web developer. Productivity geek. Linux user. Tea drinker. Amateur photographer.

Recent posts:

TanStack Form Vs. React Hook Form

TanStack Form vs. React Hook Form

How does TanStack Form, a newer form library, compare to React Hook Form, and should you consider using it?

Amazing Enyichi Agu
Jun 9, 2025 ⋅ 12 min read

SOLID Series: Liskov Substitution Principle (LSP)

A deep dive into the Liskov Substitution Principle with examples, violations, and practical tips for writing scalable, bug-free object-oriented code.

Oyinkansola Awosan
Jun 6, 2025 ⋅ 10 min read
Modern CSS Carousels: No JavaScript Required

Modern CSS carousels: No JavaScript required

This article walks through new CSS features like ::scroll-button() and ::scroll-marker() that make it possible to build fully functional CSS-only carousels.

Saleh Mubashar
Jun 6, 2025 ⋅ 5 min read
hidden coast of developer elitism

It’s time to break the cycle of developer elitism

Let’s talk about one of the greatest problems in software development: nascent developers bouncing off grouchy superiors into the arms of AI.

Lewis Cianci
Jun 4, 2025 ⋅ 9 min read
View all posts

3 Replies to "7 bad excuses for not using TypeScript"

  1. “This makes the learning curve extremely lean”

    Most people don’t know what “learning curve” means. A steep learning curve actually means that learning increases rapidly with experience, i.e. it’s easy to learn.

    A “lean learning curve” can only mean the person who drew the graph with a sharp pencil and produced a thin (“lean”) line. 🙂

  2. JiveturkeyJay – 100% agree – TDD should be the first thing people look at if they aren’t doing it.

    The number of places using Typescript – lots more code only to catch a handful of bugs – when they aren’t even doing unit tests – which catch real problems and give you confidence refactoring.

    It’s kind of crazy.

Leave a Reply