lyda

joined 1 year ago
sorted by: new top controversial old
2
Go API server (gitlab.com)
 

cross-posted from: https://programming.dev/post/5161514

A template project for creating OpenAPI document driven API servers in Go.

6
Go API server (gitlab.com)
 

A template project for creating OpenAPI document driven API servers in Go.

Conventional Commits: A specification for adding human and machine readable meaning to commit messages in c/git@programming.dev
[–] lyda@programming.dev 1 points 1 year ago

And then

git ci -am "Addressed performance issue in flurbin module

The flubin module was designed as a successor to the flurbar module
which took in...
[...500 line essay on the hostory, problem and solution deleted...]

Hopefully this will fully fix the issue discussed."

for a one character change that adds an additional, and unrequired, semicolon.

The Absolute Minimum Every Software Developer Must Know About Unicode in 2023 (Still No Excuses!) in c/programming@programming.dev
[–] lyda@programming.dev 6 points 1 year ago

Just because you can do something...

The Absolute Minimum Every Software Developer Must Know About Unicode in 2023 (Still No Excuses!) in c/programming@programming.dev
[–] lyda@programming.dev 5 points 1 year ago (1 children)

js console: document.querySelector('.pointers').hidden=true

Browse and Discover Manpages in c/linux@programming.dev
[–] lyda@programming.dev 3 points 1 year ago

ls /usr/share/man/man?/* will show you all the man pages on your system. I used to pick ones at random.

Originally there were a number of manuals. Manual 1 had user commands. Manual 2 had system calls. Etc. You can type man NUMBER intro to read about that manual. You can also use man -k or appropos but I've also just used grep. These days they're compressed so zgrep.

The Absolute Minimum Every Software Developer Must Know About Unicode in 2023 (Still No Excuses!) in c/programming@programming.dev
[–] lyda@programming.dev 11 points 1 year ago (5 children)

The mouse pointer background is kinda a dick move. Good article. but the background is annoying for tired old eyes - which I assume are a target demographic for that article.

How to affect the order of operations for "go generate" in c/golang@programming.dev
[–] lyda@programming.dev 2 points 1 year ago

Good answers. I like these. I like the more than one command in a file, that will work. And yes, should have read the source!

10
How to affect the order of operations for "go generate" (pkg.go.dev)
 

Say I have go:generate directives in two files: one in the foo/ directory and one in the mock/ directory. The generated mock code will need data structures from the generated code in the foo module. Will go generate ./... reliably generate code in the correct order? What do I need to do to make that happen?

Bingo for reproducible builds in c/golang@programming.dev
[–] lyda@programming.dev 1 points 1 year ago (1 children)

Well, nix would be an entire operating system. This is just for a build system to specify the versions of the tools to use.

13
Bingo for reproducible builds (github.com)
 

Wonder if anyone here has been using bingo for reproducible builds. I've found it to be really good and wish I could find similar tooling for things like python for tools like yamllint.

5
Version control for ~ (phrye.com)
 

Back in 2016 I finally moved from mercurial to a git-based tool for version controlling my home dir. I now have six repos. The link is to my first article on it. I use tagging on my blog so you can find the other vcsh articles from there. It makes switching machines super-simple and encourages me to write utilities to make my life easier.

Fossil: Fossil Versus Git in c/git@programming.dev
[–] lyda@programming.dev 1 points 1 year ago

I love that fossil exists. I would never use it, but I'm glad cranks have something to work on.

Signing Commits in Git, Explained in c/git@programming.dev
[–] lyda@programming.dev 2 points 1 year ago

I have never heard proper reasoning for squashing commits. I don't think sanitized history is useful in any context. Seeing the thought process that went into building something has been repeatedly useful in debugging things. It's also useful to me as a software engineering manager to help folks on my team get better. I could care less how "pretty" git log looks, but I care a hell of a lot about what git diff and git blame tell me. They help me figure out where issues actually are and how they came to be.

Signing Commits in Git, Explained in c/git@programming.dev
[–] lyda@programming.dev 6 points 1 year ago

This is yet another reason not to squash commits.

Dotfiles matter in c/programming@programming.dev
[–] lyda@programming.dev 1 points 1 year ago

I use vcsh to manage my home directory - including but not limited to dot files. Written a number of posts on it over the years: https://phrye.com/tags/vcsh/

What do y'all think about mailing lists and IRC as sole communication channels? in c/programming@programming.dev
[–] lyda@programming.dev 1 points 1 year ago

Projects like that make me want to create a uucp network and so I can email a bang path address to get my patch.

11
Memoization in Go (en.wikipedia.org)
 

I'm curious what people are doing for memoization in #golang. I've looked around and haven't found great libraries for this which makes me wonder if I'm pursuing the wrong solution to a problem.

Caching the return values of functions based on the params has been useful to reduce load on downstream services, make things a bit faster on average and even add some level of consistency in functions that can be highly variable (which is an odd use case but nonethelass useful). But maybe there's a different pattern/idiom that's used in the Go ecosystem?

view more: next ›