Sometimes I wonder if anyone is reading these. I say this all the time on here and the last time I did #100DaysOfCode but the blogging part really is for me. To me it feels like something I need to do, write and reflect on my learning that day. Even if it's just something like this:
Today I coded in coding language and it did stuff
Psh. Silly Python.
Today I did do some work on my website. I very much doing nit picky design things. Trying to get things to center or move around. Browser developers are insane. I don't even know how they get the browser to do some of the stuff that it does.
Maybe I do this because I do actually think someone will come and read these. I mean, I put the posts out there right? I tweet them to my 200 some followers and I'm like -
Here's what I do know. Coding is hard. Back end coding, front end coding. Encoding, decoding, recoding, uncoding, and even ex-coding.
(I don't know what any of those last few mean but I read them on some street sign in northern Missouri in the middle of the night and there was no one around to confirm or deny it)
I don't know where I was going with this.
...
Maybe if I give it a little bit of time, it'll come back to me...hold up..
..
I didn't really code until later in the day today. I spent a lot of time yesterday working on something that didn't end up working and most of the day today stressing out about a project I want to do but don't want to do with my client. It's complicated because it's totally the project I want to do but it's working in a way and with people that I wouldn't really choose. Just the idea of the project alone, not even the project itself was taking up a lot of space in my mind .
Coding takes enough time in my head as it is.
I hope that I can get better at making websites. I think that's why it never took is because the whole process seems less than automatic and responsive. With Python I can type a bunch of stuff in and Python will tell me something but sometimes you code your face off in HTML, CSS, or JavaScript and you get a big blank screen, no read outs or anything and you may have technically done everything correct but who knows what you didn't do to get stuff to appear. I'm sure the other side of that is that's bad testing if you don't know what you're working on is not working right?
Like, never sink tons of hours into your code without testing it. How do you test it? Just run the dang thing.
Alright. Thanks for coming all who do on
and enjoy your weekend.
ciao
2019-08-03 02:52:48.728094