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

Reply to this note

Please Login to reply.

Discussion

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!

🥰