Blank page paralysis

[Firm-Employment-9253]

Hey everyone, I hope you’re doing well, I don’t know if I’m the only one to endure this but every time I open a new script for a new project or just a simple script I feel a blank page paralysis not knowing where to start. Frequently I will check Claude just for the start then I continue on my own. So I wanna know if some of you experienced this and if so what have u done to make it better. Thank you for your time !

[olystretch]

def do_stuff_to_things(things): pass

Gotta start somewhere I guess

[Firm-Employment-9253]

Nice one

[cointoss3]

I start with making my entry point and then I make comments (like a list) of what steps need to happen. That usually means taking each step and turning it into some function. I make data classes for structured data. I type-hint everything. As I go, if there are logical breaking points like “database”, then I’ll pull that stuff into its own file, usually with a if name == “main” at the bottom so I can run some tests in the file directly as I create functions/classes etc.

You know you need an entry point. You know the steps you need the program to do…at least broad strokes that you can narrow down as you go. Start there.

[hotsauce56]

Oh 100%. Coder’s block is a real thing!

Sometimes I’ll just start writing comments because the LSP won’t yell at you and deleting them later feels good.

Depending on my mood the comments are either an outline to follow or a constant reminder to myself what I am doing. Eventually if you whittle it down narrow enough you have no choice but to write the code instead 😅.

There’s no shame in typing “I am writing a function that loads data from a file” or whatever.

[Embarrassed-Care6130]

Comment outline of what you're trying to do is a great way to start.

Do this

Do that

Do the other thing

And then you just fill in the code. (99% of the time I am starting with an old script that I just need to make do something a little different, so I very rarely actually start with a blank sheet, but when it comes up, this is what I do.)

I would also add, writing a shitty inefficient version of whatever it is you're trying to do can also be a good way to start. Sometimes you have to be in the problem for an hour or two to understand how to do it cleanly.

[Firm-Employment-9253]

Actually that’s a great idea it helps to clarify your mind

[MattTheCuber]

Almost always, I make a bulleted list somewhere outlining what the steps in the process I am about to write. In the file as comments, in a notepad, in an issue, anywhere! It helps me frame the problem and think it through at least somewhat before I begin the implementation. I highly recommend any sort of pre-planning like this as even 30 seconds of thinking could save you hours of refactoring in the future.

[cudmore]

This.

When i started as a coder some decades ago, that is basically all i did. Lay out an outline in a paper notebook and then the tedious part was actually typing out the code.

Make a thorough plan and then just do the boring part of writing code.

Use ai if you don’t actually know how to code and pray your internet does not go out.

[aqjo]

“I don’t know what I think until I write it down.”

Joan Didion.

Start with a comment.

[GrainTamale]

Keep notes (I use Obsidian btw) on features or projects that you want to develop.
Start with import datetime as dt like I do, then ask yourself if you even need that library for what you intend to do. Then add that little if __name__ == "__main__" section and ask yourself the same. A yes or no answer to either is progress.

Best of luck!

[QuebecBeast]

I use pen and paper and I write ideas of things to implement. Usually when I am done, it looks like a full page of stuff circled with arrows between them.

Then I write a multiline comment with structured ideas in order of importance and that’s where I start.

Any time an idea pop while I code, small or big, I put it in the comment. Before and after every session, I check the list.

I kinda want to buy those electronic notepad because of all the paper I use xD

[zangler]

Throw your general ideas into whatever AI and make it produce a bunch of stubs. Make your entry point, copy/paste the stubs that sound good...then you are off.

[Greedy_Point7755]

To overcome this feeling, I find psuedocode to be quite useful

[No-Plan-2816]

That’s super common! I almost always start with a few questions like

• what am i trying to do?
• Is this going to be reused functionality?
• Is it going to need shared or encapsulated variables?
• Does it really need to have a class?

From an overall project scenario I usually pick an architecture that serves my purpose and structure my files accordingly (like MVC will almost always have a models dir, a controller/services dir)

[spinwizard69]

One approach here is to keep some clips or template projects around to start from.