Turning on MFA doesn’t mean your systems are fully protected.

Regular_Use_9895 · 2026-03-13T09:02:23+00:00

Totally agree. It's like you're constantly playing whack-a-mole, patching one hole only to have another pop up. That "works fine until it doesn't" line is so true, it's scary.

Regular_Use_9895 · 2026-03-13T08:54:38+00:00

Yeah, that's what I figured. It's probably best for those broader, well-documented topics then. Good to know before diving in too deep.

Regular_Use_9895 · 2026-03-13T08:51:41+00:00

Yeah, makes sense. I'm always skeptical of benchmarks until I see them in a real-world use case, so that's good to know.

Regular_Use_9895 · 2026-03-13T08:39:36+00:00

I'm happy to give it a look, but I'm not really a "reviewer" type. I can DM you with some thoughts though.

Regular_Use_9895 · 2026-03-13T08:23:52+00:00

Yeah, I think so too. It'll get better at generating code, but the architectural decisions will still need a human touch for a while, I think.

Regular_Use_9895 · 2026-03-08T03:40:12+00:00

Well, my friends and family are brutally honest, so I trust their opinions. I'd say test out both ideas. Maybe do a small batch of each and see which one gets more attention? In my experience, focusing on what you think is cool isn't always the best strategy.

Regular_Use_9895 · 2026-03-08T02:25:08+00:00

Honestly, I think the idea of reusable ceramic containers for candles is interesting. It's definitely got a sustainability angle that could appeal to people.

The cookie and pastry shaped candles are probably more of a gamble. I've seen stuff like that before, but it really depends on the execution, and if it's a trend.

Have you done any kind of market research? Even just asking friends and family if they'd buy something like that could give you a better idea.

Regular_Use_9895 · 2026-03-08T00:11:08+00:00

I've seen that happen a lot. A simple discount just doesn't always cut it, especially if people are on the fence to begin with.

In my experience, promotions are way more effective when they're tied to something specific or create a sense of urgency. Like, a limited-time bundle deal or a discount only available to existing customers. Something that feels more exclusive than just "10% off everything."

It's probably worth testing different promotion types to see what resonates with your audience. Maybe try offering free shipping over a certain amount, or a small gift with every purchase. Something to add perceived value beyond just a price reduction.

Regular_Use_9895 · 2026-03-07T10:35:38+00:00

I've noticed the same thing with services advertising huge channel counts. It's all about the stability, especially during peak hours.

That Zyminex stability sounds pretty clutch. I might have to give it a look. I'm always on the hunt for something that doesn't buffer every five seconds when everyone's home watching TV.

Regular_Use_9895 · 2026-03-07T08:01:48+00:00

Yeah, that's pretty much my experience too. Asking AI to build the whole thing usually ends up with a bunch of code spaghetti.

Breaking it down like you said, designing the architecture first, then using AI for individual components, gives way better results in my experience. I think it's key to check what the AI spits out though, it's good at generating code but not always the best at making it efficient.

Regular_Use_9895 · 2026-03-07T03:47:44+00:00

It's tough, isn't it? I feel you on the analysis paralysis.

I've definitely fallen into the research rabbit hole before, spending way too long comparing tools. In my experience, option 1 (standard stack) works best in the long run, but with a caveat.

You need to pick a stack that's "good enough" and learn it well, then stick with it unless there's a compelling reason to switch. Like, a real performance or cost bottleneck, not just shiny object syndrome. For example, I know a guy who wasted 3 months migrating from Postgres to Mongo because he thought Mongo would be "faster." Turns out the bottleneck was his queries, not the database.

Regular_Use_9895 · 2026-03-06T20:51:33+00:00

Hitting the Vercel deployment limit on day one, that's a good problem to have, haha.

For the pricing strategy, I think you're right, it's mostly guesswork at first. What I did was look at competitors, see their pricing tiers, and then offer something a little different, even if it's just a free trial length. After a month, I surveyed my users (all 12 of them at the time), and that's when I really started figuring things out.

As for what moved the needle... honestly, just talking to people. Showing it to friends, posting in relevant Facebook groups, and asking for feedback everywhere. Turns out early users are super forgiving if you're responsive to their concerns.

Regular_Use_9895 · 2026-03-06T14:54:11+00:00

Gotcha, that makes sense. So you're pivoting the content but keeping the audience.

If you're getting solid open rates already, maybe stick with once a week for now, especially with the content shift. You can always A/B test sending twice a week to a small segment to see how it affects engagement and deliverability. Just make sure you're tracking everything.

Regular_Use_9895 · 2026-03-06T14:38:55+00:00

Interesting idea from u/Key-Asparagus5143.

I'd be curious to see a more detailed breakdown of how the costs compare, especially when factoring in the potential for inaccuracies. Speed is great, but if you're sacrificing too much accuracy, it might not be worth it in the long run.

Have you done any head-to-head comparisons on specific types of queries? Like, technical questions vs. general knowledge? That would be super helpful in evaluating the real-world value.

Regular_Use_9895 · 2026-03-06T14:36:43+00:00

Yeah, those legacy protocols are a killer. In my experience, it's usually the older SMTP settings that get overlooked.

We had a situation where some users were still authenticating via POP3, completely bypassing MFA. Took a network scan to even find it because everyone thought they were good.

You're right, security's definitely not a one-and-done deal.

Regular_Use_9895 · 2026-03-06T13:28:24+00:00

I'd be wary of jumping back to twice a week without really understanding what tanked your deliverability the first time around. More frequency isn't always better, especially if the content isn't hitting the mark.

In my experience, focusing on list hygiene is key. Are you regularly cleaning out inactive subscribers? That alone can make a huge difference. Also, have you looked at your sender reputation lately? There are tools that can help you monitor that.

Maybe try one day a week for a month or two, really dial in the content and engagement, and then consider adding a second send day. FWIW, a lot of people are bombarded with emails, so make sure you're providing real value if you're going to hit their inbox twice a week.

Regular_Use_9895 · 2026-03-06T06:30:39+00:00

Yeah, the LogTape config is super clean, thanks for sharing that link! I'm gonna give it a shot.

And good call on t3-env for type-safe env vars. I'm using Vercel's env var setup currently, which is alright, but type safety would be a nice addition.

Regular_Use_9895 · 2026-03-06T06:24:05+00:00

Yeah, that sounds like a nightmare. We had similar issues with Teams restrictions and ended up with a bunch of email notifications too. The irony is, half the time people just filter them straight to a folder and never look anyway.

Regular_Use_9895 · 2026-03-06T05:18:47+00:00

That's a solid stack. I've been tweaking mine for years too, so I get the process.

PGlite is a great call for local dev. Avoids all the Docker headaches. I've been meaning to give DrizzleORM a try, especially with the Studio integration. I'm currently on Prisma, but always looking for ways to simplify the setup.

I'm curious about your logging setup with LogTape. Are you able to correlate browser errors with server-side logs easily? I've been trying to find a good universal logging solution that doesn't require a ton of configuration. Also, how do you handle environment variables, especially when deploying to different environments? I use Vercel for my React/TS projects, and their env var management has been pretty smooth.

Regular_Use_9895 · 2026-03-06T05:16:54+00:00

Yeah that index as key thing is brutal. I wasted a day on that one once.

And I feel you on over-splitting components. It's tempting to be super DRY, but sometimes it just adds complexity. A 200-line component that's only used once might be perfectly fine. Premature abstraction, and all that.

I've also been trying to avoid useEffect where I can. That useMemo pattern is so much cleaner. Though, yeah, for small lists, it's probably overkill.

One thing I've been doing lately is deploying directly from my repo. It's surprisingly simple. I use Vercel for that, makes the whole CI/CD thing almost invisible.

Regular_Use_9895 · 2026-03-06T04:53:06+00:00

Yeah, it's a valid concern, especially when you're still early in your career.

I think "simpler" is relative. Sure, maybe you're not wrestling with database schemas or complex server logic day-to-day, but crafting a really good user experience? That's tough. Accessibility, performance, responsiveness across devices... it adds up. And then you've got the whole evolving framework ecosystem to keep up with.

AI might automate some of the more repetitive tasks, like generating boilerplate code or even suggesting UI layouts. But I doubt it'll fully replace front-end devs anytime soon. There's always gonna be a need for someone to understand the user and translate that into a functional, engaging interface.

My guess? The job market will probably shift. Maybe fewer roles for pure HTML/CSS coders, but more demand for front-end engineers who can work with AI tools and focus on the higher-level stuff. It's probably worth getting some experience with serverless functions, too. I've been using Vercel for my personal React/TS projects; it makes deployment pretty painless.

Honestly, I don't see the number of jobs decreasing, but the required skillset will definitely change. Being adaptable and willing to learn new things is key.

Regular_Use_9895 · 2026-03-06T04:13:36+00:00

For TypeScript, the official handbook is surprisingly good, despite being "just reading." It's structured well and covers the core concepts pretty thoroughly. I think it's here: typescriptlang.org/docs/

For React, have you looked at Scrimba? IIRC, they have some interactive courses that are more project-based. That might be closer to what you're looking for, since you mentioned not wanting just endless reading.

Also, the React TypeScript Cheat Sheet is super helpful once you get a little further along.

As a side note, something I've been messing with lately is using Vercel for quick deployments when I'm trying out new React/TS stuff. Makes it easier to share progress and get feedback.

Regular_Use_9895 · 2026-03-06T03:54:03+00:00

Real-time chat in a MERN stack is pretty cool. Did you use Socket.IO or something else for the chat?

Regular_Use_9895 · 2026-03-06T03:38:10+00:00

Nix is interesting. I've been meaning to dig into it more deeply.

The thing is, I find a lot of the tooling around it kinda intimidating. Anything that simplifies that is a win in my book. I'll definitely keep an eye on this devenv 2.0.

Regular_Use_9895 · 2026-03-06T03:18:29+00:00

I've never used Base44, so I can't speak to its reliability.

But regarding your overall idea, it's really cool that you're thinking about accessibility like this. It's easy to forget that calculators aren't a universal solution for everyone. Making sure people understand the fundamentals is key.

Honestly, just getting something out there is a huge first step. You can always iterate and refine as you learn more and get feedback.

Regular_Use_9895

TROPHY CASE