TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Unsolicited advice on CS independent work (2013)

91 pointsby lord_sudoabout 5 years ago

5 comments

pton_contextabout 5 years ago
A bit of context for non-Princeton readers (commenting with a throwaway because I don&#x27;t want to dox myself).<p>You can take the CS major as either a Bachelor&#x27;s or an Engineering degree. Princeton requires all Bachelor&#x27;s students to do two semesters of &quot;independent work&quot; their junior year, plus a thesis senior years. Engineering students have to do one semester of independent work, but they have to take additional courses and have more specific requirements. (The CS BSE degree is currently unique in not requiring a thesis.)<p>For many departments, junior independent work is a 20ish page research paper you write over the course of the semester either as part of a seminar or one-on-one with an advisor, so the CS independent work is intended to be roughly equivalent in terms of rigor. It&#x27;s my understanding that most CS students work on a significant piece of software with a writeup at the end of the semester—often (but not always) in a semester on a single topic (eg computer vision, digital audio, etc) junior fall, and one-on-one with an advisor (or in a lab) junior spring. BSE students will often do their one semester of independent work senior year, in either form.<p>It&#x27;s often pretty daunting staring at these requirements—and a lot of the onus is on you, the student, to figure out what you want to do and initiate it—so this advice seems to me to be aimed at students starting to plan their independent work.<p>Don&#x27;t take this as gospel—I&#x27;m actually not a CS major, somewhat ironically, though I have many friends who are. Just hope this helps to contextualize Kernighan&#x27;s advice.
评论 #22994740 未加载
redis_mlcabout 5 years ago
In case you&#x27;re not aware, Brian Kernighan worked with Dennis Ritchie and Ken Thompson at Bell Labs. Brian wrote a lot of the Unix text processing utilities, and is the &quot;k&quot; in awk.<p>&quot;In 1970, Brian Kernighan suggested the name &quot;Unix&quot;, a pun on the name &quot;Multics.&quot;<p>His family is from Canada. I had the opportunity to attend a small lecture at U. of Waterloo on &quot;Little Languages&quot; when he was in town in the mid 80&#x27;s, with about 10 other students. One of my biggest influences.<p>Some context on the article link. There was a time when CS was a novel area of research. A lot of the experimentation into OS theory was made obsolete by Linux, since you could just tweak an Open Source kernel instead of doing a PhD-length project in schedulers, etc.<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Brian_Kernighan" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Brian_Kernighan</a>
评论 #22992805 未加载
评论 #22992681 未加载
_hardwaregeekabout 5 years ago
Man I&#x27;d love to have a two semester course where I could work on a project and get advice from <i>Brian Kernighan</i>. I hope all the Princeton CS students understand how lucky they are
评论 #22996075 未加载
评论 #22992982 未加载
jjiceabout 5 years ago
As soon as I saw it was from princeton.edu, I was hoping it was Kernighan. I was not disappointed.
eatbitseverydayabout 5 years ago
This seems to be from 2013:<p>&gt; Sat May 11 18:00:52 EDT 2013