There was also s80 for the 9200/9500 and the s90 family of devices that didn’t get much beyond 2005. Sad really as I worked several of the UI parts. We had a fully customisable Home Screen where you could add and remove pages, move app icons - long before iPhone or android. It all got bined due to management preferring keyboard devices over touch screens.

I’ve driven around the Hemel Hempstead one a few times. Very confusing when I first saw the sign.

Programming languages, design languages and architecture are all inventions made to help humans write understandable source. LLMs don’t really need to do any of that. They can store very large trees of understanding and therefore implement any application in raw binary. Why bother with abstractions at all

LLMs for sure need those things. maybe not the same abstractions as humans do but without understabdable code an LLM will just fail to accomplish the task you ask it to do.

It might be less ambitious and more practical to target bytecode.

But you effectively lose the human review component.

There's more python and typescript in the training data than bytecode.

I was thinking about that. I reckon generating massive amounts of synthetic training data for that goal should be possible - you've already got the Python, after all. It's also possible for machine code, but you'd have to target more platforms.

But ultimately, I think human readability outweighs any theoretical advantage you get from removing a step in the compilation process.

Targeting byte code or asm instead of high level would be silly for everyday tasks. You blow up the number of tokens, reduce your effective context, and there's just more places for it to make a mistake, which most likely won't be caught by the assembler (unlike compilers).

As a 17 y.o (way back in the last century) I didn’t need to be advised to learn about transistors. I just had a thirst for the knowledge. I would encourage everyone to learn something about transistors. They are one of mankind’s most useful discoveries.

Hey, I'm 19 CS undergrad but i don't really know what to do but I really wanna build something that can shape the world. Can you tell me more about why you would advice someone to learn about transistors? what are the possible career paths?

Not the original commenter, but in my view as a crusty old software engineer, the reason to learn how transistors is because they're interesting and the key to how all computation is implemented. Once you learn how transistors work, you can learn how logic gates work. And then how CPUs and memory work. Bit by bit, computers stop being magic boxes and start being something built from technologies you understand.

Now, for most software careers (including my own), that knowledge isn't directly practical. BUT, the most important things for a successful, fulfilling career are curiosity and a willingness to dive into subjects _without_ necessarily knowing how (or even if) that knowledge will yield practical applications. That drive is what's going to lead to insights and breakthroughs over your career that wouldn't happen if you just let abstractions be abstractions.

Thank you

Agree. Transistors really are worth learning about to any level - its certainly possible to get lost in the physics.

I’d find some high level tutorials online that maybe use one of the free circuit simulator tools.

falstad.com/circuit/

Nice animation on this site

If you are really curious there are many simple circuits you can build.

It’s quite a thrill to get an LED to blink with a self built circuit.

I’m also a crusty old sw eng. I did spend sometime being a young electronics engineer.

Good luck with the journey.

Way back in time (1980s) I worked in the broadcast tv industry. We used to used digital still stores. A single frame of PAL took up 1MB of RAM. The machines had 2MB fitted. The board had a hardware cross fade function implemented in discrete logic chips. They also had a 20 or 40MB scsi drive. It was all controlled by a 6809 cpu. Quite impressive for the time