pittcsc / pittcswiki Goto Github PK

it should say built with <3 by pittcs because we built it with love, link to the github source, loook a little nicer, and rn it is position fixed at the bottom instead being a good footer

https://docs.google.com/presentation/d/1kNsMDk4H8d8WD42Ai7JGNp5w62mKQTow-T_EftpGXgo/edit#slide=id.g76301bc034_0_465

It would be cool if there was an easy way to collect information about company's and how long they take to respond, what their interview process is like, in a structured way

But, this is not the most necessary feature

When I click on a course on my monitor, the course's info button is super tall. Looks great on my laptop, though.

Added sources for where to interact and hangout with all the best people cough Pitt CSC PLUG

Provide a platform for Pitt CS students to share cool technical things, reminisce one college/interns/life, complain about Pitt etc.

For example, say Ming wanted to get into web development. Where should he start? Should he learn it?

We should have a section of the wiki for "How to get started with ____" that gives really clear instructions / links to good resources. Like webdev should be pretty easy to get started with, but the sheer amount of crap online makes it hard to get started.

Essentially giving direct links of where to code, templates to follow, how to pull requests, etc.

i feel like i should not be allowed to edit this -mat

ming smells bad

This is in relation to #27

As Jen said, it would be a bad look if this gets outdated in 5 years, so we should have it be suppppppppppppper easy for a new wiki maintainer to come in and fix it up.

This probably means something along the lines of:

• Documenting this repo
• Having CSC be responsible for maintaining the wiki
• Having integrations so that we do not get outdated courses
• Make updating content as easy as editing and updating a markdown file

This needs to be set up organizationally through CSC.

• PittCAT is insane

gotta make better logos and update the meta information for the html site

<meta property="og:title" content="Example Page">
<meta property="og:image" content="https://example.com/images/image.jpg">
<meta property="og:description" content="This is just an example page.">
<meta property="og:url" content="https://example.com/page.html">
<meta name="twitter:card" content="summary_large_image">

Maybe this should go somewhere in the career prep / zero -> offer thing

Right now the scraper scrapes courses.sci.pitt.edu and puts it in a file. We don't really need to run the scraper to update the courses, because we already have most of them.

But, we should still check the courses SCI offers, compare it to the ones we have, and notify of the newness so its easy for someone to check.

So, fixing this entire mess:
https://github.com/PittCSWiki/pittcswiki.github.io/tree/master/helpers/courses

Similar to #1

After we publish this wiki there will probs be a lot of CMU students tryna transfer to Pitt

We should focus on getting the core functionality first (like making it maintainable, search, getting stuff written, feedback first), but it is also important since the wiki is going to be read a lot that it has a unified design.

This book talks a lot about how exactly to make that happen and is pretty good:
https://refactoringui.com/book/

Need to decide on a sort of visual hierarchy. We are using TailwindCSS, so it is not a lot of work to pick classes

• Maybe have automatic gantt charts with mermaid js

So this would be take a short survey and then it would give them a list of companies to shoot for.

Coming off a comment made by @varughese on issue #8

This is essentially linking to syllabi but potentially getting information from them for the description or course content of a course.

Need to make sure mostly public files are inserted cause I have a bad feeling if we take private syllabi and make them public could cause issues

Not a lot of internship guides give you tips on how you should fill out a team matching survey or preference form. I had to do this for Google and Stripe and had no clue what to do. Also for Qualtrics, JPMorgan, BNYMellon etc. How do you know how to order certain things, what should you write etc.

Should be a part of a "After you get the internship" section

I would write this guide, but I am not smart enough to ☹️

Ask alumni, visitors, anyone to buy us pizza

Example resume collection
Resumake and how to use latex to update it

Interview

• All about knowing your data structures and practicing

  • Algorithm handbooks,

• Information firehose, so my best advice is just start. Here's a list of some plans to help out an abundance of links. My advice - just start. And apply to a lot of companies to get practice talking to recruiters and doing interviews. These will make you better

we want to know which pages are most popular/visited, to know what to put most effort into

also if we add search, analytics on what search results are incorrect would b nice

On mobile, consider adding a back button because the course info page fills the entire page and could confuse people.

pilot course, rohits idea, i like it

Potentially just redirecting here as this probably would be a better spot for recommending new features and the such.

We are going to have a lot of information on this wiki if we actually end up finishing this lol.

A search option would be very helpful. Also, it would force us to think of a good way to structure the information from the beginning.

In my mind, I am imagining something like how the Stripe docs search works: https://stripe.com/docs

Resources
https://www.algolia.com/for-open-source/
https://www.gatsbyjs.org/docs/adding-search-with-algolia/

5 Tips For Success

• Solid Resume
• Apply EARLY
• Study Interview Questions

Features:

• Create a ranking system for how safe a company is
• How much skill do you need for a certain place?

Including one's locally, abroad, and even better corporate hackathons (cough code for good)

Stuff you need to bother an officer to get them juicy, juicy details

Give all the resources to give intuitive approach to learning the inner workings of different programming languages. And not just wow look you can do if statements and for loops but more focused on the design of the code, how the programming paradigms work.

This will involve probably two parts, one difficulty of lecturers and difficulty of course. Cause a course could vary depending on the lecturer