'Truck driver' here serving only to put him down, because the feat wouldn't be expected of such a person?
Seems to me like papers' infamous (at least in the UK) references to victims' or alleged perpatrators' house prices, to instruct our sympathy, when it's not otherwise at all relevant.
This isn’t someone working as a full time artist, this isn’t someone living off a trust fund, this isn’t someone selling their creating for millions for the money laundering. This is just a “man in his shed” with a blue collar job doing something awesome.
It says “anyone can doing something awesome”, you don’t need a fancy upbringing or million dollar backing.
Is it lifting him up? It's certainly irrelevant, is my point. My assumption then is that it's because it's supposed to be surprising. 'Hobbyist spends 20y on their hobby' isn't that surprising, even if the hobby is interesting; instead of letting the story stand on that interest, they're attempting to add 'shock and awe'.
I think it's fair enough that 'the assistant in the GUI/cloud program X, like Clippy++' has the same name for all X.
But it's absolutely bonkers that that's the same name as the IDE auto-complete integration, and the GitHub agentic worker, and the GitHub chat, and the GitHub reviewer.
Support for Go third-party packages is not part of this first release, but the tooling to generate bindings for Go packages (which enables imports from the Go stdlib) is already in place[1]. Extending it to support third-party packages is on the roadmap.
Especially with only 1mo commitment, what happens if there's a lot of churn after the first month – more people leave a cohort than are waiting for one? The whole cohort is then waiting for it to fill again before it restarts? And will people waiting for the next cohort to fill automatically be reassigned to the last (now not full) one anyway, or would there then be multiple partially filled cohorts for a single spec?
I like the idea, I just wouldn't want my subscription to suddenly be on hold because a peer decided to stop theirs.
> The video does say "do ISO last" which I think is a good guideline. Easier said than done while shooting, though.
> … also while fact checking this comment, I stumbled across Canon's KB stating to use as low an ISO as possible, which the video rails against. They should talk to Canon, I guess?
Isn't ISO last the same as setting it as low as possible? Obviously it's always set to something, so I thought 'doing it last' means start with it low, set exposure & shutter, increase as necessary?
(Shutter speed being dictated by subject and availability of tripod, essentially it's just exposure & ISO which becomes about how much light there is and how it's distributed, I suppose.)
I'm not really into photography though, so perhaps that's all nonsense/misunderstanding.
This is GitHub being overzealous/getting it wrong, or some miscommunication somewhere. These are forks of Anthropic's open source repo on GitHub, CEO said previously it's not them DMCAing forks of it.
reply