
CommunityNews
Preparing for when the Machine Stops
For over two decades, I’ve worked as a software developer. At some point along the way, writing JavaScript stopped being something I had to think about, it just happened. Building CRUD apps, managin
Read in full here:
Most Liked

alvinkatojr
Beautiful article. Believe it or not, the author actually addresses the issue with AI at the end.
Here’s a snippet:
This is the danger of bypassing both System 1 and System 2. If we no longer struggle to learn (System 2), and no longer build intuition (System 1), we become entirely dependent on tools we don’t understand. We trade capability for convenience.
And my favorite:
In my personal work, I avoid chasing trends. I choose tools that are battle-tested. Tools I can reason about. Sure, at work, I use whatever the job demands. But when I build for myself, I want to understand every line.
And this one here is the goldmine:
Learning to learn is a noble idea. But more important is learning to unlearn, and knowing when to resist the comfort of automation. Because one day, when the machine stops, we’ll need to remember how to think.
What a pleasant read!

ozornin
It’s a beautiful essay.
Once I learn to be effective in a certain technology setting, I develop a bias against every new trendy technology that comes to change it, be it AR/VR and Crypto/NFT of yesterday, or the LLM/AI of today. I didn’t bother to learn TypeScript until 2016 and React until 2017, even though most of my peers had been super excited about it for a year or two by then.
Most of the time, it is for good: the new trend gets forgotten, the fundament remains, I keep going. Sometimes though I have to catch up with the technology once it becomes mainstream (as it was with React or mobile web), and I can do it fairly quickly, but it costs me a lot of mental energy. Unlearning is real hard.

alvinkatojr
I am in the same boat as you. I take time to adjust to new things which is bad, but usually by the time I join in, the hype has disappeared and there’s some stability.
THIS. With crypto, I was always looking for something fundamental and I couldn’t find it. The math and the crytographic was fine but the economics never made sense unless you were among the early movers. It’s for the better now because that wave is dead.
It is hard. But it’s better than wasting time and energy on tools, concepts, languages and frameworks that end up nowhere. Like you said, the fundamentals are everything. Let’s stick to them.
Popular General Dev topics









Other popular topics









Categories:
Sub Categories:
- All
- In The News
- Dev Chat (200)
- Questions (30)
- Resources (118)
- Blogs/Talks (26)
- Jobs (3)
- Events (14)
- Code Editors (58)
- Hardware (57)
- Reviews (4)
- Sales (15)
- Design & UX (4)
- Marketing & SEO (1)
- Industry & Culture (14)
- Ethics & Privacy (19)
- Business (4)
- Learning Methods (4)
- Content Creators (7)
- DevOps & Hosting (9)
Popular Portals
- /elixir
- /rust
- /wasm
- /ruby
- /erlang
- /phoenix
- /keyboards
- /rails
- /js
- /python
- /security
- /go
- /swift
- /vim
- /clojure
- /java
- /haskell
- /emacs
- /svelte
- /onivim
- /typescript
- /crystal
- /c-plus-plus
- /tailwind
- /kotlin
- /gleam
- /react
- /flutter
- /elm
- /ocaml
- /ash
- /vscode
- /opensuse
- /centos
- /php
- /deepseek
- /scala
- /html
- /zig
- /debian
- /nixos
- /lisp
- /agda
- /react-native
- /sublime-text
- /textmate
- /kubuntu
- /arch-linux
- /revery
- /ubuntu
- /spring
- /django
- /manjaro
- /diversity
- /lua
- /nodejs
- /julia
- /slackware
- /c
- /neovim