3 ms·

Have you written any C at all? This post sort of reads like you don't know what you are asking for... C is a lot of fun, I don't want to discourage you, but if

Have you written any C at all? This post sort of reads like you don't know what you are asking for... C is a lot of fun, I don't want to discourage you, but if you don't have any experience with it the odds that you are going to be able to get a job in it are low. C is a high-risk high-reward language and writing programs in it competently requires a lot of patience and practice. It isn't shocking that even entry-level positions would want you to already know quite a bit about it. Speaking from my own experience (and this is a route that might work for you if you are sure you wanna do this): At a previous employer, I worked as a C# developer at a transitioned into a C/C++ role when there was an opening on that team. I didn't do it because I wanted to learn C specifically, but that was one of the appealing things about the opportunity. (I also had already written some C in college, though that was years ago.) So looking for an organization that does C and other stuff and starting in the other stuff might be a valid way to go. That said, the company only took a chance on me because I was already fully competent in the organization's domain and I had proven myself in a less challenging position; they believed I could learn. It was a huge learning curve for me and it took several months for me to get up to speed and be useful as a pure C developer, and this was with more experienced developers mentoring me every day. I am still nowhere near being a C expert; I am just good enough to be useful. (I also no longer work with it day-to-day, because I'm not at that company anymore, though I miss it sometimes.) Honestly, it sounds like you should focus on your family first and your C aspirations at home or as a hobby. Think about how this ends: If you get into a position using C, and find it hard or just decide it isn't for you, do you really wanna be worried about losing your job or doing badly at it while dealing with your new baby?

xtracto 4y ago
You are spot on with this comment. I've done misc small/medium sized software at various times, first in Uni to implement a compiler, later programming Nintendo DS and Wii homebrew using DevKitArm and DevKitPro. Some days ago I started designing/implementing a system for "password sharing" and thought of writing at least part of it in C: I want to be able to get a password from say, KeePass2Android, then encrypt it with some OTP key (seeded from a preshared key), then generate a sound with it (say using DTMF like tones) and send it through the phone's speaker. The C app would monitor the sound (microphone, maybe through SDL library), detect a specific tone/wave as the "start" of the message, decodify the message, obtain the string of the encrypted message and decrypted with the OTP key. Finally, the C app (via xdotool ) would type the password as a keyboard. I wanted to do this as an easy way to use my phone as my password manager for my computer. I started to write the C part of the application, SDL I've done before, I read a bit about Fourier Transforms and the libraries I'll have to use. In the end doing it in C is going to be a tremendous task, given that in languages like Python there's a lot of stuff already solved. I love C and its heritage... but I really wouldn't think in starting a serious project in it at this point it time.

xtracto 4y ago

You are spot on with this comment. I've done misc small/medium sized software at various times, first in Uni to implement a compiler, later programming Nintendo DS and Wii homebrew using DevKitArm and DevKitPro. Some days ago I started designing/implementing a system for "password sharing" and thought of writing at least part of it in C: I want to be able to get a password from say, KeePass2Android, then encrypt it with some OTP key (seeded from a preshared key), then generate a sound with it (say using DTMF like tones) and send it through the phone's speaker. The C app would monitor the sound (microphone, maybe through SDL library), detect a specific tone/wave as the "start" of the message, decodify the message, obtain the string of the encrypted message and decrypted with the OTP key. Finally, the C app (via xdotool ) would type the password as a keyboard. I wanted to do this as an easy way to use my phone as my password manager for my computer. I started to write the C part of the application, SDL I've done before, I read a bit about Fourier Transforms and the libraries I'll have to use. In the end doing it in C is going to be a tremendous task, given that in languages like Python there's a lot of stuff already solved. I love C and its heritage... but I really wouldn't think in starting a serious project in it at this point it time.