100 Days of Code: CRUD, suckas

I’m about to vomit. I have my latest DoC as a PUT request. Now this is a code to be done in a day, and I’ve got 80 minutes before it’s no longer today, but I am happy with it. I can return and style it better an other day. I don’t care. Tomorrow is a day at the lake.

The important thing is that I can PUSH, GET, DELETE, and PUT. Things that once made me cry now make me dance. Yes, it does help that I’m not getting graded, and my house isn’t flooding. But even after the house was cleaned and I was assured that I’d eventually get it, I let fear and a severe lack of self-confidence become huge walls. I know walls. I’ve run a few marathons and done long rail-trail rides. Unlike those walls, I do not have glucose gels for my psyche. 

There will be another Ajax-like bug bear for me, but now I have this to look back on. Yes, I got stuck, but I got unstuck. Glad to have this for when I need it later.

Ahh. Now to fill that database with greyhound fosters.

100 Days of Code: Day Thirteen

Ermahgerd! That took forever!

I want to get into edtech. When I taught, I enjoyed creating my own games, songs, etc. to help the kids learn and enjoy learning. A typical exercise is unscrambling a word, so I wanted to try to make my own. 

This turned out to be quite the endeavour. I had to play around with the scope and reset. I could bore you with the long tale of it all, but I rather not. I asked for help from my cohort and former instructor. Was tempted to get needy (was probably very needy); however, I did not once say “Just tell me!”. That never is helpful. This is not an assignment. This is me playing around. Coming to a working exercise the hard way ends up teaching me more. Giving me the answers doesn’t make me feel good in the end. (Much happy happies to those who helped.)

Unscramble German words for animals

100 Days of Code: Day Nine


Not really a lesson on probability, but an exercise for me in making random number generators and playing with JQuery.

I find that the hardest part is coming up with something to do and then not having that explode into something too large for the amount of time left. If I’m not struggling coming up with an idea, I’m getting too many and they’re vying for attention in the noggin. 

DRY! Yeah, I know that I did, but I just started out with doing 1 out of 2 and then 1 out of 100. I don’t know if it was boredom or greediness, but I did a bunch more in between. I think that interrupted the original plan, so where doing about the same code(ish) twice isn’t really repeating myself, doing it seven times is. If I were to revisit (and I might), I’d see where I can replace repeated code with a function.

Clearly I am on a math kick: 

You’re probably wrong

(Nothing done yesterday. Vertigo + dehydration + migraine = “Feck off, mate!”)

100DoC: Day Eight

Ha ha! Bite me, Leibniz.

And here I was thinking that redoing Day Seven’s Pi function took up my entire day. What on earth can I do with that leftover code? Hm… I was entertained by the Gregory-Leibniz Series and how it was more accurate the more iterations it made, so I wanted to have a little function to look at how close the output get to Pi when the number of iterations increases.

100DoC: Day Seven again


While playing with my code, I learned that toFixed goes out only to 20. How did I miss that, and, more importantly, WHAT IS THE POINT!? I wanted to take Pi out further. I don’t like to be limited with pie or Pi. Other than hardcoding the first 100 decimal places, how would I do it? 

I looked at Leibniz formula: 

I kept increasing i. The more iterations, the more accurate. See my problem there? If I just do i=5000, then it doesn’t even come out to 3.14159, the digits most people remember. When I’d take it out to i=1000000000, it was more accurate, but the program was slower. And I still couldn’t get it to show more than 20 decimal places. I downloaded some libraries to help (bigdecimal, decimal), but I am still stymied. 

I learned plenty, but I also learned that I’ll let the computer limit the user and change the system. I also added validation codes. I might know what numbers to enter, but I have to remember to code for weenies out there.

A lot learned. I’m sorry that I can’t do the Leibniz version. That was fun. I’ve kept it in the code but commented out for when I’m alone at night and want to nibble on German pi while ogling this sex machine: 

100 DoC: Day Four

Holy jackomole this took forever. If you asked me what I learned today, it’d be that there’s a feckin’ world of difference in JavaScript between mouseover and hover. Basically, hover is fun, and mouseover is just a jerk and needs to die. It took me forever to figure out that I was using the wrong method. Well bugger you, mouse. How many things do you really need? You have mouseEnter, mouseOver, mouseOut (not at all like peace out), and even a mouseLeave. Just stop it. And you also get hover? No wonder you’re considered vermin. 

Sigh. I learned something. It took all night, but I eventually maked sumpin. 

Yesterday, my friend’s puppy was hit by a car in front of her. River P. Wafflenut is doing well. Multiple pelvic fractures, but that’s all. Yeah, I know. “All”. But nothing wrong with the internal organs. It’s a long road, but she’ll come out ok. I’m more worried about my friend. My original DoC plan was just to do the nav bar, and I did. Yeah yeah. It’s boring. Nav bars are the broccoli of a page to me. After taking my friend to the vet to visit RPW, I thought I should take a break from the portfolio’s look and the broccoli bits and make something for RPW. 

Find RPW