Do you guys write code on paper or only in IDE?

[-]

EmbarrassedAd9039@reddit

I sometimes write code on paper. Yes, it helps me think more intentionally and logically about code. This isn't too much of a surprise because writing by hand in general supports skills in critical thinking and creativity. I will continue to write code this way.

[-]

indranet_dnb@reddit

Write code on paper?? Brother I don’t even write code anymore. I whiteboard, plan out what I want to do, have AI write like 90% of it, and then tweak the last 10% and I’m golden

[-]

Talamand@reddit

I dont even write code in the IDE anymore, why would I write it on paper?

[-]

IAmADev_NoReallyIAm@reddit

Write code on paper? No. Design code on paper? Yes. I almost always do. i've got so many scraps of paper with pseudo code and outlines written on them going back years, decades even. Every once in a while I find one and look at it and either remember or totally forget who I wrote it for or why... Usually I remember. It's like finding a little lost nugget of time.

[-]

daltop@reddit

If you use PyCharm, the better option is to just go into your settings and turn off code prediction, or more simply click somewhere in the top left and then press power saving mode, all predictive functionality of PyCharm will stop functioning making you write the code completely and allow for live testing of the code to ensure it functions properly.

[-]

GrainWeevil@reddit

If you're just learning, this can be a very useful exercise. As you progress, there's probably no need to write code with accurate syntax on paper, but it's still helpful to write out your solutions/algorithms in some kind of pseudocode

[-]

Rikmastering@reddit

No. Actually writing the code on paper is not worth it, even if it has some upsides like you said. But diagrams, concepts, relationships, architectural decisions, all done in paper.

[-]

Arch-NotTaken@reddit

I'm a bit old, but not that old.

During certain exams in high school, professors would make us write code on paper, including SQL.

The difference with modern standards, in my opinion, is quite noticeable

[-]

Aware_Instance_2592@reddit

I’m 22 and did that for many of my university classes for my CS degree (at a very solid school).

[-]

covmatty1@reddit

I did all of my university software exams on paper, and I'm (only) 34!

I can still say "only" with "34" right 😂

[-]

Exciting_Weakness_64@reddit

I am 22 and we still do that in my country, I got my degree last year and we write all the code for exams on paper

[-]

iheartrms@reddit

Rote memorization is probably big in your country and you get marks off for syntactical errors, right? That is not helpful to education. As an employer, that is not what I'm looking for.

[-]

Exciting_Weakness_64@reddit

exactly, the whole education system needs a revamp, it's the same strategy from kindergarten to uni, memorize, pass the test then forget

[-]

i-sage@reddit

So paper checker is the real life compiler in uni exams

[-]

Rikmastering@reddit

Yeah me too. But that's a different thing, we mostly do that to prevent cheating and to avoid setting up a lab for a test. It's not like we think it does any good to write code in paper. In fact, most of our written exams are made in pseudo code, not a real language.

[-]

Keiji12@reddit

We wrote C exams on paper and I mean like multiple pages of code, whole classes, inheritance etc. Imo it was stupid, it didn't reward problem solving or being able to debug, fix bugs etc, it rewarded memorizing syntax and few possible scenarios.

[-]

Additional_Clothes58@reddit

'memorising syntax' is how you build the foundation.

[-]

S0_B00sted@reddit

C

classes

🤔

[-]

fakintheid@reddit

Lmao yeah, they have never written any C

[-]

Keiji12@reddit

Yeah, it was probably structures, as close as you get to classes in C for basic uni courses

[-]

Temporary_Pie2733@reddit

You don’t need perfect syntax, but you should be able to reason about what code would do without having someone else tell you.

[-]

Initial-Sea-2834@reddit

lol i had a semester of C in 2024 and we wrote the code on paper even in exam we had to write simple programs on paper

[-]

Temporary_Pie2733@reddit

Back before laptops were common, I would sketch out code on paper if I was thinking about a problem away from my desk. I might still do that, but the times I won’t have my laptop handy are less common.

[-]

geneusutwerk@reddit

With AI concerns this might be coming back.

[-]

RayZd01@reddit

I write code on paper at school but it is very unpractical and it doesn’t really rewards problem solving, just memory.

[-]

DepartureOk2363@reddit

People write code on paper???

[-]

KronenR@reddit

It helps consolidate memory, so it’s useful when you’re starting to learn programming.

[-]

Bob_Frank_Codes@reddit

I often plan on paper, but generally any code I write is on computer, if that helps

[-]

Syncher_Pylon@reddit

I don't write code on paper, but I do sketch out data flows and system diagrams on a whiteboard before jumping into the IDE. Helps me think through the architecture without getting lost in syntax. For algorithms specifically, pseudocode on paper can help — but for day-to-day work, the IDE feedback loop is too valuable to skip.

[-]

bastrooooo@reddit

Usually the interpreter has issues running from paper so I mostly avoid it.

[-]

chemape876@reddit

writing pseudocode for planning is fine, but why on paper?

[-]

sphynx411@reddit

Mostly in IDE. I make some sketches on paper, but not code that necessarily compiles. Even though we need to know the syntax, IDE helps a lot with typos, minimal mistakes, and also it highlights with useful colors...

[-]

wxr_x@reddit

Haven’t wrote code on paper yet, only plans to make that code

[-]

hiroisgod@reddit

i have a whiteboard that i write psuedo code on and draw out problems

[-]

iMrParker@reddit

Lol when I was in college for compsci, a lot of coding exams were done on paper. I think it's unnecessary, but very beneficial to lock-in those fundamentals. But you'll be wasting a lot of time writing down boilerplate code

[-]

redsharpbyte@reddit

Best devs I've seen have a paper and a pen next to their keyboard. Paper is non linear you can draw - scratch - link mixup overwrite .. with direct physical extension of your brain - your hand!

that said I always recommend new devs to express their idea on paper first. This puts one in architect mindset. pseudo algorithm architects.

[-]

ThrowAway233223@reddit

Never paper. It is a waste. You can't go up and add a line or adjust a line on paper without having to use whiteout and wait for it to dry. A text editor allows you to do so easier. Also, on that note, it doesn't have to be paper or a full IDE. You can write python in a basic text editor.

[-]

voideng@reddit

I haven't written code on paper in this century, and never for Python.

[-]

GryptpypeThynne@reddit

On paper?? If you want no IDE just use notepad, good lord

[-]

thephotoman@reddit

Code on paper is not a good idea.

[-]

capilot@reddit

In between. I write in a plain text editor in one window, and run or debug the code in another.

[-]

Old-Eagle1372@reddit

During many interviews they force you to use black/whiteboard no code pad. For work no. You can plan on paper whiteboard, use IDE for implementation.

[-]

grassxyz@reddit

I would write only pseudocode (or draw anything abstract) on paper. you can then give it to ai and let it write optimized code for you.

[-]

HalfFresh1430@reddit

I don’t like doing it on paper because writing takes way longer then typing

[-]

ProbsNotManBearPig@reddit

Also cannot ctrl + f or find + replace. It’s really tedious to edit or share with others generally.

[-]

__salaam_alaykum__@reddit

yeah it always gets my gears grinding when I have to fax pull requests

[-]

TurboTape76@reddit

I will send you a smiley on fax. This made me lol. 🤣

[-]

AllanSundry2020@reddit

your company needs to modernise fast my man

[-]

Catenane@reddit

Smh back in my day we literally pulled requests out of the sweaty trembling arms of juniors

[-]

Apart_Ebb_9867@reddit

Which is kind of the point. It is slower, you think more. That said, most interesting problems don’t fit a piece of paper so I reserve that for high level brainstorming with myself.

[-]

AliceCode@reddit

You don't have to type nonstop. I spend a lot of time thinking about what I'm doing.

[-]

Apart_Ebb_9867@reddit

Then your point about choosing one because is faster is kind of weird.

[-]

AliceCode@reddit

That wasn't me.

[-]

Apart_Ebb_9867@reddit

Yep, sorry. I realized that, deleted my comment but Reddit apparently doesn’t play ball.

[-]

walledisney@reddit

I concur

[-]

Greedy_Fault_7913@reddit

Paper pseudo code can have value since u don’t want to write all the code and then type it all in. U end up just cutting your problems intro blocks . So function (file_path) return each line , function2 parse line from file, etc. so instead of being caught up in detailed solution you just map out the work flow .

[-]

Pleasant-Leg8590@reddit

who the absolute flip writes code on paper

[-]

kewlness@reddit

I do not write code on paper, but I will sometimes sketch out the process flow I want to implement as a kind of road map which I do find helpful in some situations.

[-]

NationalGate8066@reddit

Instead of paper, why not use a simple text editor (notepad/notepad++/sublime text)?

[-]

guareber@reddit

Yep, I can vouch for this - I stick to Vim with nearly no plugins.

[-]

radrichard@reddit

I write pseudo code on paper or sometimes flow diagrams. Not syntactically correct code though

[-]

Gnaxe@reddit

Those aren't the only two options. I do sometimes write code in Markdown documents where I at least get syntax highlighting. In a Jupyter notebook, I can get Markdown, and I can test the code. Doctests have a similar feel.

I prefer to do my thinking in my head. It's faster, and I retain more. I do start writing stuff down when it gets to be too much.

A computer can help check your work. Paper can't. There were times when I had to write code on paper in school. It was weird.

[-]

HumanAfterAll777@reddit

I only use vim on my green terminal

[-]

looopTools@reddit

Paper, whiteboard, in sand (no not kidding). If I am discussing something with another person and we get to a point where we need to discuss the actual code, then write it down. Sometimes only in pseudo code. Sometimes rocks indicates pointer dereferencing

[-]

Jugad@reddit

Thinking and planning is done in the mind, on paper, or in a document (which ever works best for the case)... implementation is best done on the computer.

[-]

UsernameTaken1701@reddit

Flowchart on paper, code on screen.

[-]

frausting@reddit

Writing code on paper is a bit wild. Flow charts, architecture, big picture stuff? For sure.

I get the inclination though. When I want all the IDE BS out of the way, I just open up Sublime Text (with syntax highlighting but nothing else), and bang out some ideas.

I’d suggest trying that. Sublime Text or Notepad (Windows) or TextEdit (macOS).

[-]

beobabski@reddit

I tend to write down variable states at critical points on a piece of paper.

Like maybe a timeline with dates (i.e. delivery and arrival) on a timeline with arrows indicating timezone changes for the human interacting with the system.

Or truth tables for a particularly involved piece of customer requirement logic.

Or a data flow diagram which shows what data we know at what point in the process.

Actual code; not really. Maybe a very high level method name dotted around every now and then.

[-]

StraiteNoChaser@reddit

On paper quite often. But I also like to keep a life journal of thoughts, ideas, to-dos anyway. so if a problem is on my mind, I’ll just sketch it out in a notebook with diagrams, pseudo code, notes, follow up questions, etc. and it gives me a chance to think it out and get action plan next time I get back to the keyboard. As a result, I find I’m more productive after this exercise.

In general, I find journaling as a stress reliever. It also gets me away for a screen break, and out the house. Sitting at a park, bar, or coffee shop with a pen and pad is one of the few ways I’ve found to disconnect and get a mini digital detox.

[-]

majeric@reddit

Personally I use a stone tablet and a chisel. I mean if you’re not going to commit, what’s the point?

[-]

GManASG@reddit

It's a programming language, it belongs on a computer

[-]

BigHeed87@reddit

Diagrams for complex algorithms help organize a process flow.

Entity Relationship Diagrams help with data modeling.

I'm old-school. Waiting for someone to say. "Wait. You still write code?"

[-]

Son_nambulo@reddit

Diagrams are not code, that's a kind of pseudo code.

[-]

Temporary_Pie2733@reddit

Code can be a serialization of a good diagram.

[-]

shennan-lane@reddit

Wait. You still write code?

[-]

blacklig@reddit

Yawn this again

[-]

ProbsNotManBearPig@reddit

Ai tools are great are writing plantUML code, which you can then copy/paste into draw.io to render any kind of diagram. Much easier to edit than a piece of paper, and better suited for version control. Granted, you can scan your piece of paper and put the image into version control if you really want lol. I’ve done more ridiculous things in my past. But the plantUML code itself + the rendered diagram are nice to store together.

[-]

ABetterNameEludesMe@reddit

Real man code on napkins!

[-]

BrupieD@reddit

You might try switching your notes into an IDE as a multiple line comment block. Like pseudocode where you write out your todo items. When you are ready to try out your code, you can just uncomment rather than transfer it.

[-]

0x645@reddit

I sometimes write on paper. in early stages, some pseudocode.

[-]

Beneficial-Teacher78@reddit

I have a whiteboard. I don't write code on it, but I love discussing ideas by drawing the concept on the board.

[-]

webfiend@reddit

Real answer: if it works for you, it works. Don't let someone else's opinion get in your way when it comes to how you build skill.

For me: it depends. My current job keeps me offline ten hours a day, so it's a real and immediate question. Am I implementing an algorithm for skill-building purposes? The effort of working the whole thing out on paper is worth it. Building an application that makes heavy use of the standard library and PyPI finds? Maybe not for the whole thing, I tend towards abstract sketches of flow and structure rather than code.

If your brain enjoys working it out by hand it might be productive to learn informal conventions like pseudocode so your focus is on the core logic rather than syntax specifics. Once you're basically satisfied and in front of a computer, translate your pseudocode to Python. Note that Python has a rep as "executable pseudocode." It's not unusual for me to sketch out the flow in something that looks a lot like Python.

[-]

drumzalot_guitar@reddit

OP doesn’t mention how much programming experience they have. If you’re relatively new to programming, generally mapping out the code on paper will help organize your thoughts, work through an algorithm before sitting down with all the distractions that can occur with a modern IDE (code suggestions, documentation pop-up, etc).

As you gain experience, you may find you’re automatically able to organize your thoughts and approach without initial mapping on paper and begin writing code in an IDE earlier.

But, do what works best for you. Different people have different experiences, levels of expertise and ways of working through problems. There’s no “perfect way” that works for everyone.

[-]

RevolutionaryRip2135@reddit

Nothing happens on the paper how ever hard I press that ctrl-space … so no. Also I am rather proficient with kbd (as all coders I assume).

But sometimes I go with markdown file or drawing (drawio or paper) or sql for schema / prototype queries.

We have (some) utilities for common shit (select into list, select value, “nice excel”, generate password, control server call rest services on our backend… so writing prototype in py and comments is f-in ez. Was thinking bit about using Jupyter but I find it too … rigid.

[-]

mirracute@reddit

Tbh sometimes I do paper, when I figure something out and i’m not home. It DOES make you think more, although universities currently use it as a grading mechanism, which shouldn’t be the case. Whatever activates your brain to think, do it!

[-]

ava_ati@reddit

I’ll write out short hand code on my kindle scribe if I’m trying to visualize a flow If something Do some stuff - need x and y dict comp

That’s about as far as I code on paper

[-]

ava_ati@reddit

I’ll write out short hand code on my kindle scribe if I’m trying to visualize a flow If something Do some stuff - need x and y dict comp

That’s about as far as I code on paper

[-]

HarrisonArturus@reddit

Paper? No, but I've written code out on a whiteboard to clarify my answer to a question in a meeting.

[-]

canbooo@reddit

I carve stones

[-]

SnooPets752@reddit

Punch cards

[-]

GreenWoodDragon@reddit

Paper first is a great way to solve a lot of problems before you get tangled up in coding. Easy to find too if you keep a day book.

[-]

sue_dee@reddit

Man, drawing the QR code to upload it when I'm done is a real pain.

[-]

RedEyed__@reddit

Never. What's the point?
However, I do write on paper a lot of diagrams to represent concepts

[-]

Coffeinated@reddit

I want to add to what others said about diagrams and look at it from a meta perspective.

Languages are tools. Tools are well suited to solve some problems in some situations and environments, and way worse suited to other problems and conditions.

Python is a programming language, all of which are designed to express to the computer how it should do certain things to solve your problem, and to be edited on a computer. Python is also moderately good at expressing human thoughts compared to other programming languages.

However, if your primary goal is to express your thoughts, work on them and evolve them, then no programming language will ever be the best tool to do so, especially not on paper. That‘s just not what they were designed to do - unlike diagrams, or just prose. That‘s why rubberducking works, it forces you to express your thoughts in a new way and a different language that your brain can actually work with.

Paper is not even the ideal tool to write text in a structured syntax that needs to be modified and shifted around, so why would you ever write code on paper?

[-]

HommeMusical@reddit

I started programming before terminals were common, so you'd write your code on paper and then transfer it into the terminal.

Everyone hated it.

I agree there are some minor benefits, but it's not worth the trouble.

[-]

spidLL@reddit

It is said Wozniak wrote Apple I basic, in assembler, with a pen on a notebook before transferring it to a computer, and it compiled with no error.

[-]

stuartcw@reddit

I used to write to write on paper until 1985 and it’s been interactive editing all the way since then.

[-]

QuirkyImage@reddit

I use a pimped up text editor to write code. The only things I do on paper occasionally are flow charts, state machine diagrams, architecture design and coming up with algorithms / math. The thing I do a lot on paper is to come up with and run through ideas. When I say paper that can be paper or a iPad with Apple Pencil (goodnotes)

[-]

Haunting-Form4664@reddit

Paper is great for tiny problems or interview-style questions: you’re basically training your brain to “simulate the interpreter” and catch logic bugs before you even touch a keyboard. That mental model does make things more runnable in your head over time. For anything non-trivial though, I’d rather lean on a good IDE and tests than cosplay as a compiler for hours.

[-]

DebtComfortable2437@reddit

This was how I learned the basics, I’d even wake up at 1am with a solved problem in my head and have to write that shit down

[-]

ThiefMaster@reddit

Why would any sane person ever willingly write code on paper? The ONLY time I had to do this absolute nonsense was in university exams.

[-]

Usual_Coconut_687@reddit

If you want to learn deeper writing on paper is best especially when you have a feedback after you finish, for hard problems that feedback may even wait to the next day, you get a lot of ideas to solve it

[-]

SnooStories6404@reddit

The only time I've written code on paper for an exam. Every other time it was in an IDE.

I found it was just annoying(partly because I have abysmal hand writing) and itdidn't help.

That said, I think anything that makes you think hard about what you're doing will help. I like to run for fitness/recreation and I often think about programming while I'm running and find I find I've solved most of the problems before I even sit in front of my computer

[-]

irn@reddit

Yup. MIS220 or something back in 01. I had to write a vb.net program on paper for my final. It took an hour, I think it was a data entry form. Everyone should do it at least once like learning to drive a manual transmission. Probably an unpopular boomer sounding opinion but whatev

[-]

SnooStories6404@reddit

> Everyone should do it at least once like learning to drive a manual transmission

At my work we have a Landcruiser with a drill on it. I have to do all the drilling because I'm the only one one that can drive manual

[-]

klumpp@reddit

Yeah this was normal for exams like 20 years ago when I was in college. I also had to do it for an interview once which I thought was weird.

[-]

SnooStories6404@reddit

That is weird

[-]

DataPastor@reddit

I have never written a single line of code on paper. Writing on paper definitely has some scientifically proven cognitive benefits, but the time / benefit trade-off just simply doesn't pay off in the case of programming. It is better to train your muscle memory writing real code into a real computer.

What is worth it, however, is to learn blind typing. I can type extremely fast, and I even learned to type mathematical equations in LaTeX so fast, that it doesn't really pull me back typing down complex maths formulae, although of course my maths typing speed is not competitive with hand writing.

[-]

AncientHominidNerd@reddit

No I just talk to myself out load to reason through my logic. I might write notes in pseudocode in my IDE.

If I need to make a graph or a tree I’ll draw it on my tablet but that’s about it.

[-]

SteelRevanchist@reddit

Debugging is hell on paper, so is packaging, you can only nest so many binders.

What I do is sketch complex flows and data models to make heads or tails, but you can do that on a computer as well. What I do is more or less paper-based UML

[-]

EgZvor@reddit

Vim

[-]

Ra-mega-bbit@reddit

It is 100% worth it at an really early stage or learning. Its good to grab the concepts and learn how to think.

After a few algorithms you can move on to ides, id refrain from doing copilot for code completion, and to run the code every couple lines, try to "imagine" or write on paper how would the variables update (write a table, go iteration over iteration and write the value each var contains)

After that, any production code now a days is ai assisted, so learn once and well, then move fast

[-]

TheCableGui@reddit

On paper when I’m getting my ass kicked by a bug or feature. It’s like consulting the rubber duck, it makes me explain what’s wrong so I can understand what’s wrong.

With python I typically write out all the logical steps as NotImplemented functions in a file. I Try to get to a working model as fast as possible and Depending on the stage of the application I move on if it’s not finished and write down where to come back to.

[-]

P12134@reddit

I write the logic/flow in my head and then write it out in my editor.

[-]

unruly_mattress@reddit

I don't, but you're probably on to something. When you want to solve a difficult problem, you want to think slowly and carefully. Writing code in an IDE makes it to easy to just run the code and check if it works rather than being careful and reasoning about why it should work.

Pen and paper are excellent and underrated tools for learning. Go for it.

[-]

crazylikeajellyfish@reddit

There's no point in expressing language syntax on a piece of paper, but it's a great tool for organizing your ideas. I specifically find that it helps in 2 ways: - Our brains are wired for visual reasoning, drawing the right diagram can make or break a prototype. - Writing ideas longhand is much slower than typing them, which gives you time to think.

You can build a more natural flow because your mind can go ahead of your hand, that way you don't stop writing.

[-]

jabbalaci@reddit

When I started programming, I wrote everything on paper first. It was very helpful. I don't do it anymore but when I write a program, I usually type correct code in the editor on the first go.

When I call my students to the whiteboard to write some simple code snippet, they struggle. I always tell them to practice on paper, solve some exercises on paper. But of course, they don't listen to me.

[-]

poukai@reddit

It is an interesting process because it makes you think about your code and see it from a different perspective. Another method you can try is rubberducking. Get yourself a yellow, other colours are available, rubber duck and go through the code explaining it out loud to the rubber duck. It helps realising simple mistakes.

[-]

breadfruitcore@reddit

Perhaps not really relevant but I occasionally has an inexplicable urge to print out some critical hard algorithm files in my code base so I can read them more comfortably.

Not that I ever acted on it. But it's a weird recurring urge. Perhaps there's an innate comfort in reading on paper over from on a screen.

[-]

EgyPalocProfessor@reddit

I plan and partly write my code in my head. Than i use an ide to finish it.

[-]

TheNakedProgrammer@reddit

At this point i would even question if you need to write code in a IDE.
The goal is always code that works as intended. Code on paper has a critical issues, it does not work.

[-]

aloobhujiyaay@reddit

writing on paper forces you to actually understand, not just autocomplete

[-]

binaryfireball@reddit

paper is good for pseudo code and higher level planning. If you feel like youre thinking more thats a good thing. youll get to a point where you'll occasionally white board things and sometime after that youll have enough xp to just know what you wanna do and how it should look like that you wont need much planning at all

[-]

Alive_Community2363@reddit

Visualizing certain relationships or certain scenarios with particular situations, to see a visual before coding that part out…. Is helpful to an extent… but don’t write it out on paper, sometimes I’ll make a document excel or storyboard art of some kind, print it out so I can see it visually while i code that structure/ scenario into a file. Though depending on what it is, my printer prints 24” by whatever I want. So I get what you mean by writhing it out. But being able to copy and paste naming conventions for specific things is so much better than trying to type out what I already wrote. The visual print is nice, just until I’ve coded it fully into my file. Though most people would say just get another monitor. lol when I had just one monitor the print out helped, and when I needed to keep a naming conventions, I’d go to my digital file and copy the name specific from the file to make sure it was the same. After getting a second monitor, I haven’t really had the need to print anything out.

[-]

SaintEyegor@reddit

I mostly use vi for quick and dirty scripts,and only use an IDE for more complex things.

[-]

the_ballmer_peak@reddit

I used to write code on paper as an exercise or when working out an algorithm, but it's been a long time.

[-]

Ok_Tap7102@reddit

Do you use tabs or spaces when indenting on paper?

[-]

DNSGeek@reddit

Honestly I do 90+% of my coding in vim, but I have been known to use (or write) the occasional IDE.

[-]

will_r3ddit_4_food@reddit

IDE with most autocomplete turned off

[-]

Berkyjay@reddit

I'm not a sadist

[-]

RadioactiveTwix@reddit

I'm a senior looking for a new job and I realized how much I've been relying on auto complete. Now that I'm prepping for job interviews in trying to solve on paper first to get the sense back.

[-]

JacobStyle@reddit

I've done diagrams, pseudocode, notes, and similar kind of stuff on paper, but not code in a format meant to be run through an interpreter or compiler.

[-]

Cy83rCr45h@reddit

Flow charts sometimes

[-]

perfopt@reddit

Writing is a great way to make you think more about any topic. I use it only for when I need to think about complicated stuff. If the code is about calling the right libraries etc then directly on the editor. These days its Claude/Codex with the editor window open to see changes.

[-]

Impossible_Ad_3146@reddit

How about girls? You only asking the guys?

[-]

Apart_Ebb_9867@reddit

“Guys“ has been commonly used for both sexes for a good fifty years.

[-]

Impossible_Ad_3146@reddit

Lies, you must like penis only?

[-]

Apart_Ebb_9867@reddit

oh, I see.

[-]

sennalen@reddit

Neither. Just Notepad++

[-]

PaleoSpeedwagon@reddit

Occasionally I'll paeudocode on a whiteboard. Then I start a doc with comments stating what I want to get done:

I need to process a list of thingies and return their foofies if they have one.

...and then step-specific comments like: # take this string "thingy" and look it up against the "blerp" database

...then I turn the steps into functions and make sure that the script returns ["foofie1", "foofie2"]

I often see the shape of an app in my head and then need those comments to turn it into code. Like describing a dream.

[-]

kalially@reddit

My most useful is to use pseudocode and Visio. I thrive in a fast paced setting and this helps me to get up and running quickly and also see where my thought process is

[-]

Perfect-Fix-8888@reddit

If it helps you to think better about it why not. Different people have different ways of thinking and learning. Nothing wrong with it. It may only add some overhead as everything written on the paper at some point will need to be typed if not already. Or maybe OCR?

[-]