:)

Like I care what a fascist thinks. Why are you still here braying at me?

now run along and spread your fascist propaganda on fascist friendly instances

you won’t be missed

Because they have a predatory business model.

Usually what happens is people create lambda functions on AWS which are basically managed functions that get invoked when a request comes in (think a modern version of CGI), and then if there are a lot of requests then the user can easily end up with a huge bill.

I find the most relevant aspect of an estimate is how familiar the person making the estimate with the problem. People who have the best understanding will inevitably give the best estimates.

I’ve never touched ChatGPT out of principle, but everything I hear about it makes it sound like hot garbage.

My experience is that you want to keep changes as focused as possible. The smaller the context it has to work on the better the results tend to be, and the easier it is to check that it did what you actually wanted it to.

here’s what DeepSeek gave me for the following prompt: write a small bash script to check if a CSV exists and if it does rename to the filename_date.CSV and upload to hdfs, keep it simple

#!/bin/bash

# Check if filename argument is provided
if [ $# -eq 0 ]; then
    echo "Usage: $0 <csv_filename>"
    exit 1
fi

CSV_FILE="$1"

# Check if file exists
if [ ! -f "$CSV_FILE" ]; then
    echo "Error: File $CSV_FILE not found!"
    exit 1
fi

# Generate new filename with date (YYYYMMDD format)
DATE=$(date +%Y%m%d)
NEW_FILENAME="${CSV_FILE%.*}_${DATE}.csv"

# Rename the file
mv "$CSV_FILE" "$NEW_FILENAME"

# Upload to HDFS
hdfs dfs -put "$NEW_FILENAME" /path/to/hdfs/directory/

echo "Successfully processed: $NEW_FILENAME"

Not just OpenEvolve, I’m talking about how agents can use MCP to run code now. Cursor can now have agents iterate on a solution completely on their own.

Nowadays, the agents can iterate. It basically works like a genetic algorithm where it converges on a solution.

I’ve had pretty good success with DeepSeek making decent bash scripts. What was the script out of curiosity, I can try and see what DeepSeek spits out.

yup

I’m guessing single quotes, since a single double quote isn’t valid syntax.

yup

why not?

I’ve never got the appeal of that sort of thing either.

What I’m saying is that most good static typing systems do not practically have such limitations, you’d be very hard pressed to find them and they’d be fairly illogical. Most static typing systems that are used in enterprise do have limitations because they are garbage.

Of course they do, it’s silly to claim otherwise. Some type systems are certainly more flexible than others, but each one necessarily restricts how you can express yourself. Not to mention the fact that advanced type systems introduce mental overhead of their own. The more flexible the type system is the more complex it is as a result. There was even famously a debugger for Scala type system illustrating just how absurd things can get. I’ve used plenty of typed languages including Haskell, so I understand perfectly well how modern static typing works.

Meanwhile, I’d argue that Typescript provides incredibly weak guarantees in practice, and the impact of transpiling on the workflow is not insignificant.

My experience is that immutability plays a far bigger role than static typing. The best pattern for ensuring correctness and maintainability is to break things up into small components that can be reasoned about independently. Any large project can be broken up into smaller parts, and that’s by far the best approach towards ensuring correctness that I’ve seen.

Again, that’s my experience working with many different languages for over two decades now. I’m not suggesting other people can’t have their own preferences.