Should I use AI to wrote my code?

Recommendations?

Can it take user stories written in Gherkin? Do I need activity diagrams? How deep can the solution be, or do I need to generate each file separately?

Can AI write my Xunit test, too?

#m=image%2Fjpeg&dim=203x249&blurhash=_OHo2Y%5E*oxWFtRV%5BRiyCMyWAaftQWBWC_4IVWCadRjt6RjRPobohR%25RQodoL%3FbRjM%7CofWBkBWBozt7oJogWVRjWBXTWCxtxut7V%5BbHjraykCV%5BaxRjj%5Bn%7EoeWERkkCWBof&x=c3164838a908752237e0e341319957e0ea1178bd2df8b7c6667f1c50995a3f79

Reply to this note

Please Login to reply.

Discussion

I've worked so hard on the concept that I should be able to just generate the code.

Feels like I'm a typist, rather than a developer. AI can type for me, right?

All of the thinking is basically done. πŸ€·β€β™€οΈ

Make sure you understand the code. If you're clear in explaining it, the AI is pretty good, but you have to check its work.

Yes, I would read everything.

I'm used to reviewing code, but not writing it, so I write really slowly and have to keep looking up syntax and stuff, when it's a new language.

I think more in algorithms and pseudocode an diagrams. Logic.

Programming is more like a trade skill. Crafting. I'm not that code-crafty.

Yeah AI is good at answering questions about syntax and commonly-used patterns in this or that language.

Literally me:

-- Have novel idea

-- Document it in a user story or use case

-- Add acceptance criteria in Gherkin

-- Describe it in state diagram, activity diagram, class diagram

-- Write it up in pseudocode

-- Find interesting library to use

-- Get all excited

-- Open empty repo

-- Stare blankly at repo

-- Stare blankly at repo

-- Stare blankly at repo

-- Ask bros what the file ending for the file should be

-- Create file

-- Stare at repo containing file

-- Stare at repo containing file

-- Close laptop and go cook dinner

It's hilarious how much code I've actually written, once you've experienced me acting like that.

Will she ever start coding? 🧐

Stop rushing me! I need to get into the meditive coding trance. πŸ§˜πŸ»β€β™€οΈ There's a process. Trust the process.

You need to be a product owner or architect. Then you tell the developers what to write, and they'll nerd out over recursion and authentication code and algorithms and all that.

Ugh. Recursive functions. *shudder*

Hehe I love that stuff.

Well, Business Analyst is a bit like that. Focused on case-definition and testing and strategy and planning.

Architects need more technical understanding and PO would leave me with no one to hide behind and cry.

But if I don't program at least a bit, occasionally, I lose understanding of what the developers are dealing with.

Technologist, but make it girly.

Okay, gotta sleep, fr. GN

GN!

πŸ₯°

I personally don't enjoy A.I. although I have used it from time to time to write simple boilerplate. I also enjoy typing (usually).

Yes, boilerplate. That's what I keep hearing. You'd probably have to train one for a long time, to get much more out of it.

Or buy the really expensive one.

Oh, I actually do like the typing, once I get into the "zone". And then I work faster and faster, the more code is there.

But God forbid someone interrupt me and I leave the zone. Then I just stare blankly at the screen again.

I seem to not need that mental clarity to do everything else. I have so much kinetic memory for those tasks, I suppose.

Or maybe it's just anxiety.

That's what it probably is. A form of writer's block.

AI is probably perfect for that, as it just vomits up something and ends the Blank Page Terror.

writing notes has been very useful for getting pass the blocked phase.

I start with a problem statement or definition of what I am trying to do. Then write down the first step or steps. The step must be small, actionable.

Do you mean, you write the notes as comments into the actual program file? Like a structure? And then fill it in with code?

Yes, sometimes. This would be more if I am writing a new function.

But more generally, anytime I get stuck in a moment of inaction I just write in a text file in notepad, or a mead notebook I bring with me everywhere.

Any tool that is maximally simple that it requires 0 thought.

Ah, I see.

And yes AI is very good at that.

I relate to this very much. I haven't done this in a while, but I found at one point that offsetting my day by a few hours earlier helped me carve a block of time where I was virtually guaranteed to be undisturbed for a few hours. I would wake at 5am, be at the office at 6 and have the place to myself until 9am or so.

That sounds nice.

My house is like a train station and my work desk is in the hallway. I just put headphones on and pretend to be deaf.

I was just saying that is what, at one point, I did to solve the interruptions issue. You mileage may vary, Your circumstances are different, etc.

Pretending to be deaf is also a good strategy.

Pretending to be blind and dumb is good too.

I use that one pretty much every time I'm out in public.

πŸ˜‚

Get a GitHub Copilot subscription, set up the VS Code extension, and start chatting with it. It's really handy, and can generate large chunks of code. Then you just need your read and edit.

Oh, that's interesting. πŸ€”

There's a free-to-me version. Nice.

I just want to stay trendy. πŸ˜‚

All the kids are using AI, I hear.

I find it limited in usefulness, but the best thing is to figure out what works best for your flow.

My husband has one from his company and he says it's good for creating a template.

I can literally feel the other developers following me, staring at my note in shock and horror. LOL

Y'all are so last year.

#asknostr

nostr:note1xrhkd0p8q8506xhpxsdsf0atzls66ks9yx5sfhweqarf0zc77dgs6l7v5f

I think it depends on the code you need. If the AI is going to simulate human coding abilities, you are going to have the same problems as with human developers but faster: the more code you have, the bigger and more immutable your solution will become.

Even if you specified the solution in Gherkin and drawn all the diagrams, imagine the coordination effort needed for real developers.

But I think you are way better off than the rest of us because you actually have the concept in your head. I often donβ€˜t. I start trying different solutions to see how they feel. I guess copy-writing is similar.

I actually suffer the opposite problem. The entire system exists in my head, right down to command line help and button shapes and menu items, and I can actually try everything out in my head.

But the software just exists in my head. πŸ˜‚

It's like hacking on imaginary software in a dream.

I am then bizarrely fast, tho, as there are no false-starts or experiments. Already did all of that.

Type the whole thing out rapidly, including the unit and integration tests.

I guess I should start doing katas πŸ˜‡

Shadowboxing, but make it code.