@ProudSocialist Being human and keeping control of your own mind is the real superpower here.
English
KyroFlux
70 posts
This is wild.
Elon Musk is now pushing his Neuralink brain implants by proclaiming they give you “cybernetic superpowers.”
When something sounds too good to be true, it usually is. I don’t want artificial intelligence or a chip in my brain. I just want to be human.
English
@bendee983 Coding is just the mechanics of translation. The actual engineering happens in the spaces between the lines of code the edge cases, the constraints, and the trade offs.
English
The illusion that software engineering is just coding existed among non-technical people even before AI. They thought anyone who opens an IDE is a software engineer. Hell, even editing HTML wasn't much different from writing C++ code.
And now that they have AI writing the code for them, the same people think they can replace engineers.
AI didn't create the illusion, but it sure as hell amplified it.
Pratham@Prathkum
AI created the illusion that writing code is all it takes to be an engineer.
English
@unusual_whales In big tech, writing code is the easy part.
Hard parts are system design, cross team coordination, testing at scale, and production risk. AI speeds up coding, but org productivity barely moves; bottlenecks aren’t in code.
English
89% of leaders say AI has not improved their company's labor productivity, despite widespread adoption, per Gallup.
English
You spend less time typing and more time reviewing, debugging, and verifying.
The real breakthrough won’t be generating code faster. It’ll be mathematically proving the code is correct so you can deploy it without reading every line.
Ashutosh Maheshwari@asmah2107
Hot take: AI code generation doesn't actually save you that much time. If you have to painstakingly review and debug every line of AI-generated code, you're just trading writing time for reading time. The real holy grail? Verification. When AI can mathematically prove its code is 100% correct, you can confidently deploy it without ever looking at the source file.
English
Students today are not scared of debugging anymore.
They are scared of waking up and finding out their stack is “dead” overnight.
Akshay Saini@akshaymarch7
I think software engineering is becoming mentally exhausting in a very different way now. Earlier the struggle was: “How do I learn all this?” Now the struggle is: “What should I even focus on anymore?” Every week there’s: a new AI tool a new framework a new coding agent a new workflow a new prediction about developers becoming obsolete And I think many students are silently overwhelmed. They are not lazy, it's because the industry feels totally unstable. I’ve spoken to students who genuinely feel guilty for taking even a small break now. They think: “If I stop learning for 2 weeks, I’ll fall behind forever.” That’s a horrible feeling to live with constantly. The strange part is: the more tools we get to improve productivity… the more anxious people seem to become. I think one of the most valuable skills in the next few years will simply be: 0. the ability to stay calm. 1. To ignore noise. 2. To focus deeply. 3. To build patiently. Because the people who survive long-term in tech are usually not the fastest learners. They are the most consistent thinkers. That's why I always ask my students in my courses to "be curious" about everyting!
English
@dangreenheck AI is great for coding, but if you’re not careful with prompts and your code review process isn’t very efficient, it can confidently add a lot of dead code.
English
I've been using Claude Code exclusively for 6 months and I'm still not convinced on this whole AI thing.
There are some *seriously* insidious problems that worry me, and I don't see them being fixed any time soon.
Every release of a new model, I see hundreds of posts where people think because they one-shotted X or Y, software jobs are cooked (I've probably made one or two of these posts myself).
But none of those examples are actually representative of real-world software.
If I set it to work on an ambiguous or highly complex problem that has a lot of branching in the solution space, I've noticed the following:
- It can often generate a working solution in one-shot, which gives me a false sense of confidence that the AI knows exactly what it's doing.
- As I continue to work the problem, I've noticed the AI will start to narrow its focus more and more, not considering how a fix or solution plays into the big picture.
- The quality of a solution depends on *how* I prompt it, which is really, really bad. Software engineering should be deterministic, not a dice roll.
- It will often ignore instructions I have explicitly stated in the rules file, which removes any confidence I have in the code it generates.
- It consistently overstates its confidence in a solution. I literally just got this response from Claude: "I overstated that. Honest answer: it depends on the scene and implementation; the 2–4× figure was too confident." If I had never pushed back, I would have been operating on incorrect information.
- It is far too agreeable. If I'm not careful in my wording, the AI will blindly follow my instructions, even if they are suboptimal. I want a real coding partner that challenges my ideas, not an ass-kisser.
Don't get me wrong—AI has helped me build some amazing things faster than I ever could without it.
But the more I use it, the more I begin to question the direction things are headed.
If the AI was more direct about what it (not) capable of, it'd be a lot easier to work with. But being gaslit every step of the way makes the process stressful as hell.
Going back to manual coding isn't even an option since the value of having AI *potentially* generating the correct code in 1/10 or 1/100 of the time is literally too good to pass up on.
Sorry for the rant, drank way too much cold brew this morning.
English
@kyronflux Hi Viresh, we regret the inconvenience caused. Our team is working to restore the services at the earliest. Your Jio WiFi Router will start showing a “Green LED” once the outage is restored – Pooja
English
@kyronflux Hi, we tried connecting you over phone but could not get through. Please note that our team is working to restore the services at the earliest. Your Jio Wi-Fi Router will start showing a “Green LED” once the outage is restored - Shashank
English
@kyronflux Hi Viresh, we regret the inconvenience caused. Please allow us an opportunity to look into this for you. Kindly DM your JioFiber/JioAirFiber ID and your registered mobile number to assist you better – Neha twitter.com/messages/compo…
English
@swapnakpanda Software isn’t just writing code, it’s owning outcomes. AI can assist, but accountability will always sit with humans that’s what keeps the role alive. Coding will not disappear, it’ll just evolve. Senior engineers who understand code + systems will be more valuable than ever.
English
You may agree or not, AI will replace all software jobs by 2030.
1. Coding jobs will be gone very first.
2. Companies will slowly phase out senior developers.
3. Junior developers will be asked to take help of AI.
4. Tech interviews will be more focused on AI awareness. DSA, Leetcode will be the things of the past.
5. A company will have multiple accounts. Each account will have one human manager who will manage multiple AI agents. These AI agents would play the role of individual project managers.
6. All projects will have maximum 1 or 2 human resource. They will just be there for critical decision making. Rest all the operations will be handled by AI agents.
7. There will be AI agents for different kind of roles. Manager, BA, Architect, Sr Developer, Jr Developer, QA, DevOps Engr, DBA, etc.
8. Companies will hire more AI agents. There will be specific companies those will prepare these AI agents.
9. Initially there will be a lot of job cut. But slowly a lot of new projects will be created requiring humans. A human who knows AI and would work with AI agents.
10. Slowly this mechanism will be pushed to other industries. Banking, Manufacturing, Transport, etc.
11. Software jobs will not remain like of today. There will be no status calls. There will be no follow up meetings. But still everything gets delivered quickly, effectively, and effortlessly.
12. It will initially impact the economy very badly. But then more and more AI enabled humans will keep entering the industry.
13. We will see more n more small companies and freelancers than big scale MNCs. Big companies will either get shut down or shift to producing AI agents.
14. Companies will pay only one time for purchasing AI agents. Hence, more money gets saved. The average income of human employees will be 3x to 5x as of today.
15. This will in turn make everyone richer. Economy will flourish rapidly.
Do you agree with this analysis? What do you think how will AI impact us? How should human be prepared for all this?
English
@zuess05 If AI ever stops making mistakes, engineers still won’t just be “proofreaders”. They’ll be the ones deciding what gets built, what “correct” even means, and taking responsibility when reality breaks at 3am anyway.
Companies don’t pay for code. They pay for judgment.
English
Genuine question.
Tech companies are laying off thousands of engineers, and the ones left behind are basically just reviewing AI-generated code.
But what happens in 6 months when the AI stops making mistakes?
If your entire $200k job has been reduced to proofreading Claude's output, what exactly are they paying you for?
English
@swapnakpanda Software engineering is getting extinct by 2030, and you are still selling system design courses.
English
If you want to learn System Design Fundamentals,
Go for this playlist (100 videos):
English
You didn’t watch @sachin_rt back then you experienced him.
Mihir Jha@MihirkJha
No IPL or World Cup could ever match the divine feeling of waking up at 4am on a freezing December Patna night, wrapped in a blanket, watching the Master Blaster hammer Australian fast bowlers on the old TV. Pure magic. Pure Sachin. Divine #Nostalgic
English
With all due respect to Andrew, in his motivational post, he didn't explain why anyone would write code by hand. I can code, but I consider coding by hand a waste of time.
So, if I, the one who already knows how to code, consider this a waste of time, why would anyone learn something which is very hard to learn only to then consider it a waste of time, like I do?
English
Creator and head of Claude Code:
"100% of my code is written by Claude Code. I have not edited a single line by hand since November. Every day I ship 10, 20, 30 PRs… I have five agents running while we’re recording this."
CG@cgtwts
Anthropic CEO: “In the next 3 to 6 months, AI will write 90% of the code, and within 12 months, nearly all code may be generated by AI.” the job isn’t coding anymore, it’s telling machines what to build.
English
Yesterday I had a serious conversation with my cousin
He is a senior software developer at JPMorgan Chase with 10+ years of experience.
His wife is also an SDE at Capgemini with a similar experience
Stable jobs
High income
Comfortable life
But he told me something unexpected.
He is quietly building a small business on the side
I asked him,
“Why? You’re already earning well. What’s the need?”
His answer was simple:
“The risk of losing a job is real. AI is moving fast. No role is 100% safe. Salary is not security. Skill is not security. Only optionality is security.”
That line stayed with me.
We grow up thinking:
Good college → Good job → Safe life
But the ground is shifting
AI is automating tasks
Companies are cutting costs
Layoffs don’t care about experience
10 years in tech. Top company. Still thinking about backup
That tells you something
This isn’t fear
It is awareness
He is not quitting his job.
He is not panicking
He is diversifying his risk.
One income stream = vulnerability
Multiple income streams = leverage
The real lesson?
If people at the top are preparing for uncertainty
why are the rest of us assuming we are safe?
The question isn’t “Will AI take my job tomorrow?”
The real question is:
If it does, what is your Plan B?
English
The management is firing 1000 employees, 25% of workforce, due to implementation of AI.
Be ready for more such news in the weeks and months to come. And definitely it would keep many anxious.
AI would definitely open up new opportunities and employment. But it won't happen in a predictable pattern. Changes are always chaotic and painful. The unfortunate truth is those who get new opportunities need not be the ones who gets fired from their current jobs.
Don't go for new debts. Try to increase your emergency fund so that you've time to plan for transition.
Chandra R. Srikanth@chandrarsrikant
🚨 BREAKING: Livspace shakeup: 1,000 employees fired; Co-founder Saurabh Jain quits KKR-backed Livspace, the home decor and interior furnishing startup, has let go of at least 1,000 employees, representing about 25 percent of its total workforce, in a move to lower costs, people familiar with the developments told Moneycontrol. Break by @Goenka_Tushar1 moneycontrol.com/news/business/…
English