2,012 karma · joined February 24, 2011
Maybe you are here to make a professional connection. If so, that's excellent. You may reach me personally at:
vb.temp@gmail.com
C, Rust, aerospace, embedded systems, distributed systems. You hopefully get the shtick.The only thing I'm confused about is why more C standards keep coming out. C is what it is. Work with the archaic parts of it as need be. You use C for ultimate cross-platform compatibility (every exotic platform and its mother has an ANSI-C/C99 compiler). If you're able to run on the most bleeding-edge C compiler supporting the most recent WG version of C... then why not just use another language? I say this as someone who loves C. If there are bits that feel old, you just create a DSL to get around these problems that compiles down to C... but you don't change C itself.. Just my perception working with all this for many years now.
Yep
Location: DMV (DC, Maryland, Virginia)
Remote: Hybrid preferred, but flexible for any arrangement.
Willing to relocate: Probably not.
Technologies: C, Rust, Python in Linux environment. Mostly do distributed systems, network protocol design and analysis, and related work. Worked in Aerospace flight software, embedded systems, space mission operations, etc. "Research Engineer" fits my ideal scope-of-work best. Other non-technical/management/leadership activities not mentioned here. I seek to avoid working in product-oriented "Agile" teams.
Résumé/CV: On request
Email: vb.temp@gmail.com
Other: MS and BS in Computer Science. Security clearance (detail on request)But he's just another guy that has to turn tricks with some new variant of "durr hurr liberal plan for X is elitist and a luxury belief."
It's a little personal with him, because right before the 2020 election he posted something pretentious like "In 2016 I bet and won a lot of money on the outcome of the election, and I bet even more this time" (Implying his non-elitist background gave him the clairvoyance that Trump would win. I asked him who he bet on this time. Then the results came in and Trump was clearly losing in 2020, and then he blocked me.
In the end, even if we agree with him, he's just another culture warrior that whose livelihood depends on feeding the angry masses outrage at whatever Team Blue/Team Red is doing.
I guess if I could rephrase my original question: People who are going to adopt C23 - who are you and what field/industry/line-of-work are you in?
Asking because in my line-of-work, C is ubiquitous and I personally love coding in C, but anything beyond ANSI C (or C99) is "cool" but undermines the point of C as I've used it, which is its use cross-platform for a huge set of common and uncommon architectures and instruction sets. If something only needs to run on common, conventional platforms, C, however much I love it, would no longer necessarily be a strong contender in light of many alternatives. It seems like these standards target an ever shrinking audience (much smaller than the whole universe of software developers working in C).
Who exactly are these new C-standards for?
I interact and use C on an almost daily basis. But almost always ANSI C (and sometimes C99). This is because every platform, architecture, etc has at least an ANSI C compiler in common so it serves as the least common-denominator to make platform-independent code. As such it also serves as a good target for DSLs as a sort of portable-assembly. But when you don't need that, what's the motivation to use C then? If your team is up-to-date enough to quickly adopt C23, then why not just use Rust or (heaven forbid, C++23)?
I'd love to hear from someone who does actively use "modern" C. I would love to be a "modern C" developer - I just don't and can't see its purpose.
Do you remember the Paul Graham essay on the Blub programming language? (http://www.paulgraham.com/avg.html)
C++ is kind of like the Blub language. If you know C++ well enough, you can do anything you need to do, so something like Rust just seems too esoteric and weird and pretentious.
Fortunately, I spent many years using Rust recently (coming from primarily a C background) and when I'm on a project using C++, it just feels too weird and rudimentary and horribly over-complicated.
To end with a quote from the PG article:
_But when our hypothetical Blub programmer looks in the other direction, up the power continuum, he doesn't realize he's looking up. What he sees are merely weird languages. He probably considers them about equivalent in power to Blub, but with all this other hairy stuff thrown in as well. Blub is good enough for him, because he thinks in Blub._
I think was this was meant to mean was: Any citizen has the right to join their local/state militia, and keep their service rifle and uniform with them at home.
However, no one should confuse this with actually being some kind of analysis. This piece is entertainment to be enjoyed by white folks in Alexandria cozy on their couch with their cafe-au-lait.
Source: Decades-long resident of DC who walks and bikes those routes every month.
At a prior company, in order to be promoted from associate to senior staff, you had to demonstrate and be evaluated performing at senior level while associate for a year. In order to get hired as a senior, you just talked with a hiring manager and an HR rep, checked off some boxes based on a few blurbs about what you did at prior jobs, and boom, you were a senior. Same thing with getting a raise. To get a raise to 150K (just as a randomly selected round number), it was an enormous bureaucratic process going up 5 levels of management that would take months with lots of aggravation - and unlikely to really pan out. To get hired at 150K for the same role, it was a couple phone calls with an HR rep and hiring manager - about 15 minutes in total.
Now, I only work in teams and projects that are pointedly non-Agile, non-SCRUM, without anyone holding a title of "SCRUM Master". My love of software development is coming back, and it really feels great.
Every time I interview for a job, the only time I permit myself one foul-language word, is when I make the point that "I'm not going to work in an Agile team, I'm too old for that shit". When what follows is an awkward, silent few moments, I know it isn't going to work out. When what follows is enthusiasm and agreement (happening more and more these days) I know we're on the right track to do great work together.