Professional software engineer, musician, gamer, stoic, democratic socialist
I definitely cannot get behind the “no recursion” rule. There are plenty of algorithms where the iterative equivalent is significantly harder and less natural. For example, post-order DFS.
I guess maybe when lives depend on it. But they should be testing and fuzzing their code anyway, right?
EDIT: I can’t even find in the NASA PDF where it mentions recursion.
deleted by creator
SQLite was literally invented within the US military.
This song is everywhere if you look. I heard it in Shutter Island first.
If you go this route I recommend installing Kodi + Jellyfin Plugin + Kore Android App. You can control everything from your phone or laptop.
Copium. We’re well beyond the days when anything under 60 FPS is not cheap and lazy craftsmanship.
This would be more believable if Elon paid his cloud bills.
It’s the first sentence of the article.
Clutch team killing in Rainbow Six Siege. A rare occurrence but so much adrenaline.
Hillcrest in The Last of Us 2. Never have I had so much fun trapping and hunting people down. It really brings out the psycho killer energy.
It’s almost 30 years old. Not to knock cURL, it’s a staple for sure.
HTTPie and xh claim to have a more intuitive UX. If the functionality is comparable, I choose tools written in memory-safe languages by default.
xh is a nice modern alternative.
deleted by creator
Organizationally, you don’t want your API handler to care about implementation details like database queries. All DB interaction should be abstracted into a separate layer.
Generally API handlers only care about injecting any “global” dependencies (like a database object), extracting the request payload, and dispatching into some lower-level method.
None of this requires generic code. It’s just about having a clear separation of concerns, and this can lead to more reusable and testable code.
that’s a git problem, not Windows.
I use Git, and I don’t use Windows. I have no problems. Sounds like… a Windows problem?
You are never guaranteed to be able to do anything during a crash. You are better off handling these kinds of edge cases in a recovery phase during the start of your app.
Has a simple backup and migration workflow. I recently had to backup and migrate a MediaWiki database. It was pretty smooth but not as simple as it could be. If your data model is spread across RDBMS and file, you need to provide a CLI tool that does the export/import.
Easy to run as a systemd service. This is the main criteria for whether it will be easy to create a NixOS module.
Has health endpoints for monitoring.
Has an admin web UI that surfaces important configuration info.
If there are external service dependencies like postgres or redis, then there needs to be a wealth of documentation on how those integrations work. Provide infrastructure as code examples! IME systemd and NixOS modules are very capable of deploying these kinds of distributed systems.
This type of shit makes me aware that there really are devs that don’t care about efficiency and will spend weeks on some really novice shit because their tools and skills are bad.
Silverbullet is nice
I would take a look at LEAN4.
https://lean-lang.org/functional_programming_in_lean/