I'm a second year student at UW majoring in Computer Science and ACMS. I took CSE154 during Spring 2018 and I enjoy designing and developing websites.
This quarter, I'm taking:
Feel free to email me at email@example.com if you have any questions.
I co-founded a RSO this spring called uDev, which is dedicated to helping students get hands on experience working in teams with web development projects. We work on project ideas involving the local community, creating real solutions that solve real problems. The team's first project is to create a better RSO directory. Feel free to contact me after this class is over if this is something you're interested in.
One of the projects I made using the skills I learned from this class is a chrome startpage extension that has keyboard shortcuts that take you to different websites when you open a new tab. A user can edit bookmarks and have them sync between devices using the Chrome storage API. Still a work in progress.
Come! Attendance counts.
Ask questions and participate. Don't be afraid of asking a "dumb question". If you have a question, chances are, someone else has it too.
Do the lab problems. Even though they aren't necessarily graded, they're really helpful because similar concepts are likely to show up on homework and exams.
Go to the Web Programming Lab (WPL). This is a great time to ask any questions that come up about the class or about specific homework assignments.
Start early! These homework assignments can take a long time. Treat your late days as a safety net, not a excuse to procrastinate.
Read the spec carefully before starting.
Check and double check your homework with the spec after you're done to make sure aren't missing anything. It sucks to get points docked for small mistakes and I don't want to do that to you guys. I like to print out the spec and check off every single bullet point against my code/output and mark anything I need to go back to and fix.
Do practice tests. As many as you can. Practice by physically writing out the problem instead of typing it out to get used to writing code. Also, try doing tests while setting a time limit.
Get familiar with the cheatsheet. There's a lot of syntax in this class and we don't expect you to remember it all, but you wont have time during exams to spend a lot of time searching through the cheatsheet. A good idea is to print out the cheatsheet and do practice exams with the it to get familiar with where to find different information and/or annotate/highlight your cheatsheet to help you find info more quickly.