173 engineers on Hacker News describe using C first-hand: 20 endorse it, 17 regret it, 4 are mixed.
“75% of our new code right now is C and in my estimation that'll be 100% in about a month”
endorse · production · 59nadir · 2026-10-22 · source ↗ · wrong label?“I participated in IDE development in C long time ago, and I was drowning in this whole low-level stuff all the time, I just could not do a single feature”
regret · production · byko3y · 2025-11-24 · source ↗ · wrong label?“C was just too unsafe for us (C requires you to remember to call functions RAII saves you from that) so we switched”
regret · production · theICEBeardk · 2025-06-23 · source ↗ · wrong label?“But C is a pain in the ass in comparison to Javascript, and I know both languages extremely well.”
mixed · production · leptons · 2024-12-31 · source ↗ · wrong label?“we have been migrating projects from C/C++ to Rust and management has been impressed with the results.”
regret · production · thesuperbigfrog · 2024-12-13 · source ↗ · wrong label?“My C was still terrible (partly because it was C, partly because it was still my first language).”
regret · production · 26 yr · stouset · 2023-12-12 · source ↗ · wrong label?“Using C (Borland or Microsoft) required two floppy disks - one for the compiler, one for the linker.”
mixed · personal · malkia · 2023-08-21 · source ↗ · wrong label?“we replaced all memory allocation, system interface and I/o code with c, leaving the fortran code as basically algebra.”
endorse · production · jleyank · 2023-04-25 · source ↗ · wrong label?“I'm a C# guy who learnt C over the past 2 years. It absolutely made me a better programmer.”
endorse · personal · 2 yr · kovac · 2022-12-23 · source ↗ · wrong label?“Two of the worst C and C++ debugging experiences I had followed this template: Some coworker asked me why their function was crashing”
regret · production · nayuki · 2022-11-28 · source ↗ · wrong label?“I learned C a long time ago... the never ending exploits and security problems are a thing that I just don't need in my own projects.”
regret · personal · jillesvangurp · 2022-07-22 · source ↗ · wrong label?“we have large projects that use lots of technologies, including... even a little bit of C code, which tends to be problematic”
regret · production · brabel · 2022-07-16 · source ↗ · wrong label?“State machines in C work great when you don’t want a preemptive RTOS.”
endorse · production · alfor · 2022-05-20 · source ↗ · wrong label?“At the end we had a maintainable "high-level" language (C, yes, yes HN) exact equivalent.”
endorse · production · fargle · 2022-04-07 · source ↗ · wrong label?“I think C and Lisp together are amazing. I have been using them for decades”
endorse · personal · 20 yr · eggy · 2021-12-23 · source ↗ · wrong label?“its weirdness has been normalized. I didn't realize how absolutely bizarre some of the things in it were”
regret · personal · pyjarrett · 2021-12-18 · source ↗ · wrong label?“We used C for a while and we spent the whole time teaching C, never really getting to cool robot activities.”
regret · production · ModernMech · 2021-12-17 · source ↗ · wrong label?“when 4 days of C code became untenable.”
regret · production · somesortofsystm · 2020-11-26 · source ↗ · wrong label?“To me seemed like C was such a tight, perfect little design.”
endorse · personal · gerbilly · 2019-06-12 · source ↗ · wrong label?“I love and hate C, been using it almost 40 years. Its use seems more and more like juggling razor blades”
mixed · production · 40 yr · heyjudy · 2018-12-29 · source ↗ · wrong label?“So yeah, Safe C is an oxymoron, unless we are talking about a new variant with safety turned on by default”
regret · production · 26 yr · pjmlp · 2018-11-09 · source ↗ · wrong label?“I hope to never again have to write a non-trivial C program and make it thread-safe.”
regret · production · 1bent · 2018-10-10 · source ↗ · wrong label?“One of our core services is written in C, it never crashes, it sustains QPS no other service can”
endorse · production · acroback · 2018-07-11 · source ↗ · wrong label?“Every piece of code I write in C, when I write it in C, is run through a debugger before it is put in production”
endorse · production · Annatar · 2016-12-29 · source ↗ · wrong label?“I love C, I really don't see what the fuss is about about 'replacing' it really.”
endorse · production · buserror · 2016-12-27 · source ↗ · wrong label?“I've known C for 21 years now. I just quit a job as a C programmer for embedded systems. If I can help it, never again.”
regret · production · 21 yr · atilaneves · 2016-10-05 · source ↗ · wrong label?“before we switched over to C at school, which seemed like a big step backward”
regret · personal · Roboprog · 2016-06-19 · source ↗ · wrong label?“We're paying a hefty price for C in the form of buffer overflows, memory leaks, slow development, and other problems”
regret · production · beering · 2015-11-11 · source ↗ · wrong label?“I don't regret learning 'C'. We had our own safety standards.”
endorse · personal · ArkyBeagle · 2014-09-02 · source ↗ · wrong label?“C safety is a oxymoron, which is only enforcable with externals tools. I also don't regret learning C.”
mixed · personal · pjmlp · 2014-09-02 · source ↗ · wrong label?“10 years and 5 positions later, all of my work has been in C, and I regret nothing.”
endorse · production · 10 yr · mrmekon · 2013-12-08 · source ↗ · wrong label?“We use C quite heavily at Bump in our mobile apps. With our recent app Flock, we wrote nearly all non UI logic in C”
endorse · production · ikhare · 2012-12-26 · source ↗ · wrong label?“I'd rather have written only the innermost mechanics of them in C and lashed them together in something that was nice to work with”
endorse · production · willvarfar · 2012-10-16 · source ↗ · wrong label?“I don't regret it, as much as I don't regret my move from C++ to C over the past years.”
endorse · personal · b3tta · 2012-10-05 · source ↗ · wrong label?“write the control program in c using a cross compiler on unix (plus no segments=bliss)”
endorse · production · eckyptang · 2012-09-30 · source ↗ · wrong label?“We switched because we wanted to reduce the risks of bugs, but you must remember that in most mission critical applications”
regret · production · pron · 2012-05-08 · source ↗ · wrong label?“But reimplementing it in C or C++ paid of tremendously on each occasion.”
endorse · production · microtonal · 2011-11-16 · source ↗ · wrong label?“Programming only started to make sense when we switched to C, I did some simple tasks first, then paired off with a classmate”
endorse · personal · cousin_it · 2011-08-04 · source ↗ · wrong label?“then rewrote it in C. My main code wasn't even touched since I had already abstracted the calculations”
endorse · production · cullenking · 2011-06-15 · source ↗ · wrong label?“Can't transform it instantly, much as I would like to. (I did explicitly state that most of this is being moved to Haskell).”
regret · production · plinkplonk · 2010-11-16 · source ↗ · wrong label?“I love it as a language, and I think that is partially due to the amount we use it in our classes.”
endorse · personal · icco · 2010-10-25 · source ↗ · wrong label?“replete with our first C app on MVS”
neutral · production · jbgreer · 2026-09-09 · source ↗ · wrong label?“We intermix html, regex, js, C, and even some Haskell to get stuff done.”
neutral · personal · smj-edison · 2025-12-27 · source ↗ · wrong label?“The C and C++ code builds independently of the Python code”
neutral · production · amluto · 2025-12-18 · source ↗ · wrong label?“I now write either and basically exclusively write Rust these days and a bit of C/C++ at work.”
neutral · production · landr0id · 2025-11-24 · source ↗ · wrong label?“I got started shipping C code in the 1990s, and I'd leave asserts in prod serverside code given the choice”
neutral · production · tptacek · 2025-11-19 · source ↗ · wrong label?“doing unix systems work (C, shell, Perl and some DBs and FTPs)”
neutral · production · ojosilva · 2025-11-19 · source ↗ · wrong label?“we learned to program with giant C reference books.”
neutral · personal · bruce511 · 2025-07-16 · source ↗ · wrong label?“When I started programming in C, I used a debugger all the time.”
neutral · personal · alisonatwork · 2025-06-18 · source ↗ · wrong label?“A for-loop with an fopen that didn't have a corresponding fclose at the end of the loop.”
neutral · production · AdmiralAsshat · 2025-06-06 · source ↗ · wrong label?“when it's time to emit C, but gotos are more straightforward now.”
neutral · production · ufo · 2025-05-16 · source ↗ · wrong label?“We migrated from Asm to C. And C to C++, then to Java. And then Java to Python.”
neutral · production · polski-g · 2025-04-29 · source ↗ · wrong label?“with 40 or so LUA functions integrated into the C codebase and basic access to rooms/objects/players”
neutral · production · Lasher · 2025-03-24 · source ↗ · wrong label?“as a guy who did quite a lot of C earlier, including in prod, I was interested in the goals of zig”
neutral · production · fuzztester · 2025-01-17 · source ↗ · wrong label?“I did have a lot of experience using C for many years in production, though, including on a successful commercial product.”
neutral · production · fuzztester · 2024-12-24 · source ↗ · wrong label?“I wrote 100s of programs in pascal (for DOS and later Delphi) and C/C++ in the 80-90s myself”
neutral · production · anonzzzies · 2024-12-09 · source ↗ · wrong label?“I know very well what C can and cannot do, I've been using it for 40 years.”
neutral · personal · 40 yr · shric · 2024-12-09 · source ↗ · wrong label?“I've been writing C family languages for like 15 years and never once accidentally done a if (foo); whatever;”
neutral · production · 15 yr · BigJono · 2024-08-30 · source ↗ · wrong label?“I use C at my day job and our company works with ANSI C.”
neutral · production · muragekibicho · 2024-01-18 · source ↗ · wrong label?“the systems I work on are million+ lines C/C++ monoliths”
neutral · production · deterministic · 2023-12-30 · source ↗ · wrong label?“I went from Basic to Pascal to C/C++ to Java to Python which bear more than a passing resemblance to one another.”
neutral · personal · dventimi · 2023-12-27 · source ↗ · wrong label?“I say this as someone with 20+ years of experience in C and C++”
neutral · production · 20 yr · gosub100 · 2023-12-26 · source ↗ · wrong label?“We generate VHDL and C. It's incredibly powerful.”
neutral · production · nsteel · 2023-12-13 · source ↗ · wrong label?“from then on, everything we wrote was mostly in C, until C++ etc. became a thing.”
neutral · production · Tor3 · 2023-12-12 · source ↗ · wrong label?“My career before Rust was very C heavy.”
neutral · production · stusmall · 2023-11-23 · source ↗ · wrong label?“My first language was C++ and then we switched to C.”
neutral · personal · Gnarly9Regard · 2023-11-18 · source ↗ · wrong label?“we switched from C to Java completely for that service.”
neutral · production · warpspin · 2023-11-12 · source ↗ · wrong label?“We moved to python then arduino/microbit/etc and then to c and now to riscv assembler”
neutral · personal · throwaway71271 · 2023-10-03 · source ↗ · wrong label?“we did web development in c and then later c++”
neutral · production · monkeycantype · 2023-04-25 · source ↗ · wrong label?“spent half my career bit twiddling in C and C++ with a little inline assembly.”
neutral · production · scarface74 · 2022-12-28 · source ↗ · wrong label?“This is our first experience generating docs for a single project that spans C, C++, Python, Java, and GoLang”
neutral · production · ashvardanian · 2022-12-27 · source ↗ · wrong label?“I'd been using C for a couple years in 1989”
neutral · personal · 2 yr · abecedarius · 2022-12-19 · source ↗ · wrong label?“C, C++ have all existed since forever and which I touched up at college.”
neutral · personal · doublerabbit · 2022-12-14 · source ↗ · wrong label?“I was very interested in it as I do both python and C, but it somehow was just not that popular”
neutral · production · synergy20 · 2022-12-09 · source ↗ · wrong label?“my project language compiles to C, which is loaded at runtime with libtcc”
neutral · personal · raible · 2022-12-01 · source ↗ · wrong label?“We've got a few components written in C that I'm (partially) responsible for.”
neutral · production · fps_doug · 2022-11-28 · source ↗ · wrong label?“When I do write code in C, I can't guarantee that the disassembled code resembles my actual code”
neutral · personal · phoehne · 2022-11-21 · source ↗ · wrong label?“then we made a raytracer in plain C (easy to explain and write, huge interest spike as you get magical results)”
neutral · personal · orbital-decay · 2022-11-18 · source ↗ · wrong label?“15 years ago we built stuff in C and used cheap commercial available tools that detects EXACTLY this issue.”
neutral · production · AtNightWeCode · 2022-11-04 · source ↗ · wrong label?“Finally, we moved to C, followed by Compiler construction, Operating systems etc.”
neutral · personal · vivegi · 2022-09-13 · source ↗ · wrong label?“Thankfully we switched to C on SunOS or Ultrix for the upper level classes.”
neutral · personal · drewg123 · 2022-08-01 · source ↗ · wrong label?“When we moved to C, we could stop worrying about what registers we were using. When we moved to python/Java we could stop worrying about managing memory.”
neutral · production · natefinch · 2022-07-01 · source ↗ · wrong label?“Nope. Asm, then later Pascal quickly followed by C.”
neutral · personal · cagey · 2022-06-04 · source ↗ · wrong label?“I gave up on autotools and wrote a small c program that compiles the project along with a configure script”
neutral · personal · GartzenDeHaes · 2022-05-02 · source ↗ · wrong label?“Changing the way we streamed a response based on an HTTP header from the application. (We ended up writing a C module for this.)”
neutral · production · cakoose · 2022-02-20 · source ↗ · wrong label?“Later we replaced FORTH with a custom HyperTIES Markup Language interpreter that was written in C”
neutral · production · DonHopkins · 2021-12-29 · source ↗ · wrong label?“in writing (and more importantly in teaching!) C and C-style languages”
neutral · personal · addaon · 2021-12-27 · source ↗ · wrong label?“We use C/C++ for the traffic capture and processing”
neutral · production · gjulianm · 2021-12-23 · source ↗ · wrong label?“At my shop we use C, C++ and Ada.”
neutral · production · zppln · 2021-12-15 · source ↗ · wrong label?“I have written C, Fortran, JavaScript, Python, and Scala for money.”
neutral · production · philipkglass · 2021-12-10 · source ↗ · wrong label?“I'm a prolific user of Duff's device for poor man's coroutines in C, but in non-toy applications I do try to isolate the behavior”
neutral · production · wahern · 2021-11-19 · source ↗ · wrong label?“I used to work in a C/C++ embedded shop”
neutral · production · Skinney · 2021-09-20 · source ↗ · wrong label?“I've started moving to using python to generate what I need a lot of the time now in C.”
neutral · personal · anitil · 2021-04-09 · source ↗ · wrong label?“They even worked for a while in Assembly Language until quite recently (we now use C exclusively).”
neutral · personal · ajarmst · 2021-03-20 · source ↗ · wrong label?“I wrote the software -it's Python3 and C.”
neutral · personal · another_comment · 2020-12-21 · source ↗ · wrong label?“the only language of the 13+ I've used in production code”
neutral · production · wolfadex · 2020-12-10 · source ↗ · wrong label?“I usually use Windows with C (through the raw win32 API - which isn't everybody's cup of tea and can be somewhat confusing)”
neutral · personal · phendrenad2 · 2020-12-09 · source ↗ · wrong label?“writing vtables manually in C because I didn't trust what I couldn't see in c++”
neutral · personal · dnautics · 2020-09-28 · source ↗ · wrong label?“I've personally used C with CGI-BIN, Perl, ASP.net, PHP (back when it was Personal Home Page)”
neutral · personal · alasdair_ · 2020-05-16 · source ↗ · wrong label?“I use c style casts everywhere and I've stopped using every other style.”
neutral · personal · drenvuk · 2020-04-24 · source ↗ · wrong label?“we needed to write at low levels for performance, or to access hardware directly, or call Fortran code... we switched to C.”
neutral · production · pjdemers · 2020-03-26 · source ↗ · wrong label?“I've been writing C since the late 1970s, and I still discover things about the language.”
neutral · personal · 40 yr · kabdib · 2019-12-29 · source ↗ · wrong label?“using C libraries in a new C project ... For me that is not at all easier”
neutral · personal · jacquesm · 2019-12-27 · source ↗ · wrong label?“I've just started adding a new feature on a C project started in 2009.”
neutral · production · simias · 2019-12-19 · source ↗ · wrong label?“I implemented firmware for very specialized AC motor speed and torque control that also does whole bunch of other things on a very low end microcontroller. Was implemented in C.”
neutral · production · 6 yr · FpUser · 2019-12-18 · source ↗ · wrong label?“For the last few years I've been using C less though, as I prefer Rust anyway.”
neutral · personal · codetrotter · 2019-12-17 · source ↗ · wrong label?“R is unlike any other programming language that I have used before (also on an off) from Perl, C to Python and Java”
neutral · personal · glofish · 2019-12-15 · source ↗ · wrong label?“Unfortunately too many years of C/C++ have made it hard for me to grok FP code”
neutral · production · nineteen999 · 2019-08-16 · source ↗ · wrong label?“I've been using C for decades and I couldn't reliably answer without looking it up.”
neutral · personal · 20 yr · _kst_ · 2018-12-30 · source ↗ · wrong label?“I see foo and Foo as completely different; I've been programming in C and using Unix file systems for thirty years.”
neutral · personal · 30 yr · kazinator · 2018-12-26 · source ↗ · wrong label?“I was more unproductive with Haskell than I've ever been with C, which is usually the language I love to bash on.”
neutral · personal · atilaneves · 2018-12-19 · source ↗ · wrong label?“To someone who has been using Asm and C for decades”
neutral · production · 20 yr · userbinator · 2018-12-04 · source ↗ · wrong label?“went back to the C implementation”
neutral · production · olooney · 2018-11-28 · source ↗ · wrong label?“but our control plane is Go / C.”
neutral · production · sargun · 2018-11-20 · source ↗ · wrong label?“After that we moved to C and eventually "C with classes" C++.”
neutral · personal · reubenmorais · 2018-10-04 · source ↗ · wrong label?“we actually take advantage of this same VLA idiom for temporary storage for polymorphic variables”
neutral · production · BruceIV · 2018-03-24 · source ↗ · wrong label?“while I would regularly use a debugger for C code”
neutral · personal · burntsushi · 2017-12-21 · source ↗ · wrong label?“When we finally get to C, pointers seem natural.”
neutral · personal · alew1 · 2017-11-29 · source ↗ · wrong label?“I had my own version of C's FILE* that ended up being a horrible abstraction... I got fed up with it, and ripped that out, replacing it with native IO calls.”
neutral · personal · spc476 · 2017-11-27 · source ↗ · wrong label?“In fact, I do - daily. I'm not stating that this exact issue is the key reason”
neutral · production · kbart · 2017-11-14 · source ↗ · wrong label?“About 2/3's through the course we switched to full-blown C, at which point we had to learn pointers.”
neutral · personal · murph-almighty · 2017-10-18 · source ↗ · wrong label?“I was tired of having different standards for C and C#”
neutral · production · shoover · 2017-10-13 · source ↗ · wrong label?“I write Python and C everyday. I am highly proficient in both.”
neutral · production · grive · 2017-08-16 · source ↗ · wrong label?“I'm a programmer that has been using C for at least 8 years”
neutral · production · 8 yr · cyphar · 2016-12-21 · source ↗ · wrong label?“The speed critical parts were written in C and loaded as TCL extensions.”
neutral · production · pjmlp · 2016-12-16 · source ↗ · wrong label?“writing both straight assembler (68k processors) and C back in the 90s”
neutral · personal · algesten · 2016-10-22 · source ↗ · wrong label?“I have come across quite bad C codebases, poor Perl applications and terrible Java code”
neutral · production · marklgr · 2016-10-14 · source ↗ · wrong label?“I play with Darknet now, since C was my second language after Assembly (6502 and then x86_32)”
neutral · personal · eggy · 2016-10-01 · source ↗ · wrong label?“Around 12 it was C and games by using Allegro”
neutral · personal · sharpneli · 2016-05-05 · source ↗ · wrong label?“4 in C when I code for fun or the lead says 4.”
neutral · personal · julie1 · 2016-03-31 · source ↗ · wrong label?“I write SCSI driver code in C”
neutral · production · nathanb · 2015-07-13 · source ↗ · wrong label?“I write mostly write C, Bash, Python, Go, Puppet.”
neutral · production · sleepydog · 2015-07-05 · source ↗ · wrong label?“Back when we were thinking about breaking up our C and C++ programs into processes using RPC as glue”
neutral · production · markbnj · 2015-07-01 · source ↗ · wrong label?“I'm mostly C/C++/Java/Clojure/Matlab”
neutral · production · pron · 2015-06-21 · source ↗ · wrong label?“also have a fair amount of experience programming Microchip's MCU's in C”
neutral · personal · analog31 · 2015-06-20 · source ↗ · wrong label?“I'm torn about these choices, I've tried and liked them, but am a bit out of my element as primarily a python/c developer.”
neutral · production · mixmastamyk · 2015-06-14 · source ↗ · wrong label?“my production skill set includes php, c, c++, python, ruby, erlang, scheme, javascript, scala”
neutral · production · Ixiaus · 2014-12-27 · source ↗ · wrong label?“Coming from C I'd say that std::list is the 'strange kind' of lists”
neutral · personal · flohofwoe · 2014-12-25 · source ↗ · wrong label?“We use C, C++, C# among other languages.”
neutral · production · HeyLaughingBoy · 2014-12-12 · source ↗ · wrong label?“I've been coding for over 30 years now (Basic, ASM, C/C++, Java, Python, PHP, JS, Clojure)”
neutral · personal · rivo · 2014-12-11 · source ↗ · wrong label?“The result was 89 times slower than our c code, which is not so slow compared with other options”
neutral · production · Htsthbjig · 2014-11-19 · source ↗ · wrong label?“I've been using C since ~ 1980 (sic), loathe C++, and, yeah, I'm going to investigate Rust in due course.”
neutral · production · 34 yr · hga · 2014-11-16 · source ↗ · wrong label?“I taught myself C, C++, BSD sockets, Java, and OOP all for it”
neutral · personal · nostrademons · 2014-06-23 · source ↗ · wrong label?“Also I use it as a platform to easily develop C/C++ web services where performance is paramount, on real big servers.”
neutral · production · dmoreno · 2013-12-20 · source ↗ · wrong label?“I still use Eclipse for C and C++ development”
neutral · personal · vonmoltke · 2013-12-11 · source ↗ · wrong label?“I've been learning C (through 'Learn C The Hard Way') to be able to contribute to various projects”
neutral · personal · girvo · 2013-12-08 · source ↗ · wrong label?“What our company has ended up doing is wrappering most low level functions with the common code around it.”
neutral · production · alexkus · 2013-12-06 · source ↗ · wrong label?“Coming to Scala from experience including C, Java and Haskell”
neutral · personal · NickPollard · 2013-12-02 · source ↗ · wrong label?“it wasn't until 1996 or so that I really got into the swing of "serious" programming in C and C++.”
neutral · personal · 17 yr · breckinloggins · 2013-10-01 · source ↗ · wrong label?“I also wrote a few patches for OpenTTD and learnt some C doing that.”
neutral · personal · lucaspiller · 2013-09-30 · source ↗ · wrong label?“I designed a DSL and wrote a C tool to generate the COBOL programs from templates and DSL files.”
neutral · production · Jare · 2013-05-27 · source ↗ · wrong label?“some use Qt, some use GTK, written in python and some in C or C++”
neutral · production · noselasd · 2013-03-04 · source ↗ · wrong label?“We run web services and the like all in combinations of C, RPG, JAVA, embedded SQL, and such.”
neutral · production · Shivetya · 2013-01-15 · source ↗ · wrong label?“wrote a Common Lisp system from ground up with C”
neutral · personal · ww520 · 2012-12-28 · source ↗ · wrong label?“I'm a developer writing in C/C++/Java/Python, who has more than touched Objective C/Ruby/PHP/Perl/bash scripting/C#”
neutral · production · koffiezet · 2012-12-25 · source ↗ · wrong label?“Although our production code is written in C, I'm not particularly worried about detecting wild writes”
neutral · production · erichocean · 2012-11-27 · source ↗ · wrong label?“I have found assertions very valuable in both Python and C.”
neutral · production · fdr · 2012-09-25 · source ↗ · wrong label?“our core algorithms are in C and we run a pretty serious production Node.js app.”
neutral · production · DavidChouinard · 2012-02-10 · source ↗ · wrong label?“At work, we use C90 with a few C99 extensions which can be disabled through the preprocessor”
neutral · production · TheNewAndy · 2011-12-25 · source ↗ · wrong label?“I was already programming in C and Perl at this time.”
neutral · personal · peterwwillis · 2011-12-05 · source ↗ · wrong label?“Every suffiently large Erlang applications include parts written in C. In our case we do JSON parsing in C, we use ZeroMQ, etc.”
neutral · production · nivertech · 2011-11-12 · source ↗ · wrong label?“I can apply the method of spike solution and then refactor it into working code like I do with languages like Python or C.”
neutral · personal · swah · 2011-10-21 · source ↗ · wrong label?“I write all my C and C++ code at warning level 4 (the maximum, which is probably equivalent to -Wall).”
neutral · production · palish · 2011-08-07 · source ↗ · wrong label?“the SpiderOak directory watchers are tiny C programs for each platform, and are open source.”
neutral · production · rarrrrrr · 2011-02-03 · source ↗ · wrong label?“write all our math code in C (Newton's methods, ODE integrators, linear system solvers)”
neutral · personal · RBerenguel · 2010-12-27 · source ↗ · wrong label?“When I moved to C, suddenly the patterns of if/then and do/while/for loops immediately made sense”
neutral · personal · Natsu · 2010-10-20 · source ↗ · wrong label?“we flip from C to L to tcl to shell”
neutral · production · luckydude · 2010-10-08 · source ↗ · wrong label?“Having learned C, Java, SQL, Common Lisp, and Scheme on my own”
neutral · personal · masterponomo · 2010-08-02 · source ↗ · wrong label?“But my current startup is about 50% web app and 50% Linux app. So we're finding more and more need for C.”
neutral · production · jon_dahl · 2010-07-29 · source ↗ · wrong label?“I've had more eye opening experiences programming in Clojure than in any language I learned before it. (C, C++, Java, Python, Ruby, common lisp)”
neutral · personal · rosejn · 2010-07-15 · source ↗ · wrong label?“we used to say prototype in C++ and then re-implement in C to make it fast in production.”
neutral · production · dedward · 2010-06-21 · source ↗ · wrong label?“In my "normal" job, I get a very small white list of programming languages.”
neutral · production · stevenN · 2010-04-10 · source ↗ · wrong label?