CodeWeavers, the company that helps to support development of Wine and partnered with Valve to help with Steam Play/Proton are still looking to bring in some more developers.
I spoke to James Ramey, the CodeWeavers President last night who confirmed that there has actually been a good amount of interest as the position has been open for a while. They need more though, especially if Wine and Proton development is going to keep pushing forwards.
What are they skills they're after?
- Strong C language skills. Compilers, linkers, macros and function pointers don't scare you.
- Familiarity with developing on and administering a Linux system (bash, unix utilities, package management, etc)
- Ability to understand and debug build systems (Makefiles, autotools, etc)
- Understanding of good development practices (source control, atomic commits, code readability, test-driven development)
- Self-motivated to find work and learn new skills
- Excellent debugging skills. You will be debugging applications whose source you do not have.
- No exposure to Microsoft code or reverse-engineering of Microsoft software
CodeWeavers are based in Minnesota, USA. However, this position is open to people working remotely too so even if you're not local and don't fancy moving it's still worth applying for it if you think you have what it takes.
Interested? Check out the jobs here where they also have some others open.
QuoteNo exposure to Microsoft code or reverse-engineering of Microsoft software
Why is that? I'm curious I would have thought that the other way was preferable. (•ิ_•ิ)?
Quoting: eridanired123QuoteNo exposure to Microsoft code or reverse-engineering of Microsoft software
Why is that? I'm curious I would have thought that the other way was preferable. (•ิ_•ิ)?
Because that would make it easier for Microsoft to sue them into oblivion.
Quoting: KlaasI think they mean you'll not be sued by Microsoft for reverse enginering their code.Quoting: eridanired123QuoteNo exposure to Microsoft code or reverse-engineering of Microsoft software
Why is that? I'm curious I would have thought that the other way was preferable. (•ิ_•ิ)?
Because that would make it easier for Microsoft to sue them into oblivion.
Why, i don't know.
Last edited by kokoko3k on 5 September 2019 at 4:04 pm UTC
Quoting: KlaasCodeweavers needs to be able to show that they have a clean room implementation of Microsoft technology if they want to be on the safe side. They are only able to do that if they don't employ someone that has looked at the original code or tried to de-assemble original code.Are you stating their code is not " a clean room implementation of Microsoft technology " ?
Quoting: kokoko3kAre you stating their code is not " a clean room implementation of Microsoft technology " ?
What? I'm stating that the “No exposure to Microsoft code or reverse-engineering of Microsoft software” clause is there so they are able to call it a clean room implementation.
Quoting: kokoko3kHow did you get that from what Klaas said? They can't employ people who've seen MSFT code or reverse-engineered it, so that their own code is clean. We can't make this much clearer...Quoting: KlaasCodeweavers needs to be able to show that they have a clean room implementation of Microsoft technology if they want to be on the safe side. They are only able to do that if they don't employ someone that has looked at the original code or tried to de-assemble original code.Are you stating their code is not " a clean room implementation of Microsoft technology " ?
Last edited by Liam Dawe on 5 September 2019 at 4:56 pm UTC
Quoting: Liam DaweHow did you get that from what koko said?
How did koko get what from what koko said? I'm feeling like I'm in the twilight zone. :S:
Honestly, not sure what Kokoko is getting at either! Article and follow up comments were pretty clear to me. Perhaps it's because of the reference to "clean room" which isn't strictly applicable here - wikipedia describes clean room engineering to be related to a method of software development that focuses on bug reduction.
Quoting: scaine(…) wikipedia describes clean room engineering to be related to a method of software development that focuses on bug reduction.
I think you're looking at the wrong Wikipedia article. https://en.wikipedia.org/wiki/Clean_room_design
See more from me