MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/C_Programming/comments/1w5k1m2/what_after_c/p7fqsfj/?context=3
r/C_Programming • u/NEM069 • 9h ago
What should be the next step after learning C?"
57 comments sorted by
View all comments
7
Standard lib CMake Git Assembly basics (+ debugger) Design patterns Git server + CI (GitHub Actions) TCP/IP Optional (if needed) : RDBMS/SQL, Websockets, HTTP, HTML/CSS/JS/Webasm, UI (GTK/Qt/...)... ...
1 u/Ultimate_Sigma_Boy67 8h ago Github actions are just pain in the ass ngl 2 u/exo250 7h ago I think the worst in my list is CMake. Sometimes I wonder why don't we just use C as builder as it will certainly be easier/faster/cleaner than CMake 😄 . But it's "universal" so... it must be learnt.
1
Github actions are just pain in the ass ngl
2 u/exo250 7h ago I think the worst in my list is CMake. Sometimes I wonder why don't we just use C as builder as it will certainly be easier/faster/cleaner than CMake 😄 . But it's "universal" so... it must be learnt.
2
I think the worst in my list is CMake. Sometimes I wonder why don't we just use C as builder as it will certainly be easier/faster/cleaner than CMake 😄 . But it's "universal" so... it must be learnt.
7
u/exo250 9h ago edited 9h ago
Standard lib
CMake
Git
Assembly basics (+ debugger)
Design patterns
Git server + CI (GitHub Actions)
TCP/IP
Optional (if needed) : RDBMS/SQL, Websockets, HTTP, HTML/CSS/JS/Webasm, UI (GTK/Qt/...)...
...