F1 finally has a really nice system for showing time[0]. They show both the local time at the circuit and the local time wherever the user is. For years they showed only the track time, without even a hint about the timezone the track was in.

[0] https://www.formula1.com/en/racing/2025

https://en.wikipedia.org/wiki/Wikipedia:Fundraising_statisti...

Best I can find

    $    132,466.01  Africa
    $  4,902,373.13  Asia
    $ 49,423,340.29  Europe
    $106,546,895.77  N.America
    $  2,509,299.46  Other
    $  6,082,217.76  Oceania
    $    944,844.22  S.America

Convert that to GBP and you get about £7.5 million.

Figure that the UK accounts for about 15% of the European economy and assume it contributes to Wikipedia at about an equal share.

That's about £1.125 million in estimated annual recurring contributions from the UK.

You said 10-100/mo, so let's assume £55/mo or £660/year as the mean.

That would be about 1,700 Brits, a surprising number.

Of course, Ireland will have to move out the way. (Wait, is this an actual metaphor for Brexit?)

There are also the various territories of larger countries that aren't - French Guaiana in South America, Canary Islands are off the coast of Africa.

?

Can confirm

>The purpose of the European Commission is first of all to distribute its own software under the licence

The European Commission is the main executive branch of the European Union. The above sentence is like saying "the purpose of the White House is first of all to distribute software".

I don't think it's unreasonable to have a level-headed discussion about how society and technology have evolved since those norms came into practice, and if they should be expanded now that photography is ubiquitous.

You might have that wrong. It's when that space involves people wearing revealing clothing. And Airsoft kit is... not that.

It's not about exercise.

This paragraph really gets to the idea of why I think discussing someone’s taste is basically useless in an engineering context. This “predictably broken compass” person stands out like a sore thumb, and you can just hold a 20min behavioural interview to filter them out.

A far more dangerous engineer is the “partially broken compass”, which appears at first sight to be working because it spins around like you’d expect, but is actually 127degrees off at all times.

    func isEven(s string) bool {
        num, _ := strconv.Atoi(s)
        return num % 2 == 0
    }

    func isEven(s string) (string, error) {
        f, err := strconv.ParseFloat(s, 64)

        if err != nil {
            return "invalid", err
        }
        num := int(f)
        if num%2 == 0 {
            return "even", nil
        }
        else if num % 2 != 0 {
            return "odd", nil
        }
        return "invalid", nil
    }

    func isEven(num int) bool {
        return num % 2 == 0
    }
    func isEvenSafe(s string) (bool, error) {
        num, err := strconv.Atoi(s)
        if err != nil {
            return false, err
        }
        return isEven(num), nil
    }

There are a lot of ways to accumulate tech debt so fast you’d think you’re in a code casino.

1. Someone who has only ever written code by tutorial, and has no idea of the architecture, performance considerations or usability implications of the code they're writing.

2. Someone who has got to a point in their career LLM Coding and is unable to write code without it because they don't understand what they're doing.

The problem occurs when one of these people:

- Is required to be good at the things they are not yet

- Proceeds as they always have because they are unaware of their skill gap

- (Optionally) gets promoted while things are still _just_ working

IME you hit these silent inflection points as a system begins to scale beyond the experience of the people involved. They survive for a while (Coyote time / the compass is still pointing north) until something happens (the whole thing falls off a cliff / starts to go south).

The chance that they become a hostile actor to my business is effectively zero. Certainly among the lowest chances of any email provider.

I guess the same holds for this malicious (?) single developer.

The TAM, if you got absolutely every one of these people onto a $20/mo plan is $500,000,000/mo. For reference, that’s less than Airbnb’s revenue.

It's the actual engineers, lawyers, marketers, medical professionals and accountants that are the real targets.

There is a lot of focus on AI assisting software development right now because they are the people most willing to use it. AI as it is now will probably create more SWE positions overall. What you will have is software designers being added by AI and it's domain knowledge to build applications that replace the other professional roles.

The cost to utilize AI is going to be much much more expensive as it is heavily subsidized right now.

You’re not a state machine. A state machine does one serial task, which is why the input+state can create a consistent and deterministic output+state. There are no secondary input streams or exogenous factors to consider for calculating a state machine transition.

Humans create output from many streams of input, arriving at across many different time horizons. Because of this, you cannot create a deterministic model of a human’s state transition for a given input - a requirement of state machines.

This isn’t philosophical or semantics. Mathematically, you’re not a state machine.

Could you give some examples, and an indication of your level of experience in the domains?

The statement has a much different meaning if you were a junior developer 2 years ago versus a staff engineer.

I've been adding small features in a language I don't program in using libraries I'm not familiar with thhat meet my modest functional requirements in a couple minutes each. I work with an LLM to refine my prompt, put it into cursor, run the app locally, look at the diffs, commit, push and I'm live on vercel within a minute or two.

I don't have any good metrics for productivity, so I'm 100% subjective but I can say that even if I'd been building in Rails (it's been ~4 years but I coded in it for a decade) it would have taken me at least 8 hours to have an app where I was happy with both the functionality and the look and feel so a 10x improvement in productivity for that task feels about right.

And having a "buddy" I can discuss a project with makes activation energy lower allowing me to complete more.

Also, YC videos I don't have the time to watch, I get a transcript, feed into chatGTP, ask for the key take aways I could apply to my business (it's in a project where it has context on stage, industry, maturity, business goals, key challenges, etc) so I get the benefits of 90 minutes of listening plus maybe 15 minutes of summarizing, reviewing and synthesis in typically 5-6 minutes - and it'd be quicker if I built a pipeline (something I'm vibe coding next month)

Wouldn't want to do business without it.

And have another AI review your unit tests and code. It's pretty amazing how much nuance they pick up. And just rinse and repeat until the AI can't find anything anymore (or you notice it going in circles with suggestions)

Are the frontend folks having such great results from LLMs that they're OK with "just let the LLM check for security too" for non-frontend-engineer created projects that get hosted publicly?