@DiazCarrete@hachyderm.io avatar

DiazCarrete

@DiazCarrete@hachyderm.io

This profile is from a federated server and may be incomplete. Browse more on the original instance.

DiazCarrete, to random
@DiazCarrete@hachyderm.io avatar

I hate package-by-layer so fucking much. "Hey, see this cohesive set of files that together implement a feature? Let's spread them over the four corners of the codebase and send you in fun little Easter egg hunts every two minutes".

DiazCarrete, to haskell
@DiazCarrete@hachyderm.io avatar
DiazCarrete, (edited ) to webdev
@DiazCarrete@hachyderm.io avatar

Indeterminate state: neither checked nor unchecked but a secret third thing
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/checkbox#indeterminate_state_checkboxes

DiazCarrete, to haskell
@DiazCarrete@hachyderm.io avatar
DiazCarrete, (edited ) to random
@DiazCarrete@hachyderm.io avatar

using macos built-in text recognition capability I guess you could say I'm an AI power user.

https://support.apple.com/guide/preview/interact-with-text-in-a-photo-prvw625a5b2c/mac

DiazCarrete, to haskell
@DiazCarrete@hachyderm.io avatar

If you write a function with four positional parameters, you should feel a vague sense of guilt. If you write one with five or more positional parameters, you should repent.

DiazCarrete, to haskell
@DiazCarrete@hachyderm.io avatar
DiazCarrete, to random
@DiazCarrete@hachyderm.io avatar
DiazCarrete, (edited ) to random
@DiazCarrete@hachyderm.io avatar

blobless clones, treeless clones, shallow clones (2020)

"[treeless] clones are best for build environments where the repository will be deleted after a single build, but you still need access to commit history."

🔗 https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/
🔗 https://git-scm.com/docs/git-clone#Documentation/git-clone.txt---filterltfilter-specgt
🔗 https://git-scm.com/docs/git-rev-list#Documentation/git-rev-list.txt---filterltfilter-specgt

DiazCarrete, (edited ) to random
@DiazCarrete@hachyderm.io avatar

You should RTFM. Working with statically typed languages can overly encourage skipping RTFM, but when working with something like Nix I can't emphasize enough how lost you will be without RTFM.

"now... wait... you mean that this thing can also be used like that... in this context?"

(sometimes TFM sucks though)

🔗 https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake#flake-format
🔗 https://nixos.org/manual/nix/stable/language/derivations.html
🔗 https://nixos.org/manual/nix/stable/command-ref/new-cli/nix#installables

DiazCarrete, to random
@DiazCarrete@hachyderm.io avatar

Typical mis-targeting bug.

DiazCarrete, to random
@DiazCarrete@hachyderm.io avatar

"nix run" is super convenient.

Although I struggled to figure out how to run the secondary executable of a package. "nix shell" with the "--command" flag did the trick.

https://determinate.systems/posts/nix-run
https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-run
https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-shell
https://github.com/NixOS/nix/issues/4498

DiazCarrete,
@DiazCarrete@hachyderm.io avatar

nix run nixpkgs/23.11#hello

Here, the "nixpkgs/23.11" is an indirect reference: it goes through the flake registry.

"The specified rev and/or ref [23.11] are merged with the entry in the registry; see nix registry for details."

🔗 https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake#flake-references
🔗 https://discourse.nixos.org/t/using-nixpkgs-legacypackages-system-vs-import/17462/17

DiazCarrete, to random
@DiazCarrete@hachyderm.io avatar

We cannot know the resource-in-itself, only its representations. Very Kantian!

https://www.rfc-editor.org/rfc/rfc9110.html#section-3.2
https://en.wikipedia.org/wiki/Thing-in-itself

DiazCarrete, to random
@DiazCarrete@hachyderm.io avatar

If your branch has a good number of commits since it diverged from main, rebasing can sometimes seem like a Sisyphean task. Because each commit is applied independently, you often end up resolving merge conflicts again and again in the same places, conflicts that a merge would make you resolve together in one go.

To avoid that, I sometimes squash together all the commits in my branch before rebasing on top of main. But then of course I lose the structure of the separate commits.

DiazCarrete,
@DiazCarrete@hachyderm.io avatar

@nshephard Thanks! Although my understanding is that "rerere" mostly helps when you do repeat merges/rebases and discard the results. The docs say:

"With rerere enabled, you can attempt the occasional merge, resolve the conflicts, then back out of the merge."

In my case, I just want to perform the rebase and be done with it. The problem is merging the individual commits one by one. I dislike having to resolve the extra conflicts, even the first time!

DiazCarrete,
@DiazCarrete@hachyderm.io avatar

@BoydStephenSmithJr That "partial squash" technique sounds interesting! Is there a more detailed description of it somewhere? How does "resolving a conflict [...] to a version further down" work?

DiazCarrete, (edited )
@DiazCarrete@hachyderm.io avatar
DiazCarrete,
@DiazCarrete@hachyderm.io avatar

@nshephard Actually, I've found some links that talk about rerere helping even for single rebases (?) so maybe I'm wrong. But I'm still unsure about why it would work 🤔

🔗 https://mindup.medium.com/enable-git-rerere-for-easy-merging-303c6f2dacd3
🔗 https://stackoverflow.com/questions/10601541/smarter-rebase-avoiding-redundant-work

DiazCarrete,
@DiazCarrete@hachyderm.io avatar
DiazCarrete, to random
@DiazCarrete@hachyderm.io avatar

4:40 "I'm a huge fan of debugging"
📽️ 🔗 https://www.youtube.com/watch?v=javGxN-h9VQ

DiazCarrete, to random
@DiazCarrete@hachyderm.io avatar
DiazCarrete, (edited ) to random
@DiazCarrete@hachyderm.io avatar
DiazCarrete, (edited ) to random
@DiazCarrete@hachyderm.io avatar

Researching some doubts I had about serialized theading mode and prepared statements.

It seems that sharing a prepared statement between threads is bad news, even in serialized mode.
🔗 https://www.sqlite.org/threadsafe.html
🔗 https://sqlite.org/forum/forumpost/9d87fe7c8e
🔗 https://sqlite-users.sqlite.narkive.com/6l92EAHJ/serialized-prepared-statement-clarification

DiazCarrete,
@DiazCarrete@hachyderm.io avatar

"the interesting features of SQLite are far more connection-oriented than most client-server databases" 🔗 https://crawshaw.io/blog/go-and-sqlite

Making SQLite faster in Go 🔗 https://turriate.com/articles/making-sqlite-faster-in-go

GitHub issue for some ORM 🔗 https://github.com/typeorm/typeorm/issues/1884

DiazCarrete, to haskell
@DiazCarrete@hachyderm.io avatar

Wrote a toy dependency injection library for . inductive tuples, graph topological sorting and dynamic typing under the hood.
https://discourse.haskell.org/t/cauldron-a-toy-dependency-injection-framework/8092

DiazCarrete,
@DiazCarrete@hachyderm.io avatar
  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • cubers
  • magazineikmin
  • GTA5RPClips
  • khanakhh
  • InstantRegret
  • Youngstown
  • mdbf
  • slotface
  • thenastyranch
  • everett
  • osvaldo12
  • kavyap
  • rosin
  • anitta
  • DreamBathrooms
  • Durango
  • modclub
  • ngwrru68w68
  • vwfavf
  • ethstaker
  • tester
  • cisconetworking
  • tacticalgear
  • Leos
  • provamag3
  • normalnudes
  • JUstTest
  • All magazines