The First Line

Hello, world.

I have finished my final project for my web development course. I am proud of myself, and yet feel like I'm not quite there yet. But don't we all start from somewhere? The first day. The first chapter. The first shape. The first medium. The first line of code.

And my apologies, my possible future siblings in syntax, but I can't really refer to it as programming right now. I am not, in any sense of the word, a programmer. Yet. I can't say I program anything. As of now I fumble through functions and pick myself up from the rubble. And try again.

This last project still links right up to my paintings. It's been one of the driving forces behind my web dev journey. I've always wanted to know how websites work, I want to know how to make one, I want one of my own. Find something you love, the bootcamp said. Use that as inspiration, they said. Perfect.

I was relearning graphic design software last year, and trying to learn Figma. After I finished the HTML,CSS and Javascript course, I created the draft of my first, real, working dream website. This part of the journey wasn't as focused as the first part, when I was still looking for work. This time I had other deadlines to meet, and still, house chores. Chores never die, no ma'am.

And this is where one must plow through. When you remind yourself that you wanted this, you started this. You must finish what you started. I'd like to go all-out nerd on you. That would truly make me happy. But I'm afraid I would look back at this and cringe at the naivete. So, just a few technical tips for noobs like me:

</> When you find a willing mentor, get over yourself, swallow all pride and JUST ASK. This is going to be useful however you frame it inside your mind

</> I was into React JS this time. Some "basic" terms to look into for your first projects: useState, useEffect, routes, props vs params, creating forms (with validations), objects, functions, asynch/await or fetch, useReducer (this one I failed at miserably). If you're feeling studious today (congrats), have a look into bootstrap (personally not intending to use it, but it seems to make designing easier for non-designers. Anything that helps, I am a fan of), axios, deployment.

</> If you're like me and you were planning to "beautify" your project with dynamism and moving parts, hate to break it to ya boo. CSS doesn't work as simple as that in React apps. You might actually have to do separate functions for this (as per my research on it) Luckily this was not a requirement, so I do plan to do a deep dive on this topic for a future version of my site.

</> MVP. It's one of my favorite concepts that I picked up from studying web dev which I also use for my design and project management work. It's basically the same concept as "Start where you are, with what you have." Plan. Research. Research insanely. Do the draft. Do the final. If you think this package involves informed decisions and all that you could have done, then throw it into the universe. See what happens, what works, what doesn't. Build from there. Fail. Fail better. Build better.

</> Pick your battles, pick a project. The best way that works for me is to see things being used in practical ways than just the theoretical concepts. If there aren't any code-alongs, I find it harder. Focusing on one project will ensure that you are processing information in phases.

You'd think web development finally feeds the side of my brain that needs structure and problem-solving opportunities. If I think about it long enough, it's because of art. In my life, it has been a transferable skill. I have associated working with my hands, composition,

recognizing patterns,

the practice of it,

the failing at it,

the journey of it,

as a joy.

To finally see the output of the work and time you've put in. The knowing that one day you can get better at something. One line at a time.