Genuine question for backend devs
Why does CORS feel like it's personally attacking you every single time? 😭
Frontend and backend on different origins and suddenly the browser acts like they're enemies
What's the cleanest way you've handled this in production?Drop your approach
Sometime I think about how much time I wasted in my first year of college because of my mental state, I just regret everything I've done. I wish I could go back in time.
During SIH, no one let me join their team.Not because I couldn't code.Because I was from chemistry.Watched people worse than me walk into SIH with full teams.I sat alone.
Few months later, Google Winter of Code.2nd among 300 students.Mostly CSE and AI.
Nobody excludes you twice😇
I think AI is quietly creating a dangerous generation of software engineers.
And nobody is talking enough about it.
A lot of developers today can build things faster than ever before.
But fewer developers actually understand what they are building.
That’s the scary part.
I recently noticed something while talking to students and engineers.
People can now generate:
0. React components
1. APIs
2. backend architecture
3. SQL queries
4. Docker configs
…within seconds.
But the moment something breaks unexpectedly, many get completely stuck.
Because debugging requires understanding.
And understanding takes struggle.
Earlier, when we used to build things manually, we would suffer through:
0. weird errors
1. broken deployments
2. dependency hell
3. state management bugs
4. performance bottlenecks
At that time it felt painful.
But that pain was actually building engineering intuition.
AI removes a lot of friction.
Which is amazing.
But it can also remove the learning.
And I think this is where the gap between “developers” and “engineers” will become very visible over the next few years.
The developers who survive AI won’t be the ones who can generate code fastest.
It will be the ones who can:
0. think deeply
1. debug systems
2. make engineering decisions
3. understand tradeoffs
4. simplify complexity
Code generation is becoming cheap.
Judgement is becoming expensive.
That’s probably the biggest shift happening in software engineering right now.
Bought 100xschool combined bootcamp. I already know basics of web D, mainly bought it for Ai and devops. Syd isse hi kuch "भला" ho jaye
@kirat_tw@100xDevs@100xSchool
JavaScript's async model confused me for weeks.
Then it all clicked.
Here's the evolution from callback hell to clean async/await and the mistakes nobody warns you about
So the async JS journey looks like this:
→ Callbacks works, but messy
→ Promises cleaner, chainable
→ Async/Await readable, modern
Common mistakes to avoid:
→ Forgetting .catch()
→ Sequential awaits for parallel tasks
→ Skipping try/catch
Save this thread for later
Still learning all of this myself while building real projects
Documenting everything publicly the wins, the bugs, the breakthroughs.
Follow along if you're on the same journey
What async mistake caught you off guard? Drop it below
Recently I learned about Javascript architecture for asynchronous code, how it works and how call stack, callback queue and webapis work together. It was really good to go in depth and have clarity in what you learn.
Finally got free from the sem exams, being in a non-cse branch makes me realise how much my time gets wasted in these exams, quizzes, assignment and all 😭😭😭. Sometimes these things just really hurt my coding journey. But at the end, Ig rebound is what matters.
I casually applied to a Japanese tech company's summer internship, knowing the competition is brutal from talented applicants worldwide. I'm happy I solved their coding problem and took initiative. The rejection gave me honest insights into how much I still need to improve.
Tired of "build in public" accounts that mostly post "let's connect" and rarely actually build.Looking for serious builders who consistently ship and share real progress.If that's you, let's connect and support each other's work.