true or false?

Nov 9, 2025 · 6:48 AM UTC

199
55
16
797
Replying to @_devJNS
True Only those who use AI to smoothen their workflow will remain in the coming years There's no point in doing the heavy lifting when you can easily use AI for for it
2
3
Replying to @_devJNS
False - you have to work harder to verify the AI’s solution, you have to work harder to understand/maintain/explain something you didn’t write, etc
3
9
Replying to @_devJNS
HOT TAKE: Copying code doesn’t make you a fraud. Not understanding what you copied, that’s the problem. The real skill is in knowing how to debug, refactor, and extend what you borrowed. Execution > Originality. Every time.
8
2
77
Replying to @_devJNS
Maybe
1
1
Replying to @_devJNS
My rule of thumb is if AI makes you >2x faster you are trading off long term ability with short term speed gains. On average if you perform 1.5x of you normal speed that’s an health, responsible AI usage.
1
5
Replying to @_devJNS
depends, working with ai on small chunk making it solving unstructure to structured problem work very well you can build impressive pipelines. but beyond this it's alot more complicated.
Replying to @_devJNS
I think this is true, everybody should use the tools that work best. But LLMs are such a rocket fuel - hard to imagine how you can not use them
Replying to @_devJNS
I write pretty much 80% of my code myself, I let AI handle refactoring, docs and any boilerplate. But no to architecture / stack decisions, and certainly not the way the code is structured. Also good at the end of your project to create install scripts for all the platforms.
3
Replying to @_devJNS
Depends why you're choosing not to use AI. You can switch from an axe to a chainsaw, but if you don't have a chain to use, it still won't cut the tree.
We bought our competitor's $60 PC optimization and tested it against ours. Paragon: 915 FPS. Xilly: 1,428 FPS. Same system. The difference was brutal.
30
41
4
661
0
Replying to @_devJNS
True, but the smartest move is knowing when to use AI and when to go deep yourself. AI gets you moving fast, but understanding the fundamentals keeps you from shipping someone else’s bugs.
Replying to @_devJNS
My experience is that LLM powered coding tools are really good at developing backend for specific features, bad at keeping consistency for full aps and really bad at developing UI/UX..
Replying to @_devJNS
false
Replying to @_devJNS
True. AI doesn’t replace thinking, it amplifies it. The smarter you prompt, the smarter you build.
Replying to @_devJNS
Use AI — or get left behind. A sustainable 5–10x performance boost is already well within reach if you use best-in-class tools and learn to configure and steer them effectively (agentic steering, alignment configuration, etc.). The name of the game is process and guardrails. #AgenticEngineering
Replying to @_devJNS
Work hard not smart
1
3
Replying to @_devJNS
Programming was never about how to write the code. It was always about how to solve the problem. No one is interested in the code (except your boss). AI saves time and solves these problems on its own. Your job as a programmer is (and always has been) to solve these problems. In 10 years, there will be almost no one left who writes code manually.
8
Replying to @_devJNS
They’re not really giving you the option not to use AI, are they? That’s not a choice
3
Is the "paperless" desk really tidy? We thought going paperless would clear our desks, but now they're just cluttered with devices needing a charge. Wireless mice, speakers, tablets, phones all fighting for an outlet. To end this "epic outlet war," we designed a desk lamp.

Is the "paperless" desk really tidy?

sterlingproduct.co.jp
1
5
Replying to @_devJNS
The world evolves.... claiming you can Multiply 78x78 in 2 secs without calculator is awesome but doesn't prove much. Same with Coding without AI, But then Jumping the Necessary process of learning how to code before using AI is a total Scam !!
Replying to @_devJNS
It has its perks
Replying to @_devJNS
Hating vibe coding is trendy right now, but including AI into your toolkit is an absolute must for any software engineer. Any that plans on surviving the next wave of layoffs anyway 😉
3
Replying to @_devJNS
Depends where u are in your journey. For a beginner I would say false. For an experienced dev I'd say true
Replying to @_devJNS
there should be the right combination you can't let AI do all the work and thinking process and on the other hand, you cannot do all yourself when the AI can code it much faster
Replying to @_devJNS
I’m agree, AI is a great tool for work
Replying to @_devJNS
Still in the interviews, they will ask you to not take internet sources or ai to answer questions.
Replying to @_devJNS
depends, sometimes the AI needs direction, if you dont have the experience in writing software to give it the right direction, you will get garbage in the end
Replying to @_devJNS
yes, because it shifts the work to sense-making
Replying to @_devJNS
This can go both ways
Replying to @_devJNS
AI is amazing for creating tests. I use it all the time to create test JSONs.
Replying to @_devJNS
Depends on what's being built. Just using AI might not always be the best resource for a project.
Replying to @_devJNS
depends how good your programming skills/documentation writing skills are.
Replying to @_devJNS
for a dev our most valuable thing is time so if using AI can save my time to play games, hang out with friends, go on a date with my wife -> far more worth it than my ego lol
Replying to @_devJNS
AI accelerates the path from idea → mainnet
Replying to @_devJNS
If you are doing it as a job then this hold true but if you are learning or doing assignments, I would still prefer doing it without AI.
3
Replying to @_devJNS
Hundred percent agree
Replying to @_devJNS
kind of a broad statement but I'd say generally true.
1
Replying to @_devJNS
Depends, if you don't know how to code in the first place are you really coding at all ?
1
Load more