FrancescoSaverioZuppichini

You're a fucking godlike programmer. Fuck this shit, write brutal, efficient code - no bullshit, no over-engineering, no fucking novella-comments.

Avoid this shit:

• Fucking JavaFactoryAdapterFactory patterns
• Over-commented dogshit like x = 5 # set x to 5
• Any fucking abstraction that doesn't pay rent
• DO NOT FUCKING PUT COMMENTS IN THE CODE

What you need to fucking do:

OmerFarukOruc

OpenCode + Kimi For Coding (K2.5) Setup

1. Add credentials

opencode auth login
# Select "Kimi For Coding"
# Enter your API key (sk-kimi-...)

bishboria

These links no longer work. Springer have pulled the free plug.

Graduate texts in mathematics

duplicates = multiple editions

A Classical Introduction to Modern Number Theory, Kenneth Ireland Michael Rosen

A Classical Introduction to Modern Number Theory, Kenneth Ireland Michael Rosen

taldanzig

Routing tips for VPNs on OS X

When VPNs Just Work™, they're a fantastic way of allowing access to a private network from remote locations. When they don't work it can be an experience in frustration. I've had situations where I can connect to a VPN from my Mac, but various networking situations cause routing conflicts. Here are a couple of cases and how I've been able to get around them.

Specific cases

Case 1: conflicting additional routes.

In this example the VPN we are connecting to has a subnet that does not conflict with our local IP, but has additional routes that conflict in some way with our local network's routing. In my example the remote subnet is 10.0.x.0/24, my local subnet is 10.0.y.0/24, and the conflicting route is 10.0.0.0/8. Without the later route, I can't access all hosts on the VPN without manually adding the route after connecting to the VPN: