Once upon a time, Computer Systems was a broad field encompassing everything from hardware to software. The incredible growth and success that our field has experienced over the past half a century has had the side effect of transforming systems into a constellation of siloed fields. I'm going to make the case that we should return to a broad interpretation of systems, undertake bolder, higher risk projects, and be intentional about how we interact with other fields. I'll support the case with examples of several research projects that embody this approach.
When do you allow for the evolution of existing software versus throwing it all away and starting over? This is a question that all software developers will face many times during their career, in both small and in large ways. Too often there is a strong urge to start over with a clean slate, getting rid of all the cruft that has built up over the years. Unfortunately the decision to succumb to this urge is taken with limited guidance, or clear reasoning.
InDuke TechConnect brings students and employers together for networking and education. Each year, employers connect with Engineering and Computer Science students in an open, dynamic networking environment. Students come prepared with resumes to meet industry and tech representatives to learn about employment opportunities available, the characteristics employers seek as well as a realistic and insightful view of the job market and career paths for students interested in engineering and technical careers.