From 9e927288b8c3d9b7d079d53a6499ecb2296fd761 Mon Sep 17 00:00:00 2001 From: Xevion Date: Sat, 16 Mar 2024 09:39:30 -0500 Subject: [PATCH] More posts, add more ideas/content to expand on --- src/content/handbook/applying/networking.md | 13 ++++++ .../handbook/applying/paths-to-success.md | 23 +++++++++- src/content/handbook/learning/courses.md | 15 +++++++ src/content/handbook/learning/debugging.md | 43 +++++++++++++++++++ src/content/handbook/learning/passion.md | 21 +++++++++ src/content/handbook/learning/projects.md | 10 ++++- src/content/handbook/living/campuses.md | 12 ++++++ .../handbook/living/commuting-parking.md | 18 ++++++++ src/content/handbook/living/housing.md | 5 +++ 9 files changed, 158 insertions(+), 2 deletions(-) create mode 100644 src/content/handbook/applying/networking.md create mode 100644 src/content/handbook/learning/courses.md create mode 100644 src/content/handbook/learning/debugging.md create mode 100644 src/content/handbook/learning/passion.md create mode 100644 src/content/handbook/living/campuses.md create mode 100644 src/content/handbook/living/commuting-parking.md diff --git a/src/content/handbook/applying/networking.md b/src/content/handbook/applying/networking.md new file mode 100644 index 0000000..4094643 --- /dev/null +++ b/src/content/handbook/applying/networking.md @@ -0,0 +1,13 @@ +--- +title: 'Networking' +description: 'The importance of networking and how to do it effectively' +pubDate: '2024-03-16' +authors: ['xevion'] +--- + +> This file is a placeholder for future content. See [here](/contributing) for details on how to help out. + +- Be honest and genuine +- Prefer local players over remote +- Don't be afraid to ask for help +- LinkedIn can be quite effective \ No newline at end of file diff --git a/src/content/handbook/applying/paths-to-success.md b/src/content/handbook/applying/paths-to-success.md index 1bdfaca..2c38757 100644 --- a/src/content/handbook/applying/paths-to-success.md +++ b/src/content/handbook/applying/paths-to-success.md @@ -5,4 +5,25 @@ pubDate: '2024-03-15' authors: ['xevion'] --- -> This file is a placeholder for future content. See [here](/contributing) for details on how to help out. \ No newline at end of file +> This file is a placeholder for future content. See [here](/contributing) for details on how to help out. + +- Internships + - Usually used in combination with other methods + - Low pay, mismatched work, or lackluster experience is not uncommon at first + - Getting your foot in the door is very hard +- Volunteering, Clubs, Organizations + - Unpaid, but the barrier to entry is very low + - Easy way to get experience and build a network, acquire an edge on other interns resume-wise +- Contracting and Frelance + - Difficult to break into, but can be very lucrative alternative for some + - Requires a lot of self-discipline and self-promotion +- Research + - Usually requires a good relationship with a professor + - Can be very rewarding, but is often unpaid or low-paid + - Stipend/grant-based funding (no negotiation) + - Rigid requirements, but flexible and integrates with coursework +- Network + - Whether through a friend, family, or acquaintance, a good network can get you a job + - Not all companies are advertising positions, preferring to fill positions through word of mouth + +These methods are ideal points to start from, but anything (i.e. fulltime work) is possible once experience is built. \ No newline at end of file diff --git a/src/content/handbook/learning/courses.md b/src/content/handbook/learning/courses.md new file mode 100644 index 0000000..7f68274 --- /dev/null +++ b/src/content/handbook/learning/courses.md @@ -0,0 +1,15 @@ +--- +title: 'Courses' +description: 'Required and elective courses, what to pick and when' +pubDate: '2024-03-16' +authors: ['xevion'] +--- + +> This file is a placeholder for future content. See [here](/contributing) for details on how to help out. + +- Core Curriculum can be finished in any order + - You can start work on Computer Science immediately +- Gateway courses are required and used to determine your readiness for the major + - Only two attempts are allowed in your lifetime + - You must pass with a C or better + \ No newline at end of file diff --git a/src/content/handbook/learning/debugging.md b/src/content/handbook/learning/debugging.md new file mode 100644 index 0000000..d85a9e3 --- /dev/null +++ b/src/content/handbook/learning/debugging.md @@ -0,0 +1,43 @@ +--- +title: 'Debugging' +description: 'A general guide to debugging - a fancy word for problem solving' +pubDate: '2024-03-16' +authors: ['xevion'] +--- + +> This file is a placeholder for future content. See [here](/contributing) for details on how to help out. + +- Julia Evan's Debugging Zine +- Rubber Duck Debugging + - A form of debugging where you articule and explain the problem to an inanimate object + - Can also be a person, but the point is to explain the problem rather than it is for them to 'understand' + - If you do use a person, be sure to inform them of the purpose, and be nice to them (don't exhaust them) + - Trying to simplify the problem can often generate new perspectives + - The anxiety of trying to condense the complex situation can force many into evaluating their issues comprehensively +- Write a comprehensive report before asking for help + - Effectively the same as *Rubber Duck Debugging* + - More often than not, a comprehensive report will make you explore the problem more, allowing you to figure it out + - If not, it will help others help you faster, lowering the time it takes to solve the problem + - Version, OS, Environment, Logs, Steps to reproduce, Expected behavior, Actual behavior, etc. + - This may seem like a lot, but an in-depth exploration is a good test of your understanding of the problem + - It has worked for me dozens of times, even if frustrating +- Simplify the problem as much as possible + - If it's an error occurring on a specific line, strip away everything else until you're left with just the things that directly interact or keep it happening + - Even if it doesn't reveal the problem, it can help you understand the core components and narrow down the problem +- Turn it off and on again + - While time consuming, a re-install, reboot, cache clear or reset can fix the problem + - Attempt from multiple computers, including one that has never seen it before + - Include this detail in your report if you post online +- Questions to ask yourself +- Don't ask to ask, just ask +- You're not the only one - search often + - Become skilled at googling, researching and reading documentation +- StackOverflow has a high skill floor and has become quite elitist + - If you're posting on there, 50/50 chance you won't get an answer or will be downvoted/closed + - If you're posting something they can answer, it's probably been answered before, multiple times + - If you're posting something 'new', it's probably not a question they can answer + - Funny enough, you'll still get downvoted/closed +- Try to look for communities around the technology +- Don't directly email or message someone unless you're extremely confident they're the only one who can help + - e.g. they produced the software and don't have any public forums + - e.g. they created a discussion on the same bug but did not post the solution publicly \ No newline at end of file diff --git a/src/content/handbook/learning/passion.md b/src/content/handbook/learning/passion.md new file mode 100644 index 0000000..bee3fb1 --- /dev/null +++ b/src/content/handbook/learning/passion.md @@ -0,0 +1,21 @@ +--- +title: 'Passion' +description: 'The effectiveness of passion when learning' +pubDate: '2024-03-16' +authors: ['xevion'] +--- + +> This file is a placeholder for future content. See [here](/contributing) for details on how to help out. + +- Finding your passion may take time +- Take your established interests and try to apply Computer Science + - Video games? Try to make a mod, reverse engineer, or create your own + - Photography? Build a portfolio, photo editing mechanism, photoshop extension, camera app + - Music? Create a music player, music visualizer, or music creation software +- Don't be afraid to try new things + - Everyone fails, it's part of the process + - It's okay to not enjoy something at first, find it frustrating, or not understand it. + - Even after years of experience, you may still find yourself struggling with something new + - The only thing that really changes is your ability to cope with the struggle + - Equate struggle with learning, improvement, and growth + - Take breaks, talk about it, and ask for help \ No newline at end of file diff --git a/src/content/handbook/learning/projects.md b/src/content/handbook/learning/projects.md index 11ca96f..48a76d1 100644 --- a/src/content/handbook/learning/projects.md +++ b/src/content/handbook/learning/projects.md @@ -5,4 +5,12 @@ pubDate: '2024-03-16' authors: ['xevion'] --- -> This file is a placeholder for future content. See [here](/contributing) for details on how to help out. \ No newline at end of file +> This file is a placeholder for future content. See [here](/contributing) for details on how to help out. + +- Class projects are often highly regulated - they need to be easy to complete with clear guidelines + - If you're an overachiever, it's rare that you'll be able to do something that's truly impressive +- If placed on resume, try to show that they're more than just class projects + - e.g. "Started as a class project, but turned into a major project reaching 1000+ users" +- Special classes exist that allow for free form designed projects that are closely mentored and watched by professors + - These are made in close cooperation with the professor + - Need to be planned, approved and administered by the professor \ No newline at end of file diff --git a/src/content/handbook/living/campuses.md b/src/content/handbook/living/campuses.md new file mode 100644 index 0000000..0b216c3 --- /dev/null +++ b/src/content/handbook/living/campuses.md @@ -0,0 +1,12 @@ +--- +title: 'Campuses' +description: 'Main, Downtown, Data Science, and Online Campuses' +pubDate: '2024-03-16' +authors: ['xevion'] +--- + +> This file is a placeholder for future content. See [here](/contributing) for details on how to help out. + +- COVID Online classes are still available, but have been greatly reduced +- General shift of in-person classes to SP1 (Data Science) + - Some professors show obvious disinterest in downtown commute and will provide online attendance options for downtown students \ No newline at end of file diff --git a/src/content/handbook/living/commuting-parking.md b/src/content/handbook/living/commuting-parking.md new file mode 100644 index 0000000..84f88b6 --- /dev/null +++ b/src/content/handbook/living/commuting-parking.md @@ -0,0 +1,18 @@ +--- +title: 'Commutting and Parking' +description: 'How to get to campus and where to park' +pubDate: '2024-03-16' +authors: ['xevion'] +--- + +> This file is a placeholder for future content. See [here](/contributing) for details on how to help out. + +- Campus Bus vs VIA +- Use parking lots and campus bus routes to your advantage +- Parking permits +- Hourly garages can be cheaper than a permit for some +- Parking tickets are expensive, but one warning per year + - You can appeal them, but it's a hassle + - Left unpaid, prevents you from graduating +- University Oaks close enough for biking + - Phase 2/3 have bus stops nearby (straight to NPB) \ No newline at end of file diff --git a/src/content/handbook/living/housing.md b/src/content/handbook/living/housing.md index b589e7f..cb561e1 100644 --- a/src/content/handbook/living/housing.md +++ b/src/content/handbook/living/housing.md @@ -68,5 +68,10 @@ The options below are not exhaustive, and focus primarily on the Main Campus (No - Con: Tricky leasing agreements, impossible to get out of without a replacement. - Con: You won't see the unit before you move in. You also won't know it's location. +## TODO + +- Subleasing + - Subreddit, Facebook Group, Snapchat +- Roommates [utsa-off-campus-housing]: https://www.utsa.edu/students/off-campus-housing/ \ No newline at end of file