> I just don’t code manually anymore

I'm curious about what industry you are in and the tech stack you are using?

without revealing too much generic saas at non-toy scale, 95% TS + postgres + 5% a very long tail of other stuff.

> By far the greatest IDE I have ever used was Visual Studio C++ 6.0 on Windows 2000

Visual C++ 6 was incredible! My favourite IDE of all time too.

Poor fellow has never used IntelliJ IDEA.

Yes I have.

It’s a boil the frog thing.

The first punchline

> Our mission is to ensure AGI benefits all of humanity; our pursuit of advertising is always in support of that mission

They had a great article on this too.

It is not necessary in a theoretical sense, but in a practical sense developers that care about memory efficiency only have a handful of options.

If you also care about memory safety it further limits options.

I couldn’t tell if this article was genuine or satire, and I changed my mind several times throughout.

See this thread from a while back: https://news.ycombinator.com/item?id=46039274

You’re gonna love ctrl-r name-of-command

> Try debugging without breakpoints

Why would you need to give this up? I use breakpoints with terminal debuggers all the time.

Yea this take makes no sense. What in the world is wrong with debugging with breakpoints?

It is for many problems, especially concurrency related ones, much less powerful than trace points. But the issue I have seen is that some tools like gdb have unergonomic support for tracing so there I tend to use break points or printf debugging just because the tracing support is so bad in gdb.

It’s a particular subcategory of cork sniffing where you pick the hardest, dumbest way to do things because you’re a Real Developer

There is a good argument for never using debuggers except for core development- Once finished your logs/metrics/events should be good enough to understand what is happening in an application. If debugging your application requires breakpoints you wont really be able to debug a live instance, and wont be able to easily signal off what is happening in the future.

That is a reasonable argument - but it was not made in the article and also does not preclude the use of breakpoints (see your except clause which covers a lot of ground).

It actually said

> Debug your code without visual breakpoints

With ‘visual’ being the important aspect.

There's another section below your quote where the author also wrote:

  The Challenge
  [...]
  3. Try debugging without breakpoints

The alternative to breakpoints is to study the output logs. He wrote:

  Real Growth Requires Discomfort
  [...]
  Debug using logs and terminal output

Fair, I didn’t read that far as I got bored of the “thou shalt” nature of the thing.

Tbh it's the default way I start my app in, debug mode xD