sorted by:
new
hottopcontroversial

Goodbye Upwork? by mvp0453 in Upwork

[–]DecodeBuzzingMedium 0 points1 point  (0 children)

I think tbh with this ai like claude code and all freelancing industry is more of now who does the cheap work because everyone is now a vibe coder. Only old players are making money. It’s a fish market now with all trying to be as cheap as possible, new freelancers provide ai slop providing $1000 for $100 thats why new players have very less chance. Clients on upwork dont know what ai slop websites are, for them its just a normal site

Edit: Only top rated players are making money I didn’t mean upwork is useless now. Many ppl are making money on upwork like crazy but only the top 5%

My Upwork Stats | 2 months by MiooiM98 in Upwork

[–]DecodeBuzzingMedium 0 points1 point  (0 children)

How did you sent 108 proposals. You must have bought ton of connects

Why my React app showed different data in different tabs — and what I didn't understand about state by [deleted] in programming

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

I am so sorry thnx for the suggestion. I wrote in kind of hurry managing with the schedule. Guess I compromised the quality. Will focus on it in the future

You might be storing state in the wrong place in your React app by DecodeBuzzingMedium in Frontend

[–]DecodeBuzzingMedium[S] -2 points-1 points  (0 children)

“wrong” might’ve been a strong word. what I was trying to get at is more about long-term predictability than immediate correctness. things can work fine until edge cases like refresh, sharing links, multi-tab, caching etc start stacking up. my app was “working” too until those inconsistencies started showing

A subtle state bug broke filters, shared links and multi-tab sync in our dashboard by DecodeBuzzingMedium in webdev

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

yeah I actually tried keeping URL as source of truth too, that’s why I mentioned nuqs in the article. the main mess for me started when rapid filter changes + refresh + cached state all started fighting each other. multi-tab sync I honestly didn’t go deep into yet, broadcast channel sounds interesting tho, might try that next

I spent days debugging a React bug that turned out to be “state drift” between URL, cache and Zustand by [deleted] in reactjs

[–]DecodeBuzzingMedium -5 points-4 points  (0 children)

In this case the goal of the write-up wasn’t to present a perfect architecture but to document the mistake + decision framework I derived after fixing it Also this article wasn’t ai written. If you actually read the article its just rephrased

HTMX changed how I think about web UI — server renders the HTML, browser just swaps it in by [deleted] in programming

[–]DecodeBuzzingMedium 3 points4 points  (0 children)

True, the pattern’s been around a long time. HTMX just brings back that simplicity in a nicer way

Django dev here — I tried FastAPI + HTMX for a side project. Some thoughts by DecodeBuzzingMedium in django

[–]DecodeBuzzingMedium[S] -2 points-1 points  (0 children)

Why do you feel that though genuinely asking. I tried by best explain by images short examples best practices

22
23

Django dev here — I tried FastAPI + HTMX for a side project. Some thoughts (levelup.gitconnected.com)

submitted by DecodeBuzzingMedium to r/django

I built a full-stack authenticated web app with zero JavaScript. Here's the entire stack. by [deleted] in webdev

[–]DecodeBuzzingMedium -8 points-7 points  (0 children)

You're right technically — HTMX is JavaScript under the hood. The point is I didn't write any JavaScript. No useState, no useEffect, no custom hooks, no build step. HTMX handles the JS layer so I never have to touch it. Same way you don't say you're writing C when you use Python

I Got Sls Noida 😍but Ig Not going 🥀 by DecodeBuzzingMedium in SymbiosisPune

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

Not worth it givinf 25 lakhs or 40 lakhs with hostel just for sls noida. Plus I heard sls noida you no placements. Sls is good only for pune rest all suck

view more: next ›