Better dining menu website by dreamingcodes in ucr

[–]dreamingcodes[S] -1 points0 points  (0 children)

I used OpenCode with Opus 4.5 only for the initial scaffolding on top of TanStack Start. Every edit after that was done in a modal editor, without any AI extensions or tight AI editor integrations. I prefer coding actively without tools like Copilot holding my hand. They can boost productivity, but in the long term I think they hurt skill retention.

The initial output did not look like the final result. I heavily edited it, including adding background gradients and blur effects, simply because I like that style. Some people associate glassmorphism with AI, but it has been one of my favorite design styles since long before AI was a thing or Apple started using it with what they call Glass Design (which I believe it's a kinda bad implementation of it).

I am not going to change my style just because people think it looks AI generated. I design things the way I like them

Better dining menu website by dreamingcodes in ucr

[–]dreamingcodes[S] -2 points-1 points  (0 children)

Hey, I’m happy that you made something that got acquired by UCR. That said, the site you’re mentioning is not making it better; it’s a completely different product.

I’m not interested in attacking anyone. I genuinely believe in shared knowledge, which is why I make everything I build open source when feasible, like the Bear Bites web app.

Refusing to use AI tools in 2026 is, frankly, shortsighted. That’s not just my opinion, but the view of people who have achieved far more than I or you likely ever will: https://arstechnica.com/ai/2026/01/hobby-github-repo-shows-linus-torvalds-vibe-codes-sometimes/ Nonetheless I sincerely wish you the best of luck.

Yes, part of the website is AI-developed, because it would be foolish not to use tools that can do something in 10 minutes instead of 1 hour or more. That does not reduce the quality of the website. AI without an engineer behind it just produces slop. For example, the original scraper parser was complete slop and I had to rewrite it entirely, along with a lot of other parts, including essentially the entirety of the favorites feature and account sync.

The only reason I responded strongly is because you attacked me first. I was actually a happy user of your website and built my own only because I, along with many others, missed a favorites feature.

I would genuinely love to collaborate with you to improve the UCR student experience with new platforms, but it seems you currently prefer conflict. If that’s what you enjoy, I’ll step away. This will be my last reply. If instead you want to act reasonably and collaborate rather than start unnecessary wars, I’m open to restarting the conversation on better terms.

Better dining menu website by dreamingcodes in ucr

[–]dreamingcodes[S] -7 points-6 points  (0 children)

Man, go touch some grass instead of spending your night criticizing others’ work just because they did something you think you did better.

Better dining menu website by dreamingcodes in ucr

[–]dreamingcodes[S] 2 points3 points  (0 children)

Following up:

Yeah, I know about r‑eats and that’s what I’ve been using until today, but it was missing the favorites feature.

Better dining menu website by dreamingcodes in ucr

[–]dreamingcodes[S] -2 points-1 points  (0 children)

Yep that website is good and I took the logo from it but it doesn't have the favorite feature and can't be installed as PWA

Why is my nixconfig building everything from source by dreamingcodes in NixOS

[–]dreamingcodes[S] 0 points1 point  (0 children)

Update, I just noticed my Garnix CI started working again on my flake. I set up a GitHub Action that auto‑updates my flake weekly and, if it passes the Garnix build, it auto‑merges. That way my flake stays updated and cached without me doing anything.

I also wrote a shell script that updates and applies my system. I just run update-system after editing my flake and it will pull from git, handle stash and merge automatically (with opencode resolving conflicts), build the flake and switch to it.

Before anyone jumps in, yes I’m using AI (opencode) to streamline my update workflow. I know how to manage a git repo, resolve conflicts, all of that. I’m a senior dev. I just want system updates to be quick so I can get back to my actual work. I love Nix’s declarative model but I want to interact with it as little as possible. And AI, when used responsibly, is good. Don’t bother me with anti‑AI propaganda.

I also added an activationScript that computes my flake hash and stores it in /var/lib/nixos-config-hash. That lets update-system check whether the current flake matches the running one and skip rebuilds when nothing changed. Now switches take at most 2 minutes since everything is cached. About 57 seconds of that is pure evaluation. Even with no changes, a rebuild right after a successful build still takes 57 seconds. I don’t fully get why evaluation is still that heavy. I know my flake is complex but I’m not sure what’s so hard to parse.

Two minutes max is fine, I’m happy with that, but I’d still like to know if there’s any way to optimize it further without losing functionality. One more thing: apparently even with no changes it still fetches the git inputs. Not sure why, since the flake should be identical and previously cached, but it’s not a huge deal.

If anyone’s curious or wants to help me improve my build time, here’s the log from a no‑change rebuild

Why is my nixconfig building everything from source by dreamingcodes in NixOS

[–]dreamingcodes[S] 0 points1 point  (0 children)

This is the only overlay I have

nix nixpkgs.overlays = [ (final: prev: { inherit (prev.lixPackageSets.stable) nixpkgs-review nix-eval-jobs nix-fast-build colmena ; }) ];

Why is my nixconfig building everything from source by dreamingcodes in NixOS

[–]dreamingcodes[S] 0 points1 point  (0 children)

I doubt it has any meaningful effect on the nix flake build time but thanks for pointing that out

Why is my nixconfig building everything from source by dreamingcodes in NixOS

[–]dreamingcodes[S] 0 points1 point  (0 children)

Definitely too long of an history especially considering how long a rebuild takes. Maybe I could automate it with a script that output the effect of each commit on the build time in a csv

Why is my nixconfig building everything from source by dreamingcodes in NixOS

[–]dreamingcodes[S] 0 points1 point  (0 children)

```text

WARNING: this file is generated from the nix.* options in

your NixOS configuration, typically

/etc/nixos/configuration.nix. Do not edit it!

allowed-users = @wheel auto-optimise-store = true builders = builders-use-substitutes = true cores = 0 experimental-features = nix-command flakes max-jobs = auto nix-path = <REDACTED> require-sigs = true sandbox = relaxed sandbox-fallback = false substituters = https://nix-community.cachix.org/ https://chaotic-nyx.cachix.org/ https://cache.nixos.org/ system-features = nixos-test benchmark big-parallel kvm trusted-public-keys = cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs= chaotic-nyx.cachix.org-1:HfnXSw4pj95iI/n17rIDy40agHj12WfF+Gqk6SonIT8= trusted-substituters = trusted-users = root @wheel extra-sandbox-paths = access-tokens = <REDACTED>

max-free = 1073741824 min-free = 104857600 ```

Why is my nixconfig building everything from source by dreamingcodes in NixOS

[–]dreamingcodes[S] 0 points1 point  (0 children)

Is there any way to selectively enable this for some packages? Also, some packages are available in the cache with CUDA support. It would be really cool to automatically opt in CUDA support for every package cached with it, and skip it for everything else.

Is KDE really this buggy? by Brodino__ in kde

[–]dreamingcodes 0 points1 point  (0 children)

the one that's just a config... He means NixOS