...It's pretty easy for clients to maintain in the long run if they just wanted help with design + full set up, and lets them manage more powerful tools like a storefront and related e-commerce plugins like Stripe or a plugin that calculates taxes. Easier on the agency too :p
Day 86 #100DaysOfCode: Technically the only coding I did today was some CSS, but I spent a couple hours fooling around with WordPress in a local environment using Local by Flywheel. I knew WordPress was easy to manipulate, but I get why a good number of agencies use it...
I will say not all of the content will be applicable to juniors, but I thought the brief overviews they give for concepts were helpful and clear refresher.
Seems like I'll be able to use it in new ways even further down the line, which is pretty cool!
Day 77-85: Spent the past week or so focusing on algorithms. @InterviewCake's structure and overview was really helpful (their course is discounted for the time being, which was really nice). Had an interview yesterday and didn't use any of it π but hopefully for the next one!
Day 76 #100DaysOfCode: Worked on the errors I got from the fetched data - couldn't figure out where exactly they were coming from (I was getting good response codes). With the error being caught, the page is unable to do anything that signals the event was made successfully.
Day 72-75 #100DaysOfCode: Added a couple more fields to the add event page and had some back and forth to figure out the best way to do approach some aspects. Form is now functional! Getting some errors from fetched data from other code that I'll resolve before pushing up.
Day 70, 71 #100DaysOfCode: I've had to put it off for a bit, but I am finally almost there with the add event page I'm working on (had to familiarize myself with the code again). Testing this is not that straightforward, but should be done soon.
Day 68, 69 #100DaysOfCode: Worked on refactoring code from static HTML to rendering from an array. This originally presented difficulties when updating information (finding + remembering to edit all necessary info) and inserting info (each `li` also req'd updating multiple nums).
D 67 #100DaysOfCode: Some maintenance for a website I'm helping out with. Will be thinking about ways to automate the process now that some bulk edits are being requested. A lot of the code is written in plain HTML and it's a bit much for updating pages with more content.
D 68 #100DaysOfCode: Took a fun break to think through the best way to set up a family tree. Trying to set up my next project, am considering working with TypeScript and Vue to learn some new technologies!
Does anyone know any third-party APIs that are going to be shut down in the next week? Just let me know, and I won't use it for my current project ππ π The Star Wars API just shut down two days ago so I need to start my coding challenge over with another one lol #100DaysOfCode
@DanielHoppener Nice! Wish I was able to finish mine before it shut down. I don't think so - it was someone's side-project, and they stopped maintaining it four years ago. They're more focused on their PokeAPI, which I'll be using for my project going forward.
D 56, 57 #100DaysOfCode: Finished adding user endpoints and testing for SWS. When debugging I tried to figure out what the failing code had in common. I later realized it was that they were all copy and pasted (I wrote a typo in the original) π€¦ Anyone else ever done this?
D 53-55 #100DaysOfCode: Started on the backend for my SWS project. Finished the authentication and tests :) Would love to show you some snapshots but gotta love the server-side haha
Been working on a new project using SWAPI, the Star Wars API. I'll be referring to it as SWS going forward in my #100DaysOfCode tweets! Excited to show it off a bit in about a week's time.