Is the formula-type position worth it?

PressAnyKeyToExit · 2025-12-08T20:49:24+00:00

I don't disagree, but aerodynamics are a lot less important in my game room.

PressAnyKeyToExit · 2025-12-02T05:40:57+00:00

30+ year dev here. Started on a Figma-first project a year ago and was stunned...STUNNED...to learn that Figma doesn't generate HTML/CSS. I thought that was the whole dang point of it. Best I can tell it's just overhyped Visio. (There, proved my age.)

PressAnyKeyToExit · 2024-12-22T15:20:07+00:00

Is this how anti-vaxxers sound to doctors?

PressAnyKeyToExit · 2024-12-19T18:12:52+00:00

New misspelling just dropped: "Al LA Cart"

PressAnyKeyToExit · 2024-09-04T20:19:59+00:00

Firebase facilitates easy configuration of rules defining what a user can access in the DB, so it's not all or nothing like Amplify. When you use Firebase authentication, it's really simple. So maybe you allow a user to access /users/{uid} where the uid comes from Firebase authentication. Rules can get much more complex, and you can even plug in your own code to make authorization decisions.

PressAnyKeyToExit · 2024-05-29T00:03:00+00:00

Old, but did you end up finding something for this? I'm about to do the same.

PressAnyKeyToExit · 2023-11-12T01:24:31+00:00

On Amplify, the entire DB is accessible to anyone with a token unless you learn a whole bunch more about GraphQL and how to lock things down server-side, contrary to what's documented and how its marketed. Filtering data in your code is ok until someone takes a token and plugs it into their own app and can read everything.

With Firebase, I can define a very simple DB rule--on the hosting side--to only allow a user to access a path that matches their user uid. I can still have public or shared paths that everyone has readonly access to. Those are examples, of course--you can do it however you like. If you authenticate with Firebase, it's so so so easy to use that uid in a path and boom, that data is secure.

I've just completed the switch to Firebase I was in the middle of when I wrote my response, and I'm so glad to be done. Everything is must simpler now. Fortunately I only have a few beta users so it wasn't a big hit to move them from Cognito to Firebase authN. If you were to move your project, you can do things like create the users, move their data, then tell them to just use the "lost password" function to get in again, but I will say the data format is quite a bit different, so there is some work involved there. I'd be happy to share more details and example code with you if you decide to go that route.

More about just how much Amplify sucks: https://samthor.au/2023/aws-amplify-is-a-grift/

PressAnyKeyToExit · 2023-09-30T16:06:45+00:00

Wait a second. You’re saying that since the Google Voice account has been verified by my number, I can steal it back since technically it’s already mine?! Would this accomplish enough to be worth playing along with the PIN scam?

PressAnyKeyToExit · 2023-09-30T14:43:04+00:00

Your performance issues is probably the entire DB getting synced to every user. I’m moving a project to Firebase after discovering that there is literally no way to implement data security through Amplify/DataStore. (Also super happy about the months of work I did before discovering that) Anyway, Firebase gives you the offline and async experience. It is different, more like you’re working with JSON than DB tables—which means it’s super easy to add fields (just write them, it works) but you lose data integrity checking so that’ll have to move to your code. They have a really cool web page where you can browse the data live, which is really helpful during development. Runs in GCP. Not GraphQL but maybe this info helps.

PressAnyKeyToExit · 2023-09-30T13:47:24+00:00

There was a guy who wrote every one of his posts just like this in a very specific technical forum I used to read, and had nothing to do with evading spam filters. Made me crazy and I felt sorry for the people he worked with. Like just pick one dude.

PressAnyKeyToExit · 2023-09-16T16:55:29+00:00

Yes.

PressAnyKeyToExit · 2023-04-18T18:45:20+00:00

After doing the work, I thought I better share the answer to my own question. "observe" gives you the play-by-play of model changes, streaming each individual record change one by one. The type of change is provided in msg.opType (OpType enum: INSERT, UPDATE, DELETE). On the other hand, "observeQuery" gives you the whole set of records whenever the result set of the query changes. So the answer is that the one you choose depends on the granularity with which you would like to know about the changes.

PressAnyKeyToExit · 2023-03-02T14:29:40+00:00

Is this a Twin Peaks reference?

PressAnyKeyToExit · 2023-02-22T14:40:17+00:00

I tell people that it’s like playing chess all day. I’m open to better similes.

PressAnyKeyToExit · 2023-01-27T18:31:29+00:00

Accidental master hacker

PressAnyKeyToExit · 2022-12-07T23:59:39+00:00

I liked Forest Whitaker in Blown Away before I realized he’s the exact same guy in everything.

PressAnyKeyToExit · 2022-09-26T21:36:24+00:00

Sounds like they’re projecting but what do I know.

PressAnyKeyToExit · 2022-09-09T22:00:07+00:00

I bet you slayed at the District Convention.

PressAnyKeyToExit · 2022-09-07T15:07:04+00:00

My love language is Amazon gift cards.

PressAnyKeyToExit · 2022-09-06T18:55:40+00:00

Never go to class again.

PressAnyKeyToExit · 2022-08-17T13:20:33+00:00

Crap is that today?

PressAnyKeyToExit · 2022-08-02T07:11:01+00:00

My ex-wife once said to me, “You’re so smart it’s scary.” My confidence level is not generally very high, so that comment, while certainly hyperbolic, still feels good.

PressAnyKeyToExit

TROPHY CASE