2. Now click the big green button marked "Start now" in the "Apply online" section
3. Then click the link at the bottom of the page marked "I cannot apply on the UK ETA app"
4. Then click again "Continue application online"
And now you can start.
Realistically this is probably 2 clicks too many and, whilst on the face of it it's not that much effort, it might be enough to bamboozle the tech phobic/less capable - of which there are still many (and not just older generations, either), or your grasp of English isn't great. There's just a bit too much going on - too much content - with some of these pages, and I don't really see a good reason to bury the links all the way at the bottom the way they are at present.
I also properly hate this guy's website. Too much clicking around and exploring to find good, in focus, photographs of examples of his work. Maybe I should blame OP for not submitting a page with examples of the work but, whatever, I did not enjoy the hunting and pecking.
In practice zero hour contracts mean that if a company wants you to work you often need to work because if you don't they can simply not give you any more hours in future. I.e., the big difference between a zero hour contract and gig work is that in that the company controls the hours, not you.
And this isn't just because the companies are scummy, but for somewhat sensible operational reasons. Zero hour contracts are common in places like supermarkets because they allow companies to flex their staffing levels with, for example, seasonal demand (although there are other solutions to that problem that are better for employees!). On d day to day basis they might still need more shop floor workers on a busy Saturday than on a quiet Monday, so it means they need to be able to control the scheduling rather than workers controlling the scheduling to ensure they always have appropriate staffing levels. If you gave complete control to workers you'd regularly find you had too many people working at quiet times and too few at busy, and even if you put controls in place to avoid too many workers at a time, you'd never be able to guarantee that you'd have enough at busy times which wouldn't really be an acceptable outcome for anyone.
But going back to your point of misunderstanding: zero contracts are perhaps more like the worst aspects of gig employment married to the worst aspects of non-gig employment, which means that they operate quite differently to gig employment.
Author can be found in the settings avialable via the cog in the bottom right hand corner, which also allows you to select the timecard you want, and alter visual settings.
I need to find the time to do a bit of research into whether it's possible to use a web page as a screensaver because I'd love to use one of these for that.
I can’t actually get to the article on the WiFi network I’m on but when I see “No skill. No taste.” you don’t sound like the butt of that punchline. Clearly you at least have skill, and I’m in no position to judge your taste.
The people I have a problem with are the ones who have neither but nonetheless find their ways into positions of power and influence where they proceed to make everyone else’s lives varying degrees of miserable.
OTOH I have huge respect for anyone who makes their thing for their own satisfaction.
Yeah, but that's no different from any other aspect of office work, and more conventional forms of automation. Gains by one person are often offset to some extent by the laziness, inattentiveness, or ineptitude of others.
What AI has done is accelerate and magnify both the positives and the negatives.
In my experience the example you give here is exactly the kind of problem that AI powered code reviews are really good at spotting, and especially amongst codebases with tens of thousands of lines of code in them where a human being might well get scrolling blindness when quickly moving around them to work.
The AI is the one which made the mistake in the first place. Why would you assume it's guaranteed to find it?
The few times I've tried giving LLMs a shot I've had them warning me of not putting some validations in, when that exact validation was exactly 1 line below where they stopped looking.
And even if it did pass an AI code review, that's meaningless anyway. It still needs to be reviewed by an actual human before putting it into production. And that person would still get scrolling blindness whether or not the ai "reviewer" actually detected the error or not.
> The AI is the one which made the mistake in the first place. Why would you assume it's guaranteed to find it?
I didn't say they were guaranteed to find it: I said they were really good at finding these sorts of errors. Not perfect: just really good. I also didn't make any assumption: I said in my experience, by which I mean the code you shared is similar to a portion of the errors that I've seen LLMs find.
Which LLMs have you used for code generation?
I mostly use claude-opus-4-6 at the moment for development, and have had mostly good experiences. This is not to say it never gets anything wrong, but I'm definitely more productive with it than without it. On GitHub I've been using Copilot for more limited tasks as an agent: I find it's decent at code review, but more variable at fixing problems it finds, and so I quite often opt for manual fixes.
And then the other question is, how do you use them? I tend to keep them on quite a short leash, so I don't give them huge tasks, and on those occasions where I am doing something larger or more complex, I tend to write out quite a detailed and prescriptive prompt (which might take 15 minutes to do, but then it'll go and spend 10 minutes to generate code that might have taken me several hours to write "the old way").
> "I wish things I think are cool got more upvotes"
HN has a very different personality at weekends versus weekdays. I tend to find most of the stuff I think is cool or interesting gets attention at the weekends, and you'll see slightly more off the wall content and ideas being discussed, whereas the weekdays are notably more "serious business" in tone. Both, I think, have value.
So I wonder if there's maybe a strong element of picking your moment with Show HN posts in order to gain better visibility through the masses of other submissions.
Or maybe - but I think this goes against the culture a bit - Show HN could be its own category at the top. Or we could have particular days of the week/month where, perhaps by convention rather than enforcement, Show HN posts get more attention.
I'm not sure how workable these thoughts are but it's perhaps worth considering ways that Show HN could get a bit more of the spotlight without turning it into something that's endlessly gamed by purveyors of AI slop and other bottom-feeding content.
I think it's just numbers. There are maybe a few dozen people that see your post on /new. That's a tiny sample size, not a good proxy for how interesting the post is. You see this on Reddit as well where the same exact post gets 1 upvotes and then finally blows up.
Chasing clout through these forums is ill advised. I think people should post, sure. But don't read into the response too much. People don't really care. From my experience, even if you get an insanely good response, it's short lived, people think its cool. For me it never resulted in any conversions or continued use. It's cheap to upvote. I found the only way to build interest in your product is organic, 1 on 1 communication, real engagement in user forums, etc.
It's a good reminder that instead of hitting "refresh" on HN, hit up /new for a bit and drop some votes. Probably the most significant votes you'll have in a longtime.
> Option 1: Zhipu MaaS API (Recommended for Quick Start)
> Use the hosted cloud API – no GPU needed.
...
> Option 2: Self-host with vLLM / SGLang
So, first off, this looks really cool and, given I'm looking for OCR at the moment, I'm pretty interested in this and other OCR models.
With that said, the README implies that option 2 requires a GPU. That's fine but it would be incredibly helpful if the README were explicit about requirements, and especially the amount of memory it needs.
EDIT: Looking at the links under option 3, the docs for macOS setup suggest 8GB of unified memory is enough to run the model, which is pretty modest, so I'd imagine Option 2 is similar. Ollama also offers a CPU only option (no idea how that will perform - not amazingly, I'm guessing), but that would suggest to me that if your volume requirements are low and you can't shell out for or source a beefy enough GPU and don't want to pay the sometimes exhorbitant hire costs, you should be able to punt it on to a machine with enough memory to run the model without too much difficulty.
1. The first hyperlink in the Overview section takes you to this page: https://www.gov.uk/eta/apply
2. Now click the big green button marked "Start now" in the "Apply online" section
3. Then click the link at the bottom of the page marked "I cannot apply on the UK ETA app"
4. Then click again "Continue application online"
And now you can start.
Realistically this is probably 2 clicks too many and, whilst on the face of it it's not that much effort, it might be enough to bamboozle the tech phobic/less capable - of which there are still many (and not just older generations, either), or your grasp of English isn't great. There's just a bit too much going on - too much content - with some of these pages, and I don't really see a good reason to bury the links all the way at the bottom the way they are at present.
reply