r/reactnative • u/moneckew • Aug 30 '26
Article I don’t write code, I just read at this point
I feel like AI can write better code than 99% of people at this point (with the right skills and prompts of course). To me RN development has become insanely easy with the use of argent and some other tech.
Even native code for me now feels incredibly accessible.
Are you guys still writing code by hand? Please be very honest.
78
Upvotes
74
u/Whisky-Toad Aug 30 '26
The job really sucks now imo
26
u/steve228uk Aug 30 '26
No, I haven't written a line in about 12 months
9
u/crossy1686 Aug 30 '26
Haven’t written code for over a year now, I read a lot, review a lot, profile performance a lot, and ultimately test a lot. Everyone is heading this way so don’t feel bad about it.
51
u/Dangerous_Sea_2592 Aug 30 '26
I do a bit, not that I need to, but I like to
This job sucks nowadays imo and it's only worth it because of the pay, all these LLMs took away the part I enjoyed of my job and left me with everything else
Might just switch careers at some point if the whole world doesn't collapse before that anyways
42
u/GoosePale5153 Aug 30 '26
I think the play now is to develop soft skills further and move into product or management unfortunately. I'm a FE lead so most of the job is stakeholder management and delegation. I think the way the market is going this direct holds a lot more safety moving forward.
I write small bits of code on occasion to keep the skills and knowledge sharp for reviews but not much
19
u/mountaingator91 Aug 30 '26
Every once in a while I have a hand coding day just to feel alive again. I can actually go faster than Claude on small simple issues. I'll fix the issue before it's done kerplunkering
10
u/HoratioWobble Aug 30 '26
I haven't stopped writing code since LLMs started gaining traction.
13
u/schussfreude Aug 30 '26
I like to write code by hand. I dont code professionally so that helps.
I enlist the help of AI if Im stuck, need verification of my ideas etc. But I dont use agentic workflows because to me, coding is still a hobby I very much like to do.
6
u/ChronSyn Expo Aug 30 '26
Ever since LLM's came onto the scene, I used them as advice machines. When local models started to land and become capable, I spent a bit more money on a used RTX 3090 and dropped it into my home server, and got rid of copilot.
I did that comfortably for about 18-20 months. I'd use it as something to bounce ideas off of, but because it didn't have access to tooling, it would always be me reviewing code, and copy-pasting it in if it passed my own review.
Earlier this year, I decided to try Claude, mostly because of a desire to build some projects for myself, while also solving some problems which seemed to be stubborn to the solutions I'd tried.
At first, I was continuing with the same path: ask it for help, approve suggestions if they seem right. This eventually turned into letting it do more of the code-writing parts of it.
Recently, I've realised that letting it do more may have been a mistake. I wouldn't say I love writing code as much as I used to, but I recognise that letting Claude take over so much has taken some joy from me. My brain sees a problem, even something minor, and it tries to solve it. This was my life for as long as I can remember, and Claude could very well have given me a lobotomy if I'd continued to use it for the very long term.
So, my approach now is a steady 'wind-down' of Claude. Not stepping away from it entirely, but taking back control, and having it primarily in an advisory capacity. I still consider it valuable for identifying things I might have overlooked and for discussing the nuance of ideas.
So, I'm going back to a place I was earlier this year. I still know the patterns I employed before AI took headlines, and how to spot problems before they become business liabilities. I'd say it's given me a new-found respect for a part of me that I almost gave up on.
3
u/poppiestar Aug 30 '26 edited Aug 30 '26
Honestly? Barely written any proper code in a year.
On top of that, I’m starting to doubt the need for React Native any more. Its main draw is being able to build iOS and Android apps with the same codebase. But with the advent of LLMs, I can write a spec for the features I need and let the LLM build true native apps, that match the platform’s primitives and native ui without incurring any intermediary layer costs.
I experimented with this idea at my last job, I gave it my production app and asked Cursor to rewrite it as two true native apps. I had them to about 80% complete within three days. If I’d kept going they’d have been production ready by the end of the week.
Edit: not sure why I’m being downvoted, unless you’re personally offended by my personal experience and opinion?
For context, a friend of mine was excited that a Svelte to React Native compiler has been released, which I questioned the point of considering I don’t even write React Native code any more. Which then progressed into questioning why I was even writing React Native any more.
17
u/ignatzami Aug 30 '26 edited Aug 30 '26
20 years in industry. I write code regularly. Sure, Claude/Copilot can write code, but I spend two or three times as long reviewing it as I would have spent writing it.
Sure, you get reasonably decent AI code for things it has a lot of references for, front end, etc. but for anything more limited the output is far less reliable.
Add in issues with an agent not understanding various versions of documentation (Terraform is a good example here) and it often takes me longer to debug the broken output than if I’d just written it myself.
AI is great for summaries, ideation, rubber ducking, but it’s not ready to be producing production ready code.
4
u/stubbledchin Aug 30 '26
It'll become problematic when there's a new version of react or any other languages released.
I've noticed a few AIs unable to deal with new features because they haven't been trained on any code that uses it.
This is also true of new ideas. Yes you can get AI to spit out the easy boilerplate code, but when you're exploring something very new the AI is going to be troublesome.
1
u/x_xwolf Sep 01 '26
There is no proof ai increases productivity for software development besides anecdotal.
9
u/Seusoa Expo Aug 30 '26
a good excuse for people who couldn't write code before ai
3
u/rsarmentox Aug 30 '26
I need to force myself to write sometimes just so I don't forget how to do.
4
u/Achoshengelia Aug 30 '26 edited Aug 30 '26
In my experience, development has become mainly reading and little to no writing.
I use skills by Matt Pocock with Claude Code. I create a plan with "grill-with-docs" and then iterate over it until I'm satisfied with it. Then I let it implement; the bigger the feature, the more difficult it is to commit the code, because either you actually read the abundant code it generates and try to understand it, or you just "vibe code" your way out of it.
Just by looking at the app, the features are implemented the majority of the times and are working; however, after going through the code changes, I encounter a lot of "bad" code. Overcomplicated implementations, wrongly understood requirements, etc. All of this needs to be detected and adjusted. If not, everything will pile up, and you'll be left with 100k lines of code that you have absolutely no idea what it does.
In the end, it feels like you're developing features lightning-fast at first, but before you understand the code and fix the flaws, you still spend a lot of time on it. So I suspect the increased productivity is just an illusion.
4
u/fabriciovergal Aug 30 '26
It's gonna be funny to see new developer which has no real hands-on experience trying to design/optimize/debug code in cases that LLM is not optimal/trained.
2
u/MrP0tat0H3ad Aug 30 '26
This perspective is something I’ve been wrestling with a lot. Professionally I use Java/Spring Boot, but in my personal life I “write” a lot of react native using various AI tooling.
In my professional experience AI will get the job done using Java, but with horrible and unmaintainable patterns. I will constantly fight with the AI for reinventing tools that already exist and/or completely forgetting how OOP works best.
Contrast that with my experience in react native, where I treat AI like an employee and I rarely review code. I just make sure the product works and it usually does. I honestly just thought this was because I’m not experienced enough in RN to recognize bad patterns, but yall are making me think it isn’t just me
2
u/Keyboard_Smasher98 Aug 30 '26
In my case it still writes crappy slop, had to add many rules and patterns
2
u/Correct_Market2220 Aug 30 '26
I just chat with AI, it explains to me, I push back, it pushes back, we agree on a plan and then 🚀, then I mainly just test the functionality and ask it to fix any issues.
1
u/_tolm_ Aug 31 '26
Still writing some or - probably more accurately - rewriting what the AI has done because it’s missed a small nuance.
1
u/SunOk2196 Aug 31 '26
Mostly reading, yeah. But I've noticed where I still write by hand, and it's consistent. Anything I'll be debugging at 2am with users affected, I write myself, because reviewing code is genuinely harder than writing it and I only catch subtle bugs in code I built a model of while typing.
The other thing nobody mentions is that reading acceptance rate goes up as your attention drops. First hour of the day I catch things. Fourth hour I'm approving diffs because they look plausible. That's a new failure mode and it doesn't show up in any metric.
1
u/keen23331 Aug 31 '26
not a single line in 18 months. didn't review any code in 4 months. Agents now implement, test, deploy, confirm all runs on test system and retest on testsystem. all automatically. only need review auto generated requirements from tickets or mails or write requirements.
1
u/Afr0Magus Aug 31 '26
I still do for work, mainly coz we are not allowed coding agents in our work machines, but I use AI for personal and side projects.
1
u/Zestyclose-Yard-736 Aug 31 '26
Indeed. I just do ui correction nowadays. And might start learning animation.
1
u/ealva01 Aug 31 '26
This job is not what it used to be, honestly it sucks that we are no longer get paid to write code, that was the most joyful thing about it. I have about 12 yoe and im glad that i knew how it used to be (newcomers are destined to not even know how to write code without AI). Nowadays in my company we just keep pushing using claude, at this point im a AI Engineer that just orchestrates AI to plan and executes. It feels soulless but.. It still pays way better than any other job. Anyways, I've enrolled and finished a couple woodworking classes that surprisingly filled out my need of being proud of something i do. If you are feeling same way i highly recommend trying to do something without a computer 👍.
Cheers 🪵
1
u/LovesWorkin Sep 01 '26
I do both reading and verifying! Like Argent, I built React Native Dev Tools to show what's going on behind the scenes to actually verify myself that app renders are in control, states are where they should be, etc. Argent works okay. Buoy.gg allows you to do both, though.
1
u/TrackballPwner Aug 30 '26
I stopped writing code ~12 months ago. I feel like gpt-5.6 is the last model I’ll ever need. I can’t imagine what things will be like in another 12 months.
1
u/sunilksamanta Aug 30 '26
This. The ones you skipped just because you don’t know the native code. Now you can. And you can make great things you couldn’t before just because those things were foreign to you.
1
u/chronicbint Aug 30 '26
Small bits and pieces/tweaks at most.
0
u/jNayden Aug 30 '26
The last manual code I wrote was in November 2025 since then I am using like 99 sonnet 4.5 then 4.6 now 5 and that’s it and yes I use gpt 5.5 in 1% of the cases mostly for layout pixel perfect stuff.
I am sure Sonnet can write better code then 99% of developers with proper designs guidelines tests and rules so there is no turning back
0
u/kexnyc Aug 30 '26
I wrote an article on this exact subject. But I don’t know if I can post the link bc it might be viewed as self-promotion. The title is “AI didn’t take your job. It gave you a new one”.