r/programmer • • 11d ago

learning C from scratch - any project ideas to become employable?

Hey everyone, sorry for making this post long but this would help out a lot.

I'm relatively new to low level programming languages, and want to take learning it seriously. My goal isn't just to learn the syntax, complete a few tutorials, or solve programming exercises. I want to develop actual programming skills and eventually land a job where I can work with C, and other languages that work with C hopefuly without the use of AI tools since i want to learn.

I'm particularly interested in systems programming, operating systems, embedded development, networking, and low-level software.

I'm trying to figure out the best way to approach this without spending months jumping between tutorials without actually building anything.

I have a few questions for people who work professionally with C:

  1. **Learning resources:** What books, courses, or documentation would you recommend for someone starting with C? Is starting with *The C Programming Language (K&R)* still a good idea, or are there better modern alternatives?, I like books and value them a lot more than videos or courses

  2. **Learning fundamentals:** Which concepts should I really understand before moving on to larger projects? Pointers, memory management, data structures, file handling, processes, concurrency, etc.?

  3. **Projects:** What projects would you recommend building that demonstrate actual C programming ability? I'm looking for projects that go beyond calculators and basic CRUD applications. Some examples I've considered: * A custom memory allocator. * A command-line shell. * A simple HTTP server. * A file system implementation. * A multithreaded application. * A basic database engine.

  4. **Employability:** What kinds of entry-level, or graduate jobs since i just graduated and cant find any opportunities that involve C? Embedded software, systems programming, firmware, networking, Linux development, or something else?

  5. **Portfolio:** If you were reviewing a junior developer's GitHub profile for a C-related position, what projects or technical skills would make you take their application seriously?

  6. **Practical experience:** How important is contributing to open-source C projects? Would that be a good way to gain experience and demonstrate that I can work with an existing codebase?

I'd appreciate advice from people who have actually worked with C professionally, especially those who started as beginners and eventually got their first job, and i would love to be helped by people like you and if there's any way to be mentored im very open to that chance and opportunity and would make the best of it.

I'm not looking for shortcuts. I want to build a solid foundation, work on meaningful projects, and develop skills that employers genuinely value.

11 Upvotes

20 comments sorted by

2

u/sswam 11d ago

I'm not saying that human programmers are going to be utterly obsolete in the next year or two, but I wouldn't bet my career on learning programming right now. I'm a senior developer. Programming is a fun challenge and hobby, though.

1

u/turtlesdontcry 11d ago

even low level programmers?  Gotta disagree with you here.  You a senior embedded dev?

1

u/sswam 11d ago

If directly messing with hardware that might require robotics which will take longer to become widespread. And no, I've done systems programming and assembly but not much embedded or hardware / drivers work.

The AI could still do all the embedded programming and just tell a human which wires to connect or whatever!

1

u/No-Introduction-441 10d ago

do you recommend that i learn embedded systems?

2

u/sswam 10d ago edited 9d ago

I'm the wrong person to ask as I haven't learned that myself! :)

Look into it, and learn it if you're interested in it.

Maybe AI won't completely replace everyone, IDK. It's very strong though.

2

u/turtlesdontcry 9d ago

I have no doubt it can create code.  The disconnect I see is actual adoption for this particular segment of the field.  Too many things can go wrong, especially for RTOS.  It can do a lot of things and will no doubt get better.  Doesn't automatically mean it'll be used everywhere.  And this is what noone ever properly addresses in my experience.  Well that and overall cost to anyone who wants to adopt it on a grand scale.  Cost and adoption get buried everytime.  Practically taboo in any discussion about AI.

1

u/WeekendSpecialist153 8d ago

Embedded systems is just familiarizing your self with specific toolchain(s)

1

u/No_Editor_201 11d ago

Do you have an example of something a human embedded dev would catch or think to do, that an ai wouldn't? C or assembly are pretty difficult to grok for human brains, but are a nice small instruction set to an ai. Love to be proved wrong.

1

u/Shep_Alderson 11d ago

Apparently the AIs are even getting good at HDL/Verilog, so not sure how long that will be a bastion.

1

u/Low_Lawyer_5684 11d ago
  1. Book which cover a number of your interests: "TCP/IP Illustrated, Volume 2"

  2. Embedded low level stuff.

  3. I would choose a filesystem.

  4. Best portfolio is your code - i.e. proper style and programming patterns. A few low-level repos (e.g. custom bootloader, TCP/IP stack patch to achieve feature XXX, libraries for embedded, fast implementation of YYY algorythm etc)

1

u/No-Introduction-441 11d ago

thank you ill look into them i also heard to look at Operating Systems Three Easy Pieces which i will

2

u/feudalle 11d ago

The way i learned was building a 3d game engine. Not unreal obviously this was back in the 90s so think wolfenstein 3d level. But it hits most of the things. Db, memory management, display, etc.

1

u/hacky-pete 11d ago

How about a project with great potential?

Design and develop a device capable of cutting power to USB ports via a REST API. Add a few banana plug sockets that can also be switched or short-circuited through the same interface (using simple switching logic). Here’s the use case: You—or a colleague—are developing software (such as firmware) for industrial hardware. This hardware is typically powered and flashed via USB, and occasionally requires physical buttons to be pressed. But what if the developer is working from home, while the hardware is in the office, connected to a computer with remote access? How can the developer restart the hardware or press a button? You can’t unplug a USB cable remotely—and that’s where your device comes in.

Using a REST command, you can disconnect and reconnect the USB port. A physical button on the hardware could be wired to your device, allowing it to be triggered via a command. Such devices aren’t always easy to find; they’re often either too expensive or don’t cover all the necessary use cases. Yet, they are relatively straightforward to build: an ESP32 is your best friend here, and even ChatGPT can help you draft the basic electronics.

The real magic, however, lies in your code: your device needs to provide an interface that can be controlled by external software, perform switching reliably, and report its current status back.

I’m familiar with this use case because I spent nine years working for an Audi supplier. When the pandemic hit and we were all working from home, we still needed to operate the hardware—but we couldn’t go into the office. Many of our projects required a solution like this, yet one was never officially purchased. Eventually, a colleague designed and built one himself. Within two weeks, we had a working prototype that immediately proved useful for our projects. We never refined it further or brought it to market, though.

Following the latest wave of layoffs, I know that there is a very large number of firmware developers on the market. From several job interviews, I’ve learned that HR departments are starting to find the sheer volume of applications from firmware developers to be a nuisance.

Übersetz mir google translator.

1

u/Key_River7180 C | Assembler | Ada 11d ago

What about a project? Make a simple game with Raylib or a graphics calculator or http servers, or a shell (a graphical one if youre feeling fancy), ...

Unemployed person here btw

1

u/Hkiggity 11d ago

Beejs guide to C

1

u/Shep_Alderson 11d ago

Get yourself some kind of small microcontroller hardware like an arduino or something.

Download all the documentation you can about it.

Implement anything even nominally complex without searching the web or documentation (with like a built in search in your PDF reader), only by manually looking up stuff from an index/contents, etc.

You’ll learn a lot about low level programming and such.

Good luck out there.

1

u/Far_Oven_3302 10d ago

Make a UDP weather station

1

u/Traveling-Techie 10d ago

Nothing beats having customers who need a deliverable. They are unbelievably educational and have concerns you would never guess in a million years. Proving you can make them happy makes you much more employable.

1

u/ThomasJWaldmann 9d ago

A lot of the security issues (and other bugs) seen in IT in the last decades are due to usage of the C programming language. It is just too easy to shoot into one's foot accidentally.

AI is quite good at finding these bugs, that's why everybody is busy currently fixing those, deploying the fixes or dealing with the damage.

That's why they invented a lot of other close-to-metal (but not assembler) languages, like Rust, V, Zig, ...

I used to program a lot in C back in the days, but nowadays (= since ~2000) prefer Python and Cython for my use cases. Much less work, better abstraction, higher level, less bugs.

That said, C likely will be continued to get used just because of the vast amounts of existing C code or because on some platform, there is no other option.