arkj

Hyrum’s Law reaching all the way down to the instruction decoder. And for those who care the ud2 opcode is 0F 0B

Is there a way for public to contribute?

The blogs from doubleword are indeed full precision. A great team doing a fantastic job.

Could this be because more code is coming in through vibe coding?

What we need next is SAGI@home, a distributed computing platform for finding free and open weights that leads to AGI.

The link is down with 403 error.

>Software 2.0 are the weights which program neural networks. >I think it's a fundamental change, is that neural networks became programmable with large libraries... And in my mind, it's worth giving it the designation of a Software 3.0.

I think it's a bit early to change your mind here. We love your 2.0, let's wait for some more time till th e dust settles so we can see clearly and up the revision number.

In fact I'm a bit confused about the number AK has in mind. Anyone else knows how he arrived at software 2.0?

I remember a talk by professor Sussman where he suggest we don't know how to compute, yet[1].

I was thinking he meant this,

Software 0.1 - Machine Code/Assembly Code Software 1.0 - HLLs with Compilers/Interpreters/Libraries Software 2.0 - Language comprehension with LLMs

If we are calling weights 2.0 and NN with libraries as 3.0, then shouldn't we account for functional and oo programming in the numbering scheme?

[1] https://www.youtube.com/watch?v=HB5TrK7A4pI

Will anything be ever written in future without a little help from llm?

An interesting glitch. A few more refreshes and got the site unavailable message. It’s fixed now.

Maybe it’s a client side error but I see three links of this post on the homepage.

Losing focus as a skill is something I see with every batch of new students. It’s not just LLMs, almost every app and startup is competing for the same limited attention from every user.

What LLMs have done for most of my students is remove all the barriers to an answer they once had to work for. It’s easy to get hooked on fast answers and forget to ask why something works. That said, I think LLMs can support exploration—often beyond what Googling ever did—if we approach them the right way.

I’ve seen moments where students pushed back on a first answer and uncovered deeper insights, but only because they chose to dig. The real danger isn’t the tool, it’s forgetting how to use it thoughtfully.

”‘AGI is x years away’ is a proposition that is both true and false at the same time. Like all such propositions, it is therefore meaningless.”

If you look at this from a top-down perspective, you’ll see downsides, but from a bottom-up view, those same differences can be an advantage. Different architectures have different capabilities, and writing assembly means you’re optimizing for performance rather than prioritizing code portability or maintenance.

I don’t understand why people praise Ramanuja so much. Why not this praise for Euler or Gauss?

SW is the Derrida of computation. More words to add more confusion than explain anything.

What makes professor Wirth a unique geek?

To be a geek of geeks in computer science you have to write an OS or a Compiler and professor Wirth did both. To top it up he wrote the hardware to run it all. Now that’s when you call someone a king of geeks.

Google search to intellexa results in an http site which got redirected. I am now installing the update.

>> When using the git commit command, we recommend always including two arguments: -an and -m.

This advice will mislead beginners for whom the article is written.

I’ve heard Zizek repeat this a lot in his talks but has never been able to find a reliable source for this claim

>> Looking back we had one CS professor who in 2007 predicted we'd all be jobless in ten years, i.e. 2017.

Doomsday prophecies are not limited to religious cults, you see them all around. It’s safe to say, from experience, AI is not going to outdated programmers but it’s going to make the mythical 10x engineer a common reality.

I was wondering what the title was alluding to, a little _ducking_ pointed to this, https://en.m.wikipedia.org/wiki/Caedite_eos._Novit_enim_Domi....

Better to add the year 2016 in the title.

Few common attributes I've seen in some of the master programmers I've had the privilege to work with,

* write lots and lots of code as beginner till some programs live in the muscle memory of your fingers

* humility, be easy on yourself; no one makes it in the first jump

* find better programs and copy but never paste, as a beginner always key-in your programs

* keep a count of the lines you write and the time you take to write (reach 100k lines, this is to motivate yourself)

* make programming habit

* seek better programmers and study their code

* always go from code to theory

>>Whereas, I find myself going for almost academic perfection (i.e read all docs first) / mastery.

I suffered from the same problem. The key for me was to say to myself, it's ok to write non-perfect programs, it's ok to fail, in fact it's a must to fail, humility, humility, humility is the key virtue for a true master programmer.

> Secondly, while the program has had some monster successes, a large percentage of fellows end up just going into tech jobs or worse, going to college after their two years are up

Any reference that has data around this claim?

> We offload TLS to the NIC, NOT TCP.

How is this possible? If TCP is done on the host and TLS on the NIC data will need to pass through the CPU right? But the slides show cpu fully bypassed for data

>> 4. I will vote you down if you 'tl;dr and summarise' any article; We're all grown-ups, and we all know how to read thanks.

Isn’t your comment against your own policy?

Looks like FAANG in the title is just to get your attention. Details are missing.

I think it will miss this case but we can extend the script to catch this case.

You mean τέχνη?

Authors deserves respect for keeping this book free.

We were lucky to have a paperback low-cost-poorer-countries edition of The MINIX Book[1]. The code in the Minix book was an eye opener.The code clarifies the concept and sharpens the understanding.

Later on in my career as driver/firmware programmer, Computer Systems - A Programmers Perspective[2] and Unix Systems for Modern Architectures[3] helped a lot to clarify confusions and mysteries.

[1] https://www.pearson.com/us/higher-education/program/Tanenbau... [2] https://www.pearson.com/us/higher-education/program/Bryant-C... [3] https://www.pearson.com/us/higher-education/program/Schimmel...