Hi Application Services team! Elise Richards suggested that I reach out to you about a possible collaboration.
I’m a professor at Rhodes College: a small, selective, undergraduate-only institution. This coming Spring I’m teaching an upper-level software engineering course. I’m curious whether your team would be interested in having my students contribute. Ideally I would like to partner with a team that has a backlog of low-priority feature work, bugs, tech debt/janitorial work, etc and wouldn’t mind some attention to clearing some of it. I want this to be as low-effort as possible on your engineering team; I would take responsibility of being a filter between students and you (to the degree you desire). I have experience in industry—I was at Google for 6 years prior to this fall, where I was TL of team building distributed data processing tools. Let me know if this is interesting your team; if so, we can start talking. I’m happy to VC if you want to chat in person, otherwise email/IRC/Slack would be fine. If we go forward, my goal would be to invest in ramping up to be a contributor over the next few months so that I am in a position to make sure your team’s velocity isn’t affected by interrupts. Let me know if there’s any interest and any questions you have! Thanks and best, Matt Lang Assistant Professor of Computer Science Rhodes College p.s., A little more info: My goal for the course is to have students come out of the course understanding the process and reality of real-world software engineering. I want my students to gain the process skills that are necessary for building real-world systems: deep debugging, integration challenges, testing and deployment, configuration management, etc. The class is 25 juniors and seniors with C++ experience. I had a similar demographic in a distributed systems class and got them ramped up to Go pretty quickly; I would image that Rust wouldn’t be a barrier. I would be dividing them into groups and overseeing them, and would filter any interrupts that would come to you. Here’s the course description if you are interested: "The software systems we often find the most useful and magical are also the largest and most complex to build and understand. In order for these systems to be reliable, maintainable, and secure, they must be built according to disciplined and well-founded methods. This course examines these methods—both in the large (defining requirements, system design, architecture patterns, software process, etc.) and in the small (version control, testing, benchmarking, code review, etc.). At the same time, students will engage in the construction of a large software system or feature." _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
