assembly

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-10-15

Final complete day: 2026-10-15. Attention was 0.4% — this entity appeared in 12 of 2,852 analyzed posts/comments in the seven days ending that day (20 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-10-13 12:34 UTCComment

   My point is that being able to understand and navigate code is still very important, because AI tools don’t isolate developers from it the same way compilers isolate us from assembly. So your comment “can you write assembly” isn’t a gotcha you think it is. When juniors fully rely on AI in their workflows, this means they write, read and most importantly, reason about code less than they would before, and than the current senior engineers did when they were juniors, which impacts development of skills that still matter. There’s nothing to celebrate when someone cannot write the easiest method themselves.

2. 2026-10-12 21:16 UTCComment

   Exactly, we don’t have to write assembly because we have tools creating new abstraction layers, such as higher programming languages, and our reasoning can be contained to those levels entirely. You don’t need to be able to read or write assembly to create, debug, maintain, expand a Java program. The same cannot be said about AI coding. AI, at least in its current form, doesn’t isolate you from code the same way compilers isolate you from assembly. While you can generate code with AI, you still need to be able to review it, you still receive other pull requests with code rather than AI prompts, you still maintain a codebase in code, it’s still the code that acts as a source of truth for the program’s behaviour, and you still need to navigate it when debugging issues. Therefore we still have to be able to distinguish good code from bad code. And there’s an issue with that - while senior engineers have already developed this sense by writing thousands of lines of code back in the days, junior engineers - less so, and they are also learning it slower simply because they don’t write the code manually. I see it daily at a big tech company myself. This wouldn’t be an issue if the AI isolated as fully from code - but it hasn’t happened yet. And I am not sure it’s going to happen in a foreseeable future, simply because AI is non-deterministic.

3. 2026-10-12 20:43 UTCComment

   You could also give the same problem to 20 or 100 different developers and get 100 different code responses, whats your point? OP is saying junior developers. How much code have they written (serious code), none? handful? how would THEY know. They don't either, thats the whole entire point. The entire point of question, which seems to have gone completely over your head, is that the assembly or lower level code, we dont look at either today becuase we have tools. Yes, would could write assembly, yes, we could write C or Rust, but considering this is web dev, likely it is not. Its just abstraction layers, and this is the "next" abstraction tool we have. You are arguing we should stay in stone age? You have guardrails for the code, why not the tests? we have e2e tooling, we have unit tooling, you are saying you cannot describe your job to a machine properly?

4. 2026-10-12 00:27 UTCComment

   I see this comparison a lot and I don't think it's valid Going from assembly to higher level languages was just another abstraction. AI is something completely different. You're not really abstracting away anything... Secondly, going from assembly to C was still imperative programming, and still deterministic, where AI is neither. And no, I don't think assembly coders of old felt any sense great loss like people are feeling now. I think they just moved on to newer languages, like we always have. C, C++, Java, Kotlin, etc... I've used them all over the last 30 years... Never felt any loss like I do now. Anyway, C programmers still use assembly from time to time. Sorry, but I don't think its a valid comparison.

5. 2026-10-11 22:35 UTCComment

   People used to code in assembly, then they switched to high level programming languages. The assembly engineers probably felt the same, no? I think we'll get used to it.