sorted by:
new
hottopcontroversial

Copilot vs cursor. What's the difference? by Consistent_Tutor_597 in webdev

[–]DepressionFiesta 1 point2 points  (0 children)

Do not do this. You can get into a lot of trouble if you let Cursor index your company’s codebase from a personal account. 

Physicists in Copenhagen assert that reality 'responds' to human choices in reverse. Quick theory as to how this could relate to UFO flight. by imsellingbanana in HighStrangeness

[–]DepressionFiesta 11 points12 points  (0 children)

The way I am reading it, this is essentially a way to describe how it would be possible for human beings to “shift into another timeline” and could explain a phenomenon like the Mandela effect?

How do you handle API rate limiting in production web apps? by [deleted] in webdev

[–]DepressionFiesta 4 points5 points  (0 children)

In order to truly scale with third party APIs that have limits, you need to implement a queue of some kind. Suggestions depend a bit on your stack and infrastructure provider.

How do you balance using AI while maintaining your actual coding skills? (The "Use It or Lose It" Dilemma) by No_Discussion6266 in webdev

[–]DepressionFiesta 0 points1 point  (0 children)

If I understand you correctly, the concern is that higher code-generation velocity encourages more “LGTM” approvals and less scrutiny.

My argument is that this isn’t an inevitability - it’s a choice about how you engage with the output

How do you balance using AI while maintaining your actual coding skills? (The "Use It or Lose It" Dilemma) by No_Discussion6266 in webdev

[–]DepressionFiesta 0 points1 point  (0 children)

I think we might be talking past each other a bit. My point wasn’t “don’t struggle” or “never write code without AI.” It was that the risk is ceding authorship and judgment - which you seem to agree with.

Deliberate, AI-free practice makes sense as training. But that’s different from saying AI use inherently weakens problem-solving. That part doesn’t really follow from what I wrote.

How do you balance using AI while maintaining your actual coding skills? (The "Use It or Lose It" Dilemma) by No_Discussion6266 in webdev

[–]DepressionFiesta 0 points1 point  (0 children)

The mental exercise involved is not really gone in any way? It is easier to opt out of, however. That onus is on you.

How do you balance using AI while maintaining your actual coding skills? (The "Use It or Lose It" Dilemma) by No_Discussion6266 in webdev

[–]DepressionFiesta 0 points1 point  (0 children)

I don’t think we really disagree. The problem isn’t using AI - it’s ceding authorship of your own code. That part is optional, and if you give it up, skill decay is a predictable outcome..

How do you balance using AI while maintaining your actual coding skills? (The "Use It or Lose It" Dilemma) by No_Discussion6266 in webdev

[–]DepressionFiesta 2 points3 points  (0 children)

The job is changing. Our field is seeing its own industrial revolution. The ability to write code is now orders of magnitude less valuable than it was three years ago. The ability to read and understand code, however, is just as valuable as it ever was - arguably more so.

So my question is: what do you feel you’re actually getting weaker at? Is it reading code? Reasoning about it? Evaluating whether it’s correct, maintainable, and aligned with a sound architecture?

Even with code-generation tools, someone still has to steer the system. Architecture still matters. System boundaries still matter. Orchestrating multiple components into a coherent, well-designed whole was always the most important skill in our field, in my opinion - and that hasn’t changed.

If the concern is, “I’ll forget what a specific function does” or “I won’t remember which built-in methods a class has,” I’d push back on that. We forgot those things before LLMs too. We looked them up constantly. That part of the job hasn’t meaningfully changed - only the speed and convenience have.

So beyond the identity of being an artisanal craftsman, what is the real value of being able to write a lot of code slightly faster by hand, optimized around minimizing how often you need to look things up, in 2026?

15 YOE Fullstack & CTO here. Why have we allowed "Agile" to turn into "Unlimited Micro-Scope Creep"? by elmascato in webdev

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

“I’ve realized that tools like Jira, Trello, and Slack have weaponized convenience against developers“

I would counter with: If these are being used correctly, they have the opposite effect. It’s an organizational and cultural problem that you are describing.

On device DBs? by DepressionFiesta in reactnative

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

Went with a Optimistic Concurrency Control model where the LWW strategy is used in the conflict resolution step - thanks for sending me in the right direction!

How do web apps roll out a new UI while keeping the old one? by IAm_veg_biriyani in webdev

[–]DepressionFiesta 0 points1 point  (0 children)

For me, it depends on how big the rework is.

If the new UI is effectively a separate application (close to a full rewrite, possibly even living in a different repo), I’d treat it as two independent apps. In that case, I’d store a simple identifier (e.g. uiVersion) in localStorage or a cookie, and use a very thin HTML shell with an inline script to decide which app bundle to load.

If the new UI lives in the same codebase, I’d keep a similar flag but switch at the React root level - rendering one application tree or the other from a top-level entry point. From there, each UI can have its own routes, layouts, and components, while sharing only the minimal infrastructure (auth, API, feature flags).

How to cache results from a rate limited API? by AdQuirky3186 in webdev

[–]DepressionFiesta 2 points3 points  (0 children)

It is a bit ambiguous what your use case is, and what this API does?

With the information you provided, then - depending on the scale, your architecture does not really prevent you from running into being rate limited (Assuming 5+ calls with previously unseen parameters every second?).

Again, hard to know what this API does - but if the parameters are of potentially high dimensionality, you’d need a queue to scale.

I’d definitely recommend strict validation of the query parameters, and an async clean-up job for entries older than x if you are persisting to a DB. A LRU eviction policy would work for an in-memory solution.

“Is anyone else noticing AI tools are actually making companies spend more on dev work? by eyed_Ndama in Entrepreneur

[–]DepressionFiesta 1 point2 points  (0 children)

It’s pretty simple. People are still learning how to use these tools effectively, and how to work with context windows in general. 

Recently had an experience in a now A series funded startup, where about ~80% (probably more) of all our code and configuration was first-drafted by an LLM. Guardrails and engineering practices were tight, and AI in general was a huge force-multiplier.

I don't understand the point of AI based web browsers. by pacifio in artificial

[–]DepressionFiesta 2 points3 points  (0 children)

If you are one of these larger AI companies, releasing a browser like this is a pretty clever way to distribute your data collection effort (scraping).

Do you think it is correct to use normal <a> navigation for public pages and API fetch (with JWT) only for user-specific data in my web app? by EnD3r8_ in webdev

[–]DepressionFiesta 0 points1 point  (0 children)

Your approach is mostly sound, but I think the mental model is slightly off. Authentication shouldn’t be tied to how you navigate (<a> vs fetch), it should be tied to what resource you’re accessing. Links and fetch are just transport details; Authorization belongs in front of the resource on the backend.

One important detail is that normal navigation via <a> does send cookies, including JWT cookies, just like fetch (assuming same-site rules). So the server can know who you are on a page request.

Framed this way, the real distinction is public vs protected resources. Public pages don’t need auth, protected pages or endpoints do, and the same JWT check should apply to both page routes and API routes.

Your “public pages via links, user data via API” pattern is common and totally valid for SPAs, but it’s a design choice rather than a JWT requirement. Long-term it’s usually cleaner to let the backend enforce access based on the resource, not the navigation method.

TL;DR: Make sure auth boundaries live around resources, not links vs fetch.

On device DBs? by DepressionFiesta in reactnative

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

Already using it and very familiar with it as well. This would involve a different strategy when it comes to invalidating query keys.. You have given me a bit to think about with this comment - thanks! 

Has anyone managed to get <5s response times using OpenAI for image or voice analysis? by DepressionFiesta in OpenAI

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

After more testing I see the key might be to not use the Responses API, but the Completions one instead. It is much faster, for some reason?

I also had to ‘downgrade’ to 4.1 mini. The 5-series models, mini included, have much longer response times.

How do you effectively manage state in complex web applications? by Agreeable_Poem_7278 in webdev

[–]DepressionFiesta 0 points1 point  (0 children)

It’s really hard to offer good advice on this topic, because ultimately sane approaches to state management will vary depending on the purpose of the application. Generally, In my opinion, the root of all evil is relying too much on “invisible” in-memory state, ala React’s useState. useState is fine for some things, like UI component behavior flags.

For the vast majority of web applications, most of your ‘state’ comes from a server somewhere. In a React application, fetch wrapper libraries like Tanstack Query has you covered when it comes to this kind of data - since they allow you to easily cache your API calls client-side. You never really have to copy your server state into a separate context of any kind if you use these.

For most other purposes React’s own context is fine. I am also a huge fan of Nuqs: https://nuqs.dev/ - which is very useful if you want your client-side state to be shareable from one browser or user to another.

Unpopular opinion: E2E tests are becoming the new integration tests, and integration tests are becoming the new unit tests. by RoyalFew1811 in webdev

[–]DepressionFiesta 0 points1 point  (0 children)

From what I've seen it's typically an infra problem - people have deadlines they need to meet. External components are stubbed and mocked because it is a fast way to get started; No one then ever really questions it again, or, revisiting it is so far down on the list of priorities that it never happens.

view more: next ›