Advertisement · 728 × 90

Posts by Will_Amadeus

I just checked my email for free. AI is cooked.

1 month ago 119 2 6 0

Or “gluten-free”

2 months ago 0 0 0 0

Get ready for another week of breakthroughs

2 months ago 0 0 0 0

Do you feel good about that advice?

2 months ago 9 0 0 0
Post image

Attacking the P vs. NP problem with ruliology ... the beginnings of empirical theoretical computer science
writings.stephenwolfram.com/2026/01/p-vs...

2 months ago 16 4 0 1
E.W.Dijkstra Archive: On the foolishness of "natural language programming". (EWD 667)

"I suspect that machines to be programmed in our native tongues -- be it Dutch, English, American, French, German, or Swahili -- are as damned difficult to make as they would be to use." - Edsger Dijkstra www.cs.utexas.edu/~EWD/transcr...

2 months ago 68 8 4 0

Also, we should take responsibility for the code we submit regardless of how it was generated, and part of the review process helps me gain enough confidence to make that decision.

3 months ago 69 7 6 0

Grifters gotta grift

3 months ago 0 0 0 0

The right prompts and a shit ton of systems integration and data management

3 months ago 0 0 0 0
Advertisement

Hello @kelseyhightower.com sometime ago I remember you saying you like to learn things the hard way and reading docs written by humans. How this experience trying this tool reshapes your opinion? If it does. Cheers!

3 months ago 0 0 1 0

Spot on

3 months ago 0 0 0 0

I remember when the promise of AI was mostly about curing illnesses, enhancing cyber security and ethics in AI was a thing

3 months ago 1 0 0 0

What about Mistral

3 months ago 2 0 0 0

Interesting take. Do you happen to know if the R&D investment has factually decreased or is it less open source ?

3 months ago 1 0 1 0

It’s happening - new fulfilling jobs being created

3 months ago 1 0 0 0
Post image

One of the underrated papers this year:
"Small Batch Size Training for Language Models:
When Vanilla SGD Works, and Why Gradient Accumulation Is Wasteful" (arxiv.org/abs/2507.07101)

(I can confirm this holds for RLVR, too! I have some experiments to share soon.)

3 months ago 70 9 0 1

Do you write code at that successful software company?

4 months ago 5 0 0 0
Advertisement

ADF … taskflows eww

4 months ago 1 0 0 0

I also remember the total “Twitter rewrite”

4 months ago 0 0 0 0

And having a pension. Don’t forget pension a socialist invention

5 months ago 3 0 0 0

Been there. On the bright side it refreshes my codebase familiarity

5 months ago 1 0 0 0

Hearts at the PSF are full today from the responses about the recent grant turn down news we shared. All of your kind words of support & solidarity, as well as your donations & new memberships, mean the world to us. We're so grateful to be in community with each of you 💛🐍💙

5 months ago 150 32 1 3

I love your rants. Specially the one about global variables and global warming

5 months ago 1 0 0 0

One of the down to earth voices out there

5 months ago 2 0 0 0
Block an IP address
The most straightforward way to block and IP address is in the firewall. It is the tool build specifically for this.

To block the address 101.101.101.101, run from the command line


sudo ufw insert 1 deny from 101.101.101.101

This instructs ufw (the Uncomplicated FireWall) to insert a rule at the the top of the list (position 1) to deny all incoming traffic from the address. After running this, no restart of the firewall is needed. The rule is active. (ufw docs

The position 1 is important because in ufw, the first rule that matches is applied. If there was a rule to allow all addresses that started with 101. and that rule came before the deny rule, then the deny rule would never be reached.

While it's possible to block specific ports, or even to block an IP address from seeing particular pages, complex rules and conditions get difficult to analyze very quickly, and can lead to cases where there are loopholes. Use fancy rule combinations sparingly.

Parse logs
In their raw form access logs are technically human-readable, but they are a lot. I found it really useful to do a little parsing to pull out the bits I'm interested in. (I'm working with the default nginx log format, so adjust this according to your own.)

I wrote a script to take advantage of the repeatable structure of these logs to dissect them into their parts. It uses tricks like splitting the log based on brackets and spaces. It productes a pandas dataframe with columns containing the IP address, requested URI, HTTP status code, and every component of the date and time.

Block an IP address The most straightforward way to block and IP address is in the firewall. It is the tool build specifically for this. To block the address 101.101.101.101, run from the command line sudo ufw insert 1 deny from 101.101.101.101 This instructs ufw (the Uncomplicated FireWall) to insert a rule at the the top of the list (position 1) to deny all incoming traffic from the address. After running this, no restart of the firewall is needed. The rule is active. (ufw docs The position 1 is important because in ufw, the first rule that matches is applied. If there was a rule to allow all addresses that started with 101. and that rule came before the deny rule, then the deny rule would never be reached. While it's possible to block specific ports, or even to block an IP address from seeing particular pages, complex rules and conditions get difficult to analyze very quickly, and can lead to cases where there are loopholes. Use fancy rule combinations sparingly. Parse logs In their raw form access logs are technically human-readable, but they are a lot. I found it really useful to do a little parsing to pull out the bits I'm interested in. (I'm working with the default nginx log format, so adjust this according to your own.) I wrote a script to take advantage of the repeatable structure of these logs to dissect them into their parts. It uses tricks like splitting the log based on brackets and spaces. It productes a pandas dataframe with columns containing the IP address, requested URI, HTTP status code, and every component of the date and time.

New post: Controlling IP traffic on your webserver

A cool part about having your own webserver is that you get to choose who can visit. When IP addresses try to access sensitive files or aggressively scrape, you can just block them.

Here's how.

brandonrohrer.com/hosting5.html

6 months ago 9 3 0 0
Advertisement

Game changer

6 months ago 0 0 0 0
Preview
Self-promotion works, especially if you are bad at your job I have come across a recent paper that measures equity analysts self-representation on LinkedIn and the tone they use to describe their research and their views on LinkedIn and in the media.

Analysts who excel at self-promotion on LinkedIn are worse at their jobs, but experience the highest rates of promotion. klementoninvesting.substack.com/p/self-promo...

6 months ago 129 43 16 22

Game changer

7 months ago 0 0 0 0

Game changer

7 months ago 0 0 0 0

Me parece que ilustra muy bien el mundo actual

7 months ago 1 0 0 0