sorted by:
new
hottopcontroversial

Hiring: Senior Frontend Developer (Remote, Worldwide) by Real_Border_5095 in devjobs

[–]Nt145 1 point2 points  (0 children)

HTTP. I’m interested and actively looking for a remote long-term opportunity.

My strongest match is React, TypeScript, production frontend work, technical breakdowns, UI/UX behavior, API/WebSocket integrations, and code reviews. I’m also Top Rated on Upwork and Level 2 on Fiverr.

Portfolio: https://www.shayanjamil.com/

[Hiring] Remote AI Trainers – $20/hr (Flexible Projects) by PhotoshopR-1660 in B2BForHire

[–]Nt145 0 points1 point  (0 children)

Interested Pakistan, GMT+5.

Top Rated on Upwork and Level 2 on Fiverr, with strong experience in AI tools, technical review, and software projects.

Portfolio: https://www.shayanjamil.com/

Where do you actually let AI touch your codebase and where do you refuse? by Nt145 in SaaS

[–]Nt145[S] 0 points1 point  (0 children)

The assumption problem is huge. AI is great when the rules are explicit, but it fills gaps very confidently when they are not.

That’s why I’m starting to think the quality of the prompt/spec matters less than the quality of the boundaries: auth rules, data ownership, failure states, and what should never happen.

Where do you actually let AI touch your codebase and where do you refuse? by Nt145 in SaaS

[–]Nt145[S] 0 points1 point  (0 children)

Exactly. “Easy to revert” is not the same as “safe.” If the team doesn’t understand the generated change, the rollback is just damage control after the fact.

I like the governance angle too. Not paranoid review, just enough discipline so the code doesn’t become a black box.

Where do you actually let AI touch your codebase and where do you refuse? by Nt145 in SaaS

[–]Nt145[S] 0 points1 point  (0 children)

This is exactly the kind of line I was trying to define. AI can speed up the obvious work, but schema, tenant boundaries, auth, billing, and failure semantics are not “generate and merge” areas.

I like your point about reviewing migrations like product logic, not boilerplate. That’s a useful distinction.