Graduation thesis as work experience

- You're going to get shit code, you're not going to get the source code carried over, - I couldn't verbalize it well, so I was thinking about it bewilderingly, - "Isn't it because you're doing 'the [[thesis]] as [[work experience]]?'" - The first time I saw this, I was surprised.

What do you mean?

- A thesis that emphasizes [[experiencing the process]] rather than research results ([[human resource development]]) - We want to give them the experience of building software from scratch, so we don't take over their assets. - It's not worth passing on because those people created it.

I see.

• Well, it’s certainly hard to do “continuous software development” with people who graduate and are gone in a few years, so it’s a form of “experience the process and bye-bye”.
• In the first place, when novelty (patentability) occupies a large weight in the evaluation function, I think the problem is that the evaluation function is crazy because it encourages the act of destroying and rebuilding new software rather than improving existing software, both in universities and companies (…).

prosym65

---

This page is auto-translated from /nishio/職業体験としての卒論 using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I’m very happy to spread my thought to non-Japanese readers.