We do often include affiliate links to earn us some pennies. See more here.

CodeWeavers still looking for more developers to work on Steam Play/Proton

By - | Views: 20,946

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.

Article taken from GamingOnLinux.com.
Tags: Jobs
29 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. Find me on Mastodon.
See more from me
The comments on this article are closed.
16 comments
Page: 1/2»
  Go to:

eridanired123 Sep 5, 2019
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. (•ิ_•ิ)?
Klaas Sep 5, 2019
Quoting: eridanired123
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. (•ิ_•ิ)?

Because that would make it easier for Microsoft to sue them into oblivion.
kokoko3k Sep 5, 2019
Quoting: Klaas
Quoting: eridanired123
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. (•ิ_•ิ)?

Because that would make it easier for Microsoft to sue them into oblivion.
I think they mean you'll not be sued by Microsoft for reverse enginering their code.
Why, i don't know.


Last edited by kokoko3k on 5 September 2019 at 4:04 pm UTC
Klaas Sep 5, 2019
Codeweavers 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.
kokoko3k Sep 5, 2019
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 " ?
Klaas Sep 5, 2019
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.
Liam Dawe Sep 5, 2019
Quoting: kokoko3k
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 " ?
How 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...


Last edited by Liam Dawe on 5 September 2019 at 4:56 pm UTC
Klaas Sep 5, 2019
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:
scaine Sep 5, 2019
View PC info
  • Contributing Editor
  • Mega Supporter
This is causing so much excellent confusion! :D

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.
Klaas Sep 5, 2019
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
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.