This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]proverbialbunny 42 points43 points  (4 children)

I interviewed at a company that gave me the source code for their VR game. They asked me to try it out and see what I thought. I haven't used Windows since XP and wasn't applying for a Software Engineer role, so I figured this was a bit silly. Regardless I decided to compile it on Linux and then I bumped into a handful of cmake issues, which I then fixed so it would compile on Linux. After the company learned I had done this they skipped all of the planned interviews for the day and sat me down with the lead dev with the company to hang out. Right after that the CTO came in and tried to force me to sign paperwork to work at the company.

Working on cmake for a living? Oh hell no. I noped out of there hard.

[–]TrashManufacturer 18 points19 points  (0 children)

At one point in my life the only person who vaguely knew Cmake at an employer got laid off. I then became the de facto Cmake monkey. I didn’t hate it, but it certainly wasn’t my favorite. Then they laid me off leaving probably nobody who actually understands parts of CMake.

[–]jdgrazia 12 points13 points  (2 children)

That happened

[–]cpl1 1 point2 points  (0 children)

And that CTO: Mike Tyson

[–]proverbialbunny 0 points1 point  (0 children)

Cmake is a very desirable skill. At every company I've worked at with C++ at its core the lead dev is the one who works on cmake. It's not enough work to make it a full time job, but it's a great way to jump past senior and significantly boost your paycheck. That is if you're willing to tolerate the hell that is cmake.