I’ve gone back into Skillcrush and looked again at the project at the end of the course; it’s in four parts and now I’ve done three. I still hadn’t wrapped up those other lessons I couldn’t crack the code (it’s still funny!) on. It’s an exercise where we keep doing more and different things to the same code, which we copy and paste into their editor with each new piece. I’m trying to get it all up and running in JS Bin so that I don’t have to do the copy paste. With their layout, after I get the solution code, I have to scroll up and down to compare their code with what I’ve written and it makes me nuts, basically.
But of course this new bin is fighting me and giving me some long-ass weird error message in the console.
I’m chatting in Slack with an instructor about it now, actually. It’s even weirder because she says that she can run the code without any errors, so what the hell.
For sure it’s been helpful to have a second go at the material and I think/hope it will make me feel more confident/like I know what I’m doing. At the very least get me to finish the assignments at the end of the Skillcrush course so I can move onto the next class, which is Responsive Design, which I’m psyched to learn.
Codeacademy also has an Intro to Sass class that I want to come back too, as that’s something I want to learn.
Because I am so SASSY. (Not really, actually).
Had a lesson about debugging, and Skillcrush shared this article – Teaching Novice Programmers How to Debug Their Code over at code:union by Jesse Farmer. It’s a really interesting article despite the somewhat-uninteresting title. The article’s point being that debugging is a skill that all programmers need, and so teaching of that skill is something that should be emphasized and intentionally done.
The idea that debugging means you didn’t do a good job in the first place definitely strikes a chord in me. “[Students] often feel that [debugging] time is wasted or that it’s a kind of punishment for them not being smart enough to write the correct code the first time through. “If I knew what I was doing,” they think to themselves, “I wouldn’t have to spend so much time debugging.” ”
The article also notes: “Teaching [students] how to debug their own code effectively is the single most valuable skill we could teach — it’s the skill that makes acquiring all other programming skills easier.”
Anything that is going to make acquiring other programming skills easier is something that I want to know how to do, so bring it on, buggy code!
Coming up, we start learning about jQuery. I’m stoked.
Yesterday I finished the Visual Fundamentals class. Not sure why it was so tough for me, but glad it is done, and I can understand better how a PSD comes together. Came up with the above logo (?? I think? made it when i was trying to work on the “simple icon” but I think it’s really more of a logo), and also the actual site icon that is showing up in the browser tab. Super duper cheers to K. at Skillcrush, who helped me to get the icon to a point where I felt like I could move on, and for saying nice things about it.
Kudos as well to Adobe Illustrator for letting me have ONE MORE DAY in the free trial; was pretty sure the trial was done but everything was loading up ok – started to feel like, ok, I can still do what I need to do, when a screen popped up saying the trial was over. Unnnggghhh. But it had a handy button that said “extend trial” and so I clicked on that and was granted one last day. Whew.
Oh, and the Skillcrush folks managed to get me squared away with my push to Github. Still not entirely clear on how I went astray, but hope to keep creating branches, staging and committing them, merging them and then pushing to Github so I can get lots more practice.
I’m at the point in the Skillcrush course where I need to create a “simple icon” in Illustrator. I’ve been noodling around with the Bezier game – https://bezier.method.ac/ – to try and feel a little bit more in control of the pen tool. It’s helpful, for sure.
I’d like to create an icon for this site and also for myself, for freelance/side projects.
I haven’t gotten very far. I’ve done some sketches, but nothing that I’m crazy about.
I have to get this completed in 4 days, when my Illustrator trial runs out.
I also did some html-ing of the practice PSD I’m working on. In addition, working with git to create a new branch, merge it with the master, and then push it up to GitHub. Looks like I successfully did those first two things, but am stuck on pushing it to GitHub. Skillcrush has a main “questions” email that I have written to multiple times – they are super helpful and get back quickly. So I’ve sent along my screenshots and will hopefully get an update on where I went astray, and then actually have an updated repo.
Tonight I just added all the text to the html. Next I want to link in the images. And THEN tackle stying.
I’m taking the Break Into Tech blueprint from Skillcrush. The course has three parts, and I am at the beginning of phase two.
Phase one was lots of HTML and CSS, and then learning to work in the terminal, and then Git and GitHub. I really enjoyed these classes. I don’t think I made anything super amazing, but getting results and problem solving along the way was hugely satisfying.
I’ve been working in Atom to type code; have dabbled in codepen, set up in GitHub, and got my subscription to Photoshop.
For phase two, you can choose different tracks: designer, developer, or designer & developer. Basically, I want to learn ALL THE THINGS, so I’ve put all the courses into my track. I’m in the first class, Visual Design Fundamentals and Tools.
The main thing I’ve learned so far is this: I don’t want to be a designer. I appreciate good design and feel like I can recognize “bad” design, but it’s not my strength. I miss coding. I’m slogging through Visual Design Fundamentals and Tools with my eyes on the prize:
I’m very excited.
In the meantime, to try and keep coding a bit because I miss it and don’t want to forget everything I’ve learned, I’ve downloaded a PSD and am attempting to code it; follow along in GitHub!