YHK - yet another hacker news clone

Architecture decisions, requirements analysis, trade-offs in technology selection, and cross-system debugging—these high-level cognitive activities cannot yet be replaced by AI. Focusing on these areas is actually a smarter skill investment.

Cognitive skills? You must be using cognition to guide the AI.

Either you are doing something guiding the AI or you are in your hammock doing nothing. If you’re in a hammock find a crossword puzzle.

I suppose work organisation, leadership, soft skills, working in areas with inherent uncertainty will be key for defending employment in near future

For every skill that may atrophy, I feel like I am developing experience in 10 new ones. I am not focused on using AI to perform my existing job function though, I am developing new capabilities.

In addition to what other people have said, I've taken some time to do leetcode questions lately - both architecture ones and coding ones. I'm not looking for a job by any stretch, but the practice and forcing a detailed zoom in has been really cathartic, and leetcode gives a nice structure/feeling of progress to it.

I honestly don't feel there is much atrophy or this is an issue at all

As if for example someone's skill lessened if they switched from assembly to a higher level programming language over time (like, does it matter?)

If you for some reason had to go back and program more manually, then you could do so as the need arises

Otherwise, LLMs appear to be here to stay and you don't actually need those skills that are even possibly admittedly "atrophying"

I guess we'd need a detailed pinpointing of what skills exist or existed and to identify if they actually ateophy (I guess I'm not sure if skills are really atrophying, or even if they are if it matters)

Edit: here's an idea or exercise or projects to work on. Maybe people should find clear documentation of pre-AI processes in case you need to go back and learn them. Or create such documentation if it doesn't exist (which would be an exercise to practice your skills to make you remember them).

It’s like skiing or biking, it comes back quickly.

Simple. I use my brain and write code without coding agents.

I am curious how the workflow of people, who do not write code at all, looks like, or what products do they build. In my experience LLMs are an excavator, but you still have to tweak the fine details with a shovel.

I use AI for Kubernetes. On a day-to-day basis, it runs 80%+ of my kubectl commands. It’s the most steroidal auto-complete I’ve tried. But I do get dumber for it.

What I do to compensate:

  - make it my duty to own every change, i.e. cognitively debt-free:
  - write summaries on every new thing I do (blog post, memo to colleague)
  - contribute documentation to the open-source projects I rely on
  - practice for CKA/CKAD certificates which require pre-LLM muscle memory
  - build interactive learning material for what I’m trying to learn
  - work with things that LLMs don’t yet trivially solve
  - repeat or reconstruct my recipes to perfect workflows, 

We’re incentivised to take the short path. I’m trying to create at least one path through a subject that I have to walk myself, preferably several times.

I find it inefficient to use models for all possible uses right now even with the current subsidies. As the costs increase this will only become more true. Keeping that in mind will naturally motivate you to not lose your skills by engaging in inefficient token burn.