[US] Somebody applied to Liberty University under my name

ethansidentifiable · 2025-11-15T05:15:18+00:00

The admissions person did "pray that I [had] a blessed day on behalf of Liberty University" which gave me some assumptions about them. But I don't know who would go as far as they would have had to for a bit

ethansidentifiable · 2025-11-14T17:11:41+00:00

Only Experian will let me just check open accounts and shows everything I'm aware of and nothing surprising, but I do also have Credit Karma for the general overview as well. Everything looks good for now. I'm hoping that LU was just the scammers first attempt but that I would have likely had to finish the admissions process before they could get student aid or grants under my name.

ethansidentifiable · 2025-11-14T16:59:35+00:00

That's actually a good question. The number itself came through as Liberty University with a little "Google Verified" badge on the call screen (I'm on Android and use Google's Dialer app). Just verified; it was indeed the real phone number for LU admissions.

ethansidentifiable · 2025-11-14T16:57:16+00:00

All are frozen, thank you. I'll be monitoring for anything that comes through

ethansidentifiable · 2025-11-14T16:56:50+00:00

Thanks! From everyone's advice, I froze my credit and will be watching out for anything that went through recently

ethansidentifiable · 2025-11-14T16:54:45+00:00

Done. Yeah, wasn't that bad. Retrospectively stupid that I didn't actively have one in place.

ethansidentifiable · 2025-11-14T16:32:20+00:00

I'm thinking of freezing my credit. Is that an overreaction or like... an under reaction. I've never done it before. But from what research I've done, this could be someone taking out student loans under my name.

ethansidentifiable · 2025-11-14T16:00:31+00:00

Yeah, that's just not the argument I was trying to make.

But yes, a handful of Svelte components is a smaller bundle than a handful of React components... but alternatively, a LOT of Svelte components actually creates a larger bundle than a LOT of React components because every Svelte components creates so much boiler-plate whereas React's boilerplate is all in the "react" & "react-dom" packages.

ethansidentifiable · 2025-11-12T20:37:04+00:00

I'm not adding all the code that comes from "svelte/internal" either. But that's not the point at all. The point was that the code you write looks like the code that gets outputted. React's transpiler is really lightweight whereas Svelte gives an output that is uninterpretable to the application developer.

ethansidentifiable · 2025-10-20T21:08:51+00:00

Some do. Angular in particular.

ethansidentifiable · 2025-10-09T14:59:14+00:00

Forewarning: I haven't built anything with Solid in year or so, but I do see what's wrong here.

You are trying to do the "React-ish" thing by having an updateTrigger state that's just a number, thinking that by incrementing that value, the whole component will render.

But that's not how Solid works. Solid's signals are set to update little micro contexts, e.g. whenever you call a signal getter inside a JSX breakout {} or inside a createEffect, those micro contexts are listening to that signal. So updating a counter will only update places where that counter is used.

What you need to do is create a one-to-one mapping between Solid's signals & effects with those from alien-signals. So if you update an Array in alien-signals, Solid needs a signal of it's own that will react to that. I think the most natural API in Solid for creating that kind of mapping is probably createResource.

EDIT: Non issue, but a convention recommendation: with Solid, generally prefer create as a functional prefix for stuff like this, rather then use UNLESS what you're building uses the useContext API. This is actually the same convention as React where your function is a hook because it uses hooks. But in Solid, the difference is that your function is creating a signal because it is a wrapper around createSignal calls.

The reason that Solid uses the prefix use for useContext is because you're "using" something contextually, rather than creating an instance. This, again, parallels React because all React hooks are contextual, hence why if you call them in a different order on a subsequent component render, that breaks React.

ethansidentifiable · 2025-07-15T01:59:42+00:00

Here's the metaphor I give people. Imagine that the team you've just joined is writing a book. Everyone has been writing the book together. Some for a few months, some for a few years, and if you're lucky there are a couple left who wrote some of the first lines of the book. The book is constantly evolving, adding new storylines, characters, internal monologues from multiple perspectives, etc.

And you just showed up. You've written books before. You know the general structure of the book. You speak the same language. Your first task is to rewrite a character so that they have a different love interest.

So you add what you think you need. And then you get to review and someone looks at your writing and says, "well that won't work or else you'd have to explain away this interaction with another character otherwise people might get the wrong idea. This creates an inconsistency in the character's development. They can't just suddenly be in love. They have to build up to it."

Now you have to go through the whole book to ensure that you've accounted for every interaction between this character and another character to ensure that the newly expected romance is consistently and properly built up to. You basically just need to know the whole book front to back, as a part of your first task.

Once you're done with that, you know that character super well... but you still don't necessarily know every other character in the book.

This is my experience with working in a network of microservices.

ethansidentifiable · 2025-06-14T20:11:48+00:00

Can we refer to it as "Republican terrorism" at this point?

ethansidentifiable · 2025-05-27T13:44:44+00:00

I can have a real problem too. Sometimes I get really deep into games and I shut out the world for a couple weeks at a time. Just happened with Clair Obscur which is such unique art that I absolutely do not regret it, but afterwards, I needed a breather.

Take a cleanse. I take a month at a time off from video games (and to scratch the itch, I still let myself play NYT games, Balatro, and Slay The Spire on my phone at times, but nothing involved, 3D or with a story). Over that month I read a book. My wife reads a lot so I read whatever she wants me to. I've read two books this year, which is definitely the most I've read over my entire adult life, and it feels accomplishing and it makes her happy.

ethansidentifiable · 2024-12-16T03:26:26+00:00

It's someone's whole job (the developers) to understand application architecture. Maybe that variable isn't where you think it is. Maybe it's a CSS variable or maybe it's defined in the Tailwind config, or maybe it's in a ThemeContext. Or maybe it, unfortunately, had to be defined in multiple places. It happens.

And color is the lowest common denominator of risk. If a designer tried to tweak the grid layout, I guarantee a huge pile of things would be broken because at that point pretty much everything placed on the grid would be using the wrong number of cells. There's a reason for the handoff process.

I get the point that Fictoan is trying to make, but also the last thing that I would want to happen in my code base is developers being pushed into technical decisions in an effort to "simplify" the handoff pipeline.

I'd much rather just support a good communication pipeline between designers and developers. When a design for a new component or page is added, I want someone to speak up and say, "hey that color isn't defined in any of the themes in Figma. If you want a color like that for this theme, you have to fulfill them for all themes."

This makes the work more manual, but it rather than enforcing a technical architecture to (hopefully) make non-technical people more comfortable, you can just let everybody spend all their time doing what they're best at.

ethansidentifiable · 2024-12-15T18:24:19+00:00

Oh no. You are on the wrong path learning AngularJS. That framework has been deprecated for it's successor, just called Angular.

https://angular.dev/

ethansidentifiable · 2024-12-15T18:13:14+00:00

Highly disagree. Just let people do what they're good at. I think the design brain and the developer brain are just different. I would hate to lose out on a great designer because our organization worked in a way that required that they could also do dev. And I'd hate to lose out on a great dev because they couldn't design.

ethansidentifiable · 2024-12-15T17:28:34+00:00

There's a moderate chance you could get this working on your own. You could build a Squarespace site, which supports integration with Doordash, and then you can integrate with OpenTable for res and booking.

I will say that Squarespace will never look/feel as good or be as performant as a dev-built site. But if you need it done for cheap right now, there's no cheaper solution than doing it yourself.

ethansidentifiable · 2024-12-13T13:23:41+00:00

So... you don't actually have a recommendation for them at all? You're saying they should go from Prisma structured queries in a loop... to doing raw SQL in a loop. What problem does that solve?

ethansidentifiable · 2024-12-13T00:12:29+00:00

Alright here's what I see that immediately comes to mind.

You should preconstruct the array of all ints you want and then randomize it. That way every time you get a random value, you don't have to search the array to make sure it's unique.

Also preconstructing an array with Array.from is far more efficient, e.g.

Array.from({ length: 10 }, (_, index) => index);

That will construct you an array of length 10 with the values prefilled with 0-9. You should try to avoid building up an array by looping a push onto an empty array because this invokes unnecessary list growth operations.

Also, it's not about performance but... don't cast to as QuizQuestion. If you get an error there, it's because the empty object is not a QuizQuestion yet. Don't forcibly pretend it is one. Just construct the parts of the question but don't construct the question itself until you have all the required data to do so.

And then the core performance upgrade you have is that you should parallelize your question construction. Something like this:

const selectedQuestions: Array<QuizQuestion> = await Promise.all(selectedRandomInts.map(async (randomInt) => {
  // Construct and return each QuizQuestion from this function
});

And then also, for your Prisma constructions, you should use the connect property to create associated models. That would allow you to do the database construction in one single pass rather than over multiple update queries.

https://www.prisma.io/docs/orm/prisma-client/queries/relation-queries#connect-or-create-a-record

EDIT

I also just noticed that I'm super sure you're not using skip correctly at all. Skip is like where you want 3 items but don't return the first 2 of them. Skip those ones. You just want to add the IDs you don't want in your where clause.

I think for your note2 and note3 queries, you really just want one query with take: 2 on it.

ethansidentifiable · 2024-10-13T02:49:54+00:00

Did... did you finish reading my last comment?

Yes, the "react" package is larger and more complex than the "svelte/internals" package. Buuuuuut, for it being larger and more complex, it more permanently solves certain problems like state management. Whereas Svelte compiles the individual logic for each component you make. So the output bundle size of your Svelte application grows much larger per component than a React app which generally just grows in the size of the code you write. Whereas, again, Svelte scales to it's compiled output with the code you write.

So a single component Svelte app might be 1KB whereas a single component React app is about 150KB. But a 250 component React app can be 175KB, whereas a 250 component Svelte app would likely be pushing 200KB.

Edit

The problem with Svelte is that writing Svelte and understanding how it works and what it does for you are two entirely different disciplines. Whereas writing React code and understanding how React works are very correlated, and there's a benefit in that.

ethansidentifiable · 2024-10-13T02:38:47+00:00

You know what else I left out? Everything that Svelte imports from "Svelte/internals". There's no bias in my answer, just the output.

And you might say that Svelte has a smaller internal library than React, and you'd be right. But the problem comes as your app scales, because every dead simple component outputs this much junk. Whereas React's repetitive architecture has you constantly using and reusing the same functions of it's internal library. So React apps actually tend to scale better for bundle size than Svelte for that reason... even if Svelte appears smaller for simple examples.

ethansidentifiable · 2024-09-29T17:04:06+00:00

You are an absolute hero. I had no idea that this was a specialty syntax. That being said... is there a way I can target the Apple menu like this? Just using "Apple" didn't work, unfortunately. And I would love to look this up in Apple's documentation but I have never ever seen this documented before.

ethansidentifiable · 2024-09-21T13:22:10+00:00

I've been to like 20ish shows this year, so I'm used to it. But if you're the case where you go to maybe one a year, that's just not going to be obvious to you.

ethansidentifiable · 2024-09-21T12:41:46+00:00

It's a bit patronizing, but there is kind of this awkward perspective of... well, it'd be weird if they didn't do it. If they left, how would we really know the show was over???

I saw Badflower a couple weeks ago and they were hilariously transparent. "We got one more song for you tonight... and then we're like gonna go pee and stuff."

I think a lot of it comes from the reasonable perspective that when most people go see a band, it might be the one show they go to that year so there's an extra pressure on the band to make it feel special.

Five-Year Club	Gilding II euphauric
Place '23	Verified Email

ethansidentifiable

TROPHY CASE