38 karma · joined November 6, 2016
> Our last three cars, the eldest of which was from the 2017 model year [...].
Is it common to buy three cars in let's say 10 years? That seems like a large amount of spend (afaik cars depreciate in value rather quick?) and -- barring accidents -- a really short time to have to replace something as sturdy as a car; If I get less than three years out of a phone it feels like a waste and it feels like the main barrier for phone longevity (besides batteries, which are replaceable) is security updates.
IDK, since I don't see any comments on it, it must not be that strange, it just struck me as odd.
FWIW, my quick impression is that takes reasonable concepts and tries to formalize them into a framework; I can see potential benefits, I've certainly asked in a claude code session for it to have a look at pipeline so and so and figure out the issue, but I'm not really convinced by this at first glance either. Both setup-cost and token cost seem like downsides.
I'm sure I won't be the only one curious, please enlighten me.
[1]: <https://github.com/EnriqueLop/legalize-es/commit/424cbc96507...>
I don't think I've ever encountered a typo in any of the LLM output I've seen, seems like the exact sort of thing an LLM would be more or less perfect at. Am I wrong to take this as an indication that this text is actually written by a human as a concise marketing example?
Location: Germany (Bremen / Hamburg)
Remote: flexible (Europe/Berlin time ideally)
Willing to relocate: likely not, perhaps within Germany especially back to Berlin
Technologies: Rust, Go, C++, Linux, WASM, SBOM
CV: https://hensel.dev/about/cv
Email: see CV
I'm a software developer about to finish my MSc (CS) looking what interesting work might be out there.I believe she is citing the PDF she links, where only an archived version is available right now. It seems to be a US-only study, although I don't see any explanation of where participants were from.
Early in my University time I always felt most productive when sketching out my day in Google calendar, then keeping up with that plan and if necessary, adjusting it. For a long time I was envisioning something that would allow me to follow that workflow but without the browser window or telling Google my plans, ideally in the terminal, ideallyer something as nice to use as Vim.
When I sat down to learn Go I decided to make that my project and, although messy, it's become my longest-running (though sporadically developed) personal project.
Realistically, I wouldn't suggest anybody use this except to try it, but for myself it is really useful and a fun project to tinker with sometimes.
There's probably a distinction that I'm not aware of but this is not true for CC0 (as stated also in the FAQ for CC0 on this same website).
If I am understanding the AGPL-3.0 correctly (and assuming that the format is also under the license), I could NOT add an "export to Markwhen" feature to my project without then being forced to convert it to AGPL-3.0. Is this correct?