jdsleppy

SvelteKit is very alive and is the way svelte apps are made generally, not like next.js which is more optional.

You almost perfectly recreated the styling of Astro Space UX Design System https://www.astrouxds.com/

Reading that other people donated helped me to do so. I'm writing this to help other people get over the decision hump.

I self-host his [name redacted] on a fun site of mine. I like this style of app: small, simple binary that can share a machine with lots of other things.

I use it to allow a ?next={url} query parameter in the redirect so I can send users to the page they originally wanted to visit. It becomes more important the faster the access tokens expire because a user can reauth multiple times in a session.

The other way might be to put that URL in redis or something, maybe that's better?

I think it would be easier to read if the line spacing of the titles were much smaller, and similar design tweaks to help the eye group and prioritize information. It's a little mentally painful to read compared to the old styling.

I recently had to learn OIDC which is the standard for auth that most people really mean when they say OAuth now, I think. I learned by implementing (using Keycloak) and most importantly by reading the OIDC specs. It may seem intimidating, but the real core of it is not that large.

It's a topic I'd be interested in writing more about, and I'm happy to start here if you would find it useful.

Why go to the doctor to be told it's a flu or a cold? There's nothing to do but treat yourself well and wait, right? I wonder what portion of visits are for common viruses.

You aren't tied to only referencing things from JS: you can have Webpack emit a manifest file with a JSON object mapping from the original filename to the hashed one. Then oldschool web app code can reference these fingerprinted files using the manifest.

To fingerprint files you normally wouldn't import in JS, you can 1) import them in JS anyway just for the bundling side effect or 2) use a Webpack copy plugin to copy all font files, for example, to the build directory and fingerprint them.

It's fine if you don't want to call it a waste of bandwidth, but bandwidth is definitely still used because browsers don't share caches between domains https://www.stefanjudis.com/notes/say-goodbye-to-resource-ca....

I suppose you could test your system including the Keycloak configuration to make sure things work as expected after a TF change. You probably want to be doing that anyway, though. It's a fairly comprehensive Terraform provider under active development, I recommend it.

There's a good Terraform provider for consistent configuration across environments, too.

I think you misunderstand GP's post on a low level, words-and-their-definitions level. The story has a timeline to it, and during the hometown portion they were not wealthy and not discussing wealth yet. Read it more carefully.

I'm unable to find the death notes easily. Could you give me a hint?

The comments seem of average pitch to me. I did have to scroll to the bottom to see the more inflammatory ones, but even with those it matches what you get on any exciting topic. Ask devs what they think of golang and you almost get the same!

Has this all been introspection, or are there external resources (like books) you used?

It looks like the largest effect found (from reading only the summary) is how many more adverse effects the Moderna placebo causes compared to the Pfizer placebo.

Given that, I won't regret my vaccinations just yet.

Try web development agencies. You may be able to get on an older project that isn't in such a rush and can be moved along by a part time contractor. That's what I'm doing now. I found the open position on the agency's website.

I noticed that the webapp doesn't show personalized content (or my privacy extensions do a wonderful job). You have to use the mobile app to see the full power.

I know it's not magic, but right now it's not mundane either. I want it to be mundane. Everyone gets raises with inflation. Prices go up, wages go up, and we don't have to worry about falling backwards by sitting still.

Then what's the point of inflation? So people deploy their spare cash in productive ways. That's it. Mundane, no drama, money moves around.

You are (intentionally, I think) unaware of the context of this entire discussion where these are people who aren't comfortable managing their own servers. They don't know what they don't know. They don't want to learn about systemd, sshd, users and groups, apt, ufw, and however many other things needed to run on a VPS.

You got your point across in your various comments.

If you had contact information in your profile, someone might reach out.

But since you don't: what kind of help are you looking for? Web development?

I'm working hourly on a contract where I advised the company I could only work 15-20 hours a week. It can be a win-win I believe, but with tradeoffs for both sides.

I'm able to make the 3-4 hours of work a day be extremely productive. I always deliver in fewer hours than were budgeted for the work. As a contractor, there are no extraneous meetings to slow me down. But I'm still involved in client meetings as needed, understand their needs, and take ownership of the codebase to my immense satisfaction.

It's not very different than working "full time" from home where you might take a walk, run an errand, cook your lunch, etc., but I can flex the schedule even further without any guilt. The change in mindset from "taking a break from full-time work" for an errand versus "I'm not billing this hour, I'll do whatever I want" is empowering.

The negatives: less pay in total for me (but hourly rate can be negotiated), and features might (but won't necessarily) get done more slowly in terms of calendar days.

BTW a typical day might be:

- daycare drop-off 9:30, exercise

- 10:30 shower, chores, life tasks

- 11:45 cook and eat lunch

- 12:30-4:30 work with a break for walking or playing piano

I do some "down time" thinking about problems as I fall asleep at night or on walks.

Nginx config seems like a bottomless pit. It gives me the painful feeling that no matter what I have done with it, there's some security or performance issue still there.

Does this mean I should just stick with a more managed solution? Or is this a common feeling that I should just learn to live with? For my fun projects I use Caddy with mostly default settings.

I've even written a unit test that fails after a certain date with a descriptive message for this purpose. It's maybe more familiar to developers and already has tooling around it.

There's not an example for us to try out on that page? That's cruel.

My favorite is https://www.reddit.com/r/experienceddevs

It's more focused on the people/team/organization/career side. There are zero blog articles and zero newbie questions.

Yes, there are many. https://mission.dev/ is one I've spoken with but haven't had an opening to work with (I think this is the one, they were called GSquad before). When you get past the marketing site and hear from the people, it sounds more like a self-organizing software co-op.

I worked somewhere where one of the considerations for moving from Python to go was a less browsable deliverable (executable vs code). I'm sure they would be happy to obfuscate beyond that.

It's surprisingly easy to stay on the front page for a while.

Anyways, I always enjoy seeing how other people set up this interstitial stuff, the ergonomics, and little scripts. I get a lot of valuable learning seeing other people do things, even things I know how to do (a different way).

As one example, Django handles test parallelism by creating N test databases (on the single test database server) and dividing tests into N runners. https://docs.djangoproject.com/en/3.2/ref/django-admin/#envv...

You could also have multiple Docker containers running DBs.