tim
@timteezee.bsky.social
being an underachieving, overly fussy pedant since 2013. dumb, but stubborn, so end up winning. views don't represent the employer I'm employed at
agree, Sub should have been Diff or something. But backwards compat....
Add makes sense though to handle both forward and back
Add makes sense though to handle both forward and back
October 29, 2025 at 5:15 AM
agree, Sub should have been Diff or something. But backwards compat....
Add makes sense though to handle both forward and back
Add makes sense though to handle both forward and back
maybe I'm misunderstanding your use case
that's the whole point of the getter, to return something with your intended scope
I agree, some work is required, at the expense of a simpler compiler and probably faster build time (generalizing)
that's the whole point of the getter, to return something with your intended scope
I agree, some work is required, at the expense of a simpler compiler and probably faster build time (generalizing)
October 22, 2025 at 2:49 PM
maybe I'm misunderstanding your use case
that's the whole point of the getter, to return something with your intended scope
I agree, some work is required, at the expense of a simpler compiler and probably faster build time (generalizing)
that's the whole point of the getter, to return something with your intended scope
I agree, some work is required, at the expense of a simpler compiler and probably faster build time (generalizing)
add getters for the private fields?
immutability would reduce boilerplate, but adds complexity to the compiler and runtime.
immutability would reduce boilerplate, but adds complexity to the compiler and runtime.
October 22, 2025 at 12:16 PM
add getters for the private fields?
immutability would reduce boilerplate, but adds complexity to the compiler and runtime.
immutability would reduce boilerplate, but adds complexity to the compiler and runtime.
what's wrong with encapsulating in package and making all fields unexported?
October 21, 2025 at 11:07 PM
what's wrong with encapsulating in package and making all fields unexported?
func name should be UUID, aughhhh
October 8, 2025 at 12:44 AM
func name should be UUID, aughhhh
compared to what language?
September 26, 2025 at 5:33 PM
compared to what language?
Didn't want to randomly tag you, but full credit for this came from a Twitter post from you. I ended up taking the same picture when I visited SF.
Truer words never said
Truer words never said
July 28, 2025 at 2:53 AM
Didn't want to randomly tag you, but full credit for this came from a Twitter post from you. I ended up taking the same picture when I visited SF.
Truer words never said
Truer words never said
if OCaml has a strong standard lib for engineering grade work (auth, http, logging/pager integration), then that def seems interesting.
July 26, 2025 at 4:11 PM
if OCaml has a strong standard lib for engineering grade work (auth, http, logging/pager integration), then that def seems interesting.
compiler automatically creates documentation and doc tests from tests. great tooling.
only a few ways to do things, and the language forces these patterns for consistency.
basically golang, but with a more robust type system (dedicated nullable type).
only a few ways to do things, and the language forces these patterns for consistency.
basically golang, but with a more robust type system (dedicated nullable type).
July 26, 2025 at 2:28 PM
compiler automatically creates documentation and doc tests from tests. great tooling.
only a few ways to do things, and the language forces these patterns for consistency.
basically golang, but with a more robust type system (dedicated nullable type).
only a few ways to do things, and the language forces these patterns for consistency.
basically golang, but with a more robust type system (dedicated nullable type).