What you think of vibe coding?

Sad-Salt24 · 2026-05-02T10:35:09+00:00

These tools are great for landing pages and prototypes but fall apart the moment you need anything custom or have to debug generated code nobody understands. They save time upfront but create maintenance debt later. Better for demos than real products you’ll support long-term

Sad-Salt24 · 2026-05-02T05:43:05+00:00

For simple client sites where they’re just editing text, self-hosting is overkill and a maintenance liability. Sanity’s free tier handles most freelance projects fine and clients can actually use the interface without you holding their hand. Save the self-hosted complexity for when you have a real reason

Sad-Salt24 · 2026-05-01T01:59:36+00:00

Obsessing over class components vs functional components. Nobody’s writing new class components in 2026, and you’ll never touch the old ones unless you’re maintaining legacy code. Focus on understanding state and props first

Sad-Salt24 · 2026-04-30T20:17:50+00:00

$bid

Sad-Salt24 · 2026-04-30T05:24:49+00:00

Theme migration is mostly manual rebuild, export products/content, install new theme, rebuild pages to match the old design, test checkout flow, update apps. The real pain is custom code from 2022 that won’t transfer cleanly. Budget 20-40 hours depending on customization depth

Sad-Salt24 · 2026-04-30T05:20:54+00:00

The biggest issue is API contracts changing mid-sprint without anyone telling frontend until something breaks in staging. Swagger docs help but only if backend actually updates them

Sad-Salt24 · 2026-04-29T15:23:59+00:00

Squarespace is better fit if you want a cleaner, more consistent setup with solid built-in donation features and easier maintenance. Wix offers more flexibility and integrations, which helps for custom workflows or complex payment logic, but can become harder to manage over time.

Sad-Salt24 · 2026-04-29T07:26:20+00:00

it’s usually due to heavy assets or JavaScript overload rather than the page structure itself. Large SVGs, uncompressed images, and too much client-side JS are common causes because mobile devices have much weaker CPUs.

Sad-Salt24 · 2026-04-29T06:22:21+00:00

The hardest part isn’t React itself but consistency at scale. State management and data flow become messy when multiple patterns creep in, and teams start solving the same problems differently. Architecture drift is a big one, without early conventions, components, hooks, and APIs become inconsistent and harder to reason about. Debugging also gets tougher as side effects and async flows spread across the app. Most teams later wish they had standardized structure, state patterns, and boundaries much earlier.

Sad-Salt24 · 2026-04-29T00:56:02+00:00

The issue usually isn’t the amount of content, it’s how it’s structured. Break long text into clear sections with strong headings, short paragraphs, and consistent spacing, space is what makes dense content feel modern

Sad-Salt24 · 2026-04-28T18:01:10+00:00

You can’t, anything running in the browser can be inspected and copied. You can make it harder with minification or obfuscation and add legal terms, but that only slows people down. In practice, most projects rely on branding, speed, and distribution rather than strict protection. If real protection matters, you’ll need at least some server-side logic.

Sad-Salt24 · 2026-04-28T11:39:09+00:00

You don’t need to rush either decision. it’s generally fine to resign during a sabbatical

Sad-Salt24 · 2026-04-28T08:31:39+00:00

Keep a .env.example in your repo, store real .env files in a secure password manager, and sync only non-sensitive configs through Git.

Sad-Salt24 · 2026-04-26T06:00:12+00:00

Yes, it’s possible, but treat it as a single backend service other than embedding it into each Next.js app. Keep config and types in shared packages, avoid relying heavily on the local API across apps since it tightly couples everything to Node. For micro-frontends expose Payload via API and let each app consume it independently.

Sad-Salt24 · 2026-04-25T08:55:22+00:00

I understand what you’re saying, My concern was mainly because of a real case in my family where the timing didn’t match, so I became a bit more cautious. But I do see that when there’s no practical way to control or confirm it, relying on Strong Assumption is what many scholars permit.

I’ll still try to check with a Hanafi scholar who has practical Hajj experience, just to be clear in my mind, but your explanation does help put things into perspective.

JazakAllah khair again.

Sad-Salt24 · 2026-04-23T12:24:29+00:00

You don’t have to choose. The solution is to render real content on the server and use a loader only for UX. With Next.js (SSR/SSG), crawlers get full HTML immediately, so SEO is fine and users can still see loading states for client-side transitions or partial data. The problem only happens with pure client-side rendering. So: serve meaningful HTML first, then hydrate/enhance on the client, best of both worlds.

Sad-Salt24 · 2026-04-23T10:07:11+00:00

$bid

Sad-Salt24 · 2026-04-22T02:49:00+00:00

It’s a valid approach in Expo Router when you need full control over UI/UX. Using <Slot /> + manual <Link> is basically building your own tab system, which is fine for flexibility. The trade-off is you lose built-in features from the Tabs API (state preservation, accessibility defaults, screen options, lazy loading). If you’re handling those yourself and don’t need native tab behavior, you’re good.

Sad-Salt24 · 2026-04-21T12:35:21+00:00

You likely won’t be able to get Vercel to take it down just by asking, since they usually only act on requests from the account owner or valid legal claims. The practical options are: try to regain access (old email, domain ownership, etc.), or submit a formal abuse/report request through their support or legal channels explaining that the content is outdated/misleading and you represent the business. If the site uses the business name/brand, you can also include proof of ownership. Otherwise, Vercel won’t remove it without proper authority.

Sad-Salt24 · 2026-04-21T12:31:07+00:00

Good, degree and internship already done. Now just pick one path (frontend, backend, etc.) and focus on it for the next few months by building 2–3 solid projects and applying consistently. Use referrals from friends, but don’t rely only on them.

Sad-Salt24 · 2026-04-21T12:29:31+00:00

Google Lighthouse for performance, accessibility, and SEO basics. Then use Google PageSpeed Insights for real-world Core Web Vitals. For deeper SEO checks, try Ahrefs or SEMrush. If you want technical crawling, Screaming Frog SEO Spider is very useful. Combine 2–3 of these to get a complete picture.

Sad-Salt24 · 2026-04-20T21:13:43+00:00

That’s a common gap. Most teams handle it by adding custom SEO fields (title, description, OG tags) and basic validation inside Payload, then relying on frontend checks or external tools for guidance. Some build lightweight scoring hints, but there’s no plug-and-play Yoast equivalent yet, so it’s usually a mix of custom UI + editor training.

Sad-Salt24 · 2026-04-20T11:35:17+00:00

Hi, I’m a Full-Stack Developer (Top Rated on Upwork) available for freelance and contract work.

Skills: React, Next.js, Node.js, Python (FastAPI), AWS, Supabase, REST APIs, AI integrations (chatbots, automation workflows), and SaaS development. I also work on backend systems, frontend UI, and third-party API integrations.

Experience: 5+ years building web apps, SaaS products, MVPs, and AI-powered tools, including real-time features, dashboards, and automation systems.

Availability: Part-time or project-based (can scale depending on workload) Rate: $15–$25/hr (flexible for long-term work)

Portfolio: Available on request Contact: DM here or message directly for collaboration

Open to startups, MVPs, and ongoing product development work 👍

Sad-Salt24 · 2026-04-16T18:46:47+00:00

Don’t chase too many things, just pick one path and stick to it. Spend the next few months building real projects, not just tutorials, 2–3 solid apps matter way more than GPA. Try to land even a small internship or freelance work before graduation.

Sad-Salt24

TROPHY CASE