Get idea, buy domain, make git repo, let the domain expire, post memes about how side projects are always abandoned!

git init

>Have idea
>Create repo
>Never touch it again

My process to start new coding project?

Unless it was dictated by the powers that be, my process usually begins/began when I hear..

"It's impossible for us to make the program do that" or equivalent negative comment.

It triggers a "Someone hold my beer" area in my brain.

- have a cool idea
- the idea is way too ambitious
- think about it for a few days
- start coding
- lose interest and never touch it again after 4 days

Every time.

Give up, start notebook, cry, yell, scream, pull hair out, close notebook, come back in a few months and finish it in one day. 😐

Read 1/5 of the requirements and then fire up VS and start coding.

I begin by just writing my ideas and them attempting to roughly image their execution in my head, and then start to write the code. I found this method to pose the smallest amount of holdups and issues. Of course, you might have to rethink some procedures but it mostly works.

mkdir <name here>

Whiteboard the concept, tell a friend who hypes me up, never speak of it again.

Come up with Idea, sketch outline, feel really enthusiastic, come up with new idea, get distracted, repeat

1. Think about it.
2. Get super hyped.
3. Tell everyone.
4. Go to step 1.
5. Plan it
6. Execute
7. Profit.

Going to the office when the girlfriend is working from home.

But most of the time, I knowingly stay home too

Step one, Find free time
Step two, complete first one first

Have idea, lay ground work, get user interface designed, find out someone already had the idea and did that, repeat.

copy code from old projects. also a hefty dose of Stack Overflow.

For a Web project I usually start with copying a minimal boilerplate node app, find some api I wanna use, copy paste a single example of some data I wanna display and render something on a html page as fast as possible. Seeing stuff on a page motivates me to keep going and helps me figure out the most essential direction forward.

1. Put on my lucky pants
2. Code
3. ???
4. profit $$$$

Control projects already realized
Design in Figma and Prototyping
Class diagram
code
*I wake up from sleep*

I feel compelled to figure out how to use software in a gaming setting to teach skills like CS and Math. But do it in a way that is fun and not feeling like a "math game".

I want to spend more time learning about algorithms, architectures, design approaches, etc. Writing such a game would force me to understand what I present in a very intimate way.

I can see a way to create algos in game using very visual ways. Then allowing someone to make superstructures combining those algos to solve tasks.

I was inspired by how some algos require data to be sorted a certain way before starting. As the algo as a side effect resorts the data to know when it has completed. I realized if an algo is generic enough it can be combined just like functions or objects.

I also want to learn math better, especially in conjunction with code. So making a platform for learning these would be a lot of fun. I would definitely want both visual and textual interfaces to the code. I have to imagine a real programmer being frustrated with a visual interface unless it was really compelling.

I find it interesting that a lot of algos are represented visually when trying to show how it works. I realize some probably cannot be visualized so easy though.

I also want to use software like this to teach someone to think more deliberately and help people be more disciplined in their thinking. I know I could use this.

I have a secret goal of being able to use such software to help someone become a math/programming wizard. I don't know if this is achievable, but having exercises that help solidify root concepts in a fun way would be really useful IMO.

1. Where does it run
2. Who runs it
3. did i put every bit of email conversations about errors in my archive?

I search for a problem. Write down all of its aspects. Write down the process I would like to implement for each aspect.

At this point I ask myself which language/db/library... is compatible with my processes. I write down all the data types I would probably need and a rough outline for the ui.

After that I just start coding and go with the flow 3 rewrites later I need a break.

Not very efficient start.

ALT, F, N

Visualize the entire complexity of the content within the project so that you know what data users will need to access, and compartmentalize those in to separate modules that you can build on over time. Think about any limitations with accessing that data (does the user have that role, what if the data is accessed simulateously, how to handle the same user accessing from different devices etc).
Think about the devices being used - is it going to be a website, an app, both? How best then to access the data? Direct access to a database, or an API system?
Then think about the front-end design and how to simplify the view right down as much as you can. Again, break it down in to modules.
Then decide on the technology you want to use, and what libraries would help simplify things.

These days I like to use JSON API's to access DB content because app and web technologies change quite often but the API will be accessible to whatever I use to build it.

For websites I love using Laravel, which simplifies the back-end tasks, and mdbootstrap which simplifies the front-end tasks and looks "appy".

Be interrupted by request for help. Needed help is much more interesting than my main project because 1) need for it is so clear 2) and it's skunkworks without stifling PM oversight. If result of helping is deemed good enough it becomes my main project and old project gets another lead dev or is on hold until I get back to it. Usually this cycle repeats around 1,5 years.

I usually start with a sketch on my phone ( Thankfully, I use a Note device, which comes really handy ), make the data structures, Look for available resources, choose the language/library/framework to build with, discuss with some of my friends if they think its a good idea, if they do if they want to become its first customers, & after that I start coding and showing to my friends & get feedback & keep going until I publish it for masses

Mull over the flow and data for days. Write tests first as small experiments to explore the core functionality.