Henrik Nyh
@henrik.nyh.se
There are cardboard knives that are supposedly extra good for the purpose! Have not tried.
www.youtube.com/shorts/qkbY6...
www.youtube.com/shorts/qkbY6...
Stop! Your knife isn't for cardboard! #edc #cheaptools
YouTube video by Rabid Haggis
www.youtube.com
July 19, 2025 at 5:49 PM
There are cardboard knives that are supposedly extra good for the purpose! Have not tried.
www.youtube.com/shorts/qkbY6...
www.youtube.com/shorts/qkbY6...
Typo: "where a base not update"
July 17, 2025 at 10:58 PM
Typo: "where a base not update"
Oh, this sounds so good! 😍
July 17, 2025 at 12:01 PM
Oh, this sounds so good! 😍
The idea is that my artist partner is unlikely to use en-dashes for other purposes in product titles, so they can serve as a reliable separator; it's easy to type (opt + hyphen); and it reads well when not given special design treatment – it's more correct (🧐) than the hyphen we had before, even.
July 15, 2025 at 10:36 AM
The idea is that my artist partner is unlikely to use en-dashes for other purposes in product titles, so they can serve as a reliable separator; it's easy to type (opt + hyphen); and it reads well when not given special design treatment – it's more correct (🧐) than the hyphen we had before, even.
So curious why this is not an end-user setting. Have they formalised changing it manually? Is it a case of support and devs not communicating? Is it bespokeness theatre, with a support-only setting?
July 12, 2025 at 8:31 PM
So curious why this is not an end-user setting. Have they formalised changing it manually? Is it a case of support and devs not communicating? Is it bespokeness theatre, with a support-only setting?
In the spec:
run(ids, spec_hook: -> { run(ids) })
(Code abbreviated to fit.
I'd use a clearer arg name and explicitly check out a DB connection inside the thread:
Item.connection_pool.with_connection do
parallel_run_for_specs.call
end
Ensure the test env DB pool size is > 1.)
run(ids, spec_hook: -> { run(ids) })
(Code abbreviated to fit.
I'd use a clearer arg name and explicitly check out a DB connection inside the thread:
Item.connection_pool.with_connection do
parallel_run_for_specs.call
end
Ensure the test env DB pool size is > 1.)
Twist
Thread.new
July 6, 2025 at 7:44 AM
In the spec:
run(ids, spec_hook: -> { run(ids) })
(Code abbreviated to fit.
I'd use a clearer arg name and explicitly check out a DB connection inside the thread:
Item.connection_pool.with_connection do
parallel_run_for_specs.call
end
Ensure the test env DB pool size is > 1.)
run(ids, spec_hook: -> { run(ids) })
(Code abbreviated to fit.
I'd use a clearer arg name and explicitly check out a DB connection inside the thread:
Item.connection_pool.with_connection do
parallel_run_for_specs.call
end
Ensure the test env DB pool size is > 1.)
There are apps though I haven’t tried them myself: halide.cam
”Now with Process Zero - for zero-AI, minimally processed shots.”
”Now with Process Zero - for zero-AI, minimally processed shots.”
Halide Mark II: Pro. Camera. Action.
The most powerful camera for iPhone and iPad.
halide.cam
July 4, 2025 at 10:48 AM
There are apps though I haven’t tried them myself: halide.cam
”Now with Process Zero - for zero-AI, minimally processed shots.”
”Now with Process Zero - for zero-AI, minimally processed shots.”
Yeah, that makes sense; cheers. Reading the post closer, it proceeds to use that argument as a polymorphic receiver in a second method call, and is making a point about that second method call not being cached for this reason.
June 5, 2025 at 4:02 PM
Yeah, that makes sense; cheers. Reading the post closer, it proceeds to use that argument as a polymorphic receiver in a second method call, and is making a point about that second method call not being cached for this reason.
Though I see now that was 10 years ago 😅 No longer true?
June 5, 2025 at 3:09 PM
Though I see now that was 10 years ago 😅 No longer true?