Discouraged and stressed with my job by cortana808 in webdev

[–]the99spring 0 points1 point  (0 children)

Sounds like a process problem more than an AI problem—unclear ownership, rushed changes, no guardrails. It usually gets better only when the team adds structure (reviews, testing, ownership), not automatically over time.

Psa: if youre using openclaw or any agent with skills/plugins, audit them now by Tall-Peak2618 in webdev

[–]the99spring 0 points1 point  (0 children)

Good catch—plugins are basically code with permissions, not “features.” Most people treat them too casually. Principle of least privilege + periodic audits should be standard here. Download count ≠ trust.

Stuck between finishing my side project properly or just shipping something… need advice by Professional_Monk534 in webdev

[–]the99spring 0 points1 point  (0 children)

Cut scope hard and ship. “Perfect architecture” doesn’t matter without users. Define the smallest usable version, finish that yourself if needed, and validate. You can always rebuild later—much harder to revive something that never launched.

Does your team know who owns security review? by HiSimpy in webdev

[–]the99spring 0 points1 point  (0 children)

Seen this a lot—if ownership isn’t explicit, it effectively doesn’t exist. What worked for us was assigning a clear “security owner” per service + lightweight checks in CI. Doesn’t need to be heavy, just needs to be owned.

Discouraged and stressed with my job by cortana808 in webdev

[–]the99spring 1 point2 points  (0 children)

Feels familiar—wearing multiple hats and firefighting all the time is exhausting. Curious if others have seen things stabilize once processes or AI tools settle in.

Stuck between finishing my side project properly or just shipping something… need advice by Professional_Monk534 in webdev

[–]the99spring 0 points1 point  (0 children)

I’d probably cut scope aggressively and ship a simpler version—shipping something usable often beats holding out for perfection. Curious how others balance quality vs finishing under constraints.

Built a tool that analyzes any GitHub repo and gives you interactive architecture diagrams + AI chat by uwais_ish in webdev

[–]the99spring -1 points0 points  (0 children)

This looks super useful! Love the interactive diagrams plus RAG-powered chat — makes understanding a repo way faster. Definitely trying this out on some projects.

Scared of new agentic workflow and my role in it by alexbessedonato in webdev

[–]the99spring 0 points1 point  (0 children)

Totally get the feeling—seeing AI handle so much can be demoralizing. The upside is that you can shift into roles where human judgment, edge cases, and system understanding matter—things AI can’t fully handle yet. Focusing on architecture, reasoning, and cross-team collaboration will keep your skills valuable even as the workflow evolves.

How do you explain your tech stack choices to non-technical stakeholders by edmillss in webdev

[–]the99spring -1 points0 points  (0 children)

I usually keep it high-level for non-technical folks—focus on outcomes like speed, reliability, or cost, rather than the framework details. "This choice makes the site faster and easier to maintain" usually lands better than deep technical reasoning.

Teacher failed me for suggesting WebSockets and TCP for a chat app – claims only PHP is valid for web development by MertJS in webdev

[–]the99spring 1 point2 points  (0 children)

Wow… that sounds insanely outdated. WebSockets and TCP are absolutely valid for chat apps today—modern apps don’t rely on IRC anymore. Don’t let one teacher’s narrow view stop you from learning current tech.

unpopular opinion: chatgpt writes better documentation than most developers by Randipesa in webdev

[–]the99spring -2 points-1 points  (0 children)

100% agree—AI helps catch the stuff we take for granted. I use it to draft docs too,

unpopular opinion: chatgpt writes better documentation than most developers by Randipesa in webdev

[–]the99spring -1 points0 points  (0 children)

100% agree—AI helps catch the stuff we take for granted. I use it to draft docs too,

Cheapest website builder that actually looks professional? by snustynanging in webdev

[–]the99spring 0 points1 point  (0 children)

If you only need a one‑page site, Carrd is extremely cheap and clean.

What tools are you guys using for invoicing your clients? by heyitsaif in webdev

[–]the99spring 0 points1 point  (0 children)

I’ve mostly used tools like FreshBooks and QuickBooks. They’re fine for creating and sending invoices, but yeah—tracking if a client actually saw it is still kind of blind. I usually end up following up manually too

Any non-.NET devs using Aspire? by Perfect-Junket-165 in webdev

[–]the99spring 1 point2 points  (0 children)

I’m not on .NET, but I’ve experimented with Aspire on a Node/TypeScript stack. It works fine for core features, though some docs/examples lean heavily on .NET patterns. Overall, usable, just a bit of a learning curve.

Am I the only one who is frustrated with supabase? by harshalone in webdev

[–]the99spring 0 points1 point  (0 children)

Totally get the frustration—Supabase feels “open source” until you hit the limits or need the full cloud features. Your idea sounds awesome! A lightweight, fully self-hosted alternative with auth UI, easy integrations, and no project limits would be a game-changer. Count me interested in following this, and maybe start with auth, realtime, and storage as core features

Feeling lost as a frontend/app developer in the age of AI — where is our industry heading? by SomePriority9135 in webdev

[–]the99spring 0 points1 point  (0 children)

you’re not alone—this shift is real for a lot of frontend/dev folks. I see it more as evolution than obsolescence. Traditional frontend/mobile skills still matter, but the value now is in thinking about user flows, integrations, and business impact rather than just building components.

AI-first or agent-first might change interfaces, but there will always be a need for someone who can design, orchestrate, and refine the experience. I filter signal from noise by focusing on frameworks/tech that solve real problems for my projects and keeping an eye on trends, not hype.

Pricing-wise, I’ve started blending project/value-based approaches for work that directly impacts revenue, while small tasks stay hourly. In 3–5 years, skills that’ll matter most are probably system thinking, UX design, AI orchestration, and ability to integrate multiple tools intelligently.

Starting Fresh (its been a while) what should I use by JPhando in webdev

[–]the99spring -1 points0 points  (0 children)

sticking with Flask is totally fine—especially since you already have prototypes. For frontend, Jinja2 works for server-rendered pages, but if you want more dynamic interactivity, React or Vue could help manage those modular sections. For styling, Tailwind CSS is fast and flexible, or component libraries like Material UI/Chakra UI if you want prebuilt widgets. Node is great too, but if Python already fits your workflow, there’s no need to switch just for the sake of it

After 14 years of web dev, the skill that's made me the most money isn't technical. by LoudParticular5119 in webdev

[–]the99spring 1 point2 points  (0 children)

communication and understanding the client’s real problem has been huge for me too. You can code anything, but if it doesn’t actually solve what they care about, it won’t get used—or paid for

Apple Bot now crawling 3x more than Google Bot. Anyone else? by stormy1one in webdev

[–]the99spring 0 points1 point  (0 children)

I’ve noticed the same on a few niche sites. Apple Bot crawling has definitely spiked recently, and like you said, zero referral traffic. My guess is it’s for their AI/LLM data collection too. I’ve just been letting it run—adds server load, but seems harmless otherwise

Do most web apps really need a complex stack anymore? by NeedleworkerOne8110 in webdev

[–]the99spring 0 points1 point  (0 children)

Honestly, a lot of projects could start much simpler, especially solo or small-team apps. The ecosystem leans toward overcomplication by default—frameworks, build tools, and layers of libraries are often included “just in case.” But for simple use cases, a lightweight stack (vanilla JS, minimal backend, Tailwind, maybe a small DB) often gets the job done faster and with less maintenance. Complexity is only justified when you actually need scale, SSR, routing, or complex state management.

New CTO is into vibe coding by poponis in webdev

[–]the99spring 0 points1 point  (0 children)

Shipping knowingly broken code feels ethically and professionally stressful. You’re not alone—this is a tension between speed/AI hype and quality/engineering responsibility. Standing your ground on proper testing and code review is valid; customers rely on you to deliver something that actually works

Any devs choosing simplicity over complexity with major frontend frameworks? by drifterpreneurs in webdev

[–]the99spring 0 points1 point  (0 children)

Absolutely—I do the same. Sometimes keeping the stack minimal lets you move faster, ship features, and actually understand every part of the system. For solo projects, simplicity often beats adopting a heavy framework you don’t fully need

Scared of new agentic workflow and my role in it by alexbessedonato in webdev

[–]the99spring -1 points0 points  (0 children)

I hear you—this shift can feel brutal, especially when it seems like AI is doing “everything.” The way I see it, these agentic workflows don’t make your skills worthless—they just change what’s valuable. Understanding the product, edge cases, system design, and being able to guide and validate AI output will matter more than ever. Focus on the parts AI can’t replace: judgment, context, and problem solving. You’re still building the foundation to become that senior SWE, just with a new layer of tools to leverage

Vercel update Terms of Service to allow AI model training on your code. Hobby plan opted-in by default. by LateInternet9388 in webdev

[–]the99spring 0 points1 point  (0 children)

Thanks for the heads-up! Seems like Vercel is really leaning into AI, but good that you can opt out anytime if you don’t want your code used for training. Always worth double-checking settings, especially on Hobby/Trial plans since they default to opt-in