Resume in C

https://gist.github.com/klange/4042963

by brudgers • 11 years ago

291 112 11 years ago

gist.github.com

newobj• 11 years ago

    --- a/resume.c
    +++ b/resume.c
    @@ -118,7 +118,7 @@ void print_job(job_t * job) {
            }
     }
    
    -int main(int argc, char * argv) {
    +int main(int argc, char ** argv) {
    
            int i = 0;
            while (jobs[i]) {
    @@ -127,4 +127,4 @@ int main(int argc, char * argv) {
            }
    
            return 0;
    -}
    \ No newline at end of file
    +}

lukeasrodgers• 11 years ago

For those who don't write C, could you explain what is significant about this change? I'm guessing the earlier version was some kind of subtle bug?

tcas3• 11 years ago

  char * argv

is a pointer to a string (or a single character).

  char ** argv

is a pointer to an array of pointers to strings. The latter is used since it allows for multiple arguments in (the number being `int argc`).

This picture shows the second example in terms of pointers:

http://www.londonquilters.org.uk/ctext/pic511.gif

shultays2• 11 years ago

You input arguments into your program using argc and argv. argc is number of arguments and argv is the list of arguments.

There is no string in c so you use char pointers instead. But in previous code he used char, which is usually defines a single string, but main actually inputs an array of string so it should have been char* (pointer to pointer of char, or pointer to 'string')

Basically he did something like this in Java

public static void main(String args)

instead of

public static void main(String args[])

sago• 11 years ago

How about storing the structures in linked lists, and printing them recursively?

therealdrag0• 11 years ago

When I was in university, I did something similar in Python. I printed it off in color and brought it to a career fair. One guy loved it excitedly. But I didn't hear back from him :(. And that's the story of how I cam to work in Java ;)

afarrell• 11 years ago

This is why when you meet someone at a networking event:

0) Have brought a pen or cell phone.

1) Always get their business card or contact info.

2) When you get someone's business card, always write down where you met them and what you want to ask or show them. Otherwise, you end up with a pile of cards and no memory of who they were from.

2.1) If you actually had them type their email into your phone, sketch out the email, but don't send it.

3) follow up within 3 days or you'll forget.

Aldo_MX5• 11 years ago

Wow, I didn't know this was valid C code, it's pretty convenient.

  school_t uiuc = {
      .school   = "University of Illinois at Urbana-Champaign",
      .location = "Urbana, IL",
      .program  = "BS Computer Science",
      .started  = 1251158400,
      .left     = 1336608000,
      .accomplishments = {
          "Minor in International Studies in Engineering, Japan",
          "Focused on systems software courses",
          NULL
      }
  };

lcampbell• 11 years ago

It's a C99 feature (I think?) -- designated literals. They're absolutely wonderful.

amaterasu• 11 years ago

It's supported by GCC as an extension to C90 too.

masklinn7• 11 years ago

Although GP didn't remark on it, TFA uses an other cool feature which is actually C11: anonymous unions. Although not as wonderful as designated literals, they're really quite convenient.

blt• 11 years ago

I so, so wish C++ would adopt this feature.

stephencanon• 11 years ago

Designated initializers are one of a few indispensable features that make "C++ is a better C" a complete non-starter for me.

zem• 11 years ago

i learnt about them from this post and the library it refers to: http://spin.atomicobject.com/2014/10/08/c99-api-designated-i...

good read, both the post and the socket99 code.

amitlan• 11 years ago

My gcc required me to put { } around any fields of unnamed unions.

[gcc version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC)]

GFK_of_xmaspast• 11 years ago

gcc 4.4 is getting kind of long in the tooth.

cipher0• 11 years ago

These are called desginated initializers, they're part of C99.[0] This is a good read which discusses them and also devles into compound literals.[1]

[0] https://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html [1] https://nickdesaulniers.github.io/blog/2013/07/25/designated...

wschroed• 11 years ago

I highly recommend "21st Century C" (http://shop.oreilly.com/product/0636920025108.do) as a tour of modern C programming, including use of C99 features. It goes over C tooling (profiling, debugging, testing, cross-platform deployment), and explores C99.

pwaring2• 11 years ago

There's a newer edition available which has been published recently:

http://shop.oreilly.com/product/0636920033677.do

Aldo_MX5• 11 years ago

Following your recommendation, to people interested in learning about Modern C++, Stroustrup's Tour of C++ is a recommended read.

http://www.stroustrup.com/Tour.html

pwaring2• 11 years ago

They're used heavily in Linux device drivers, amongst other things - here's just one example:

https://github.com/torvalds/linux/blob/master/drivers/video/...

dangayle• 11 years ago

It's cheeky, but then again it is a project you can show someone. Graphic designers get to make fancy schmancy resumes to impress their potential employers, so why not programmer? Better make sure there are no bugs in it though.

BinaryIdiot• 11 years ago

Ah nothing like handing your resume over to a prospective employer and having it SEGFAULT

MatthewWilkes• 11 years ago

If they'll run unknown code without checking it first that's something you'd want to know about.

sloanesturz• 11 years ago

It's pretty slick -- although I don't know a lot of recruiters who can convert unix timestamps to actual dates in their heads!

asveikau8• 11 years ago

That's why they run the program, it formats them.

Pasting in code from the internet and running it is a little scary though. I wonder of we can spot the backdoor here. :P

pestaa• 11 years ago

It's not even running it only. Recruiters need to compile it first. :)

Aldo_MX5• 11 years ago

You can use ideone.com

http://ideone.com/Tr7oiN

asveikau8• 11 years ago

Code review:

* The struct members and variables pointing at string literals should be const.

* People do break this all the time but typedefs ending in _t are reserved by POSIX.

* Your C99 style struct initializers are valid but it's notable that one popular compiler, MSVC, will not like them.

* If we are being idiomatic I would suggest pointer arithmetic to iterate instead of using a counter i.

adamnemecek• 11 years ago

* If we are being idiomatic I would suggest pointer arithmetic to iterate instead of using a counter i.

How exactly is one more idiomatic than the other?

asveikau8• 11 years ago

It's subjective. It feels more c like and natural to me to write while (foo->bar) and not while (foo[i].bar). The latter feels like the way you would do it somewhere else, grafted onto C. But it's not wrong, I don't have deep qualms with it, and that's why I put it last on my list.

anta40• 11 years ago

* Your C99 style struct initializers are valid but it's notable that one popular compiler, MSVC, will not like them.

The code compiled fine with MSVC 2013 (simply 'cl resume.c'). No warnings at all.

asveikau8• 11 years ago

I think they they implemented it very recently. 2012 will fail.

Aldo_MX5• 11 years ago

People do break this all the time but typedefs ending in _t are reserved by POSIX.

hahaha, shame on me, I always use _t to abbreviate types or make custom ones, ex. uint_t, fraction_t, bitfield32_t, etc...

bitfield32_t: https://gist.github.com/AldoMX/526e84da13b00ac0c75e

pjmlp4• 11 years ago

If we are being idiomatic I would suggest pointer arithmetic to iterate instead of using a counter i.

Well, the CVE guys need to keep their job.

asveikau8• 11 years ago

He's already iterating by using null termination instead of based on array bounds. I am suggesting he do it in the more common way.

On another topic, I have noticed you post this sort of trollish c bashing on almost every hn thread about c. It's fine that you prefer something else, but maybe time to give it a rest?

amelius• 11 years ago

Style review:

* Avoid using NULL in your resume. It has a negative connotation, and makes your resume look bad.

* Make use of as many existing libraries as possible, to show that you're not the kind of programmer that wants to invent the wheel on every occasion.

* Try to obfuscate your resume a little (but not too much!) As it is written here, your reader can easily guess what the program will do, and he/she will not even want to run it anymore.

* #include a portfolio of your work inside your resume.

evincarofautumn• 11 years ago

You had me going for a moment there. I was ready to respond to your comment about NULL before I realised you were joking.

emergentcypher• 11 years ago

I think we have bigger problems to address before we get to these minor contrivances.

This resume is not web scale enough. We need to wrap the resume in node.js so it can be non-blocking for big data. It should be written in an esoteric JS variant and transpiled to ES5 because everyone knows ES5 is unreadable. Oh and the storage of his education and job history should really be stored in a NoSQL database like MongoDB that way he can shard asynchronously. When he presents the resume in his interviews it should be wrapped in a webkit container.

zamalek• 11 years ago

Cute, but it probably wouldn't make it past the HR filter.

eps• 11 years ago

That in itself is a good selector for companies where HR wields more power than the engineering.

teh_klev• 11 years ago

True, but there is a disclaimer:

No, I don't distribute my résumé like this.

forrestthewoods• 11 years ago

Cute. Effort I'm willing to spend parsing a resume: zero. Not sure if this is a net win or not.

alexbecker• 11 years ago

Just curious, but why do you use

  initialize
  while (test) {
    ...
    increment
  }

instead of

  for (initialize; test; increment) {
    ...
  }

vbezhenar• 11 years ago

Something like #define DATE(month, day, year) ... would help to read dates without program running.

z3t4• 11 years ago

This is a hit or miss. Say they are looking for a C coder. A bad recruiter (most of them) would just discard this as he/she wouldn't even recognize it as C code, just some junk not fitting into his/her template. A good recruiter though, or if a recruiter wasn't used - they would see this as smart and creative and definitely get you an interview.

I've seen companies shutting down/relocated because of bad recruiters filtering good programmers like this.

kpmah• 11 years ago

Personally, I wouldn't want to work for a company that uses bad recruiters (and thus probably hires bad programmers), so something like this would be doing its job.

You don't have to go this far. My CV is a HTML page, and I just refuse to convert it to Word. It hinders the recruiters who just like to buzzword search their database.

zaroth• 11 years ago

Yes, but if i is divisible by 3, you need to print... oh, never mind.

nvader• 11 years ago

When I saw the title, I thought it was going to be about pausing and resuming a thread of execution or some stack.

Could an editor put the slanty thing over the e in the title?

wrboyce• 11 years ago

FYI the "slanty thing" is called an acute accent.

dan1234• 11 years ago

Reminds me of Major Hayden's man page résumé[0]

[0]http://majorhayden.com

draegtun• 11 years ago

Nice. Here's one I always remember (written in Haskell) - https://ocharles.org.uk/

OCharles originally did it in Perl/Moose and with a module of mine (Acme::URL) which is how I stumbled across the CV in the first place - https://web.archive.org/web/20120119150530/http://ocharles.o...

klange• 11 years ago

My actual résumé is written in BSD mandoc: http://r.dakko.us/

raverbashing• 11 years ago

thing_t * thing

This makes my head hurt!

I'd prefer thing_t *thing.

But it's a nice concept

masklinn7• 11 years ago

Surely it should be `thing_t* thing`!

malka• 11 years ago

thing_t* thing_ptr, thing

imo, the star should be with the variable name. because, in this case, a reader could think that both thing_ptr and thing are pointer to a thing_t

"thing_t thing_ptr, thing, other_thing_ptr" is imo more readable

perdunov9• 11 years ago

Great idea, but oops... the data structure thing_t is hideous. It is a "god object" for anything where differently purposed members are union'd. Also, putting char*'s into a union is a terrible idea.

masklinn7• 11 years ago

It is a "god object" for anything where differently purposed members are union'd. Also, putting char*'s into a union is a terrible idea.

They're not differently purposed, the union is just used to define more contextual labels for equivalent fields, and thus make initialisation more readable within each domain.

perdunov9• 11 years ago

There are three data structures unsystematically blended into one (that is, one cannot unambiguously tell which fields go into which "virtual" type, and cannot formally check the correctness). The name thing_t is indicative that you indeed cannot really tell what that entity is. This kind of data structure design begs for errors, while being conceptually wrong.

Ma8ee3• 11 years ago

Why is putting char* into a union a bad idea?

perdunov9• 11 years ago

char* points to some mutable buffer of char's that is supposed to be allocated somewhere. In this particular case they are assigned string literals, but in general it would be quite easy for someone to break consistency of allocations/deallocations in such code.

allending• 11 years ago

Would be pretty awesome to make a Swift playground version of a CV that is animated and interactive.

philh• 11 years ago

For bonus points (or not, depending on the recipient's sense of humour) construct a resume that would be suitable for the underhanded C contest (http://www.underhanded-c.org/).

chii2• 11 years ago

that would be an interesting way for malware to enter - you submit a seemingly innocent resume in C, ask the reader to compile it to see it in pretty colours/formatting. And subtlety pwning the machine in the process.

veihan• 11 years ago

This could be good idea, if it would lead to omission those retarded screenings.

bane• 11 years ago

This is great fun, which comes along at a nice time since I'm working through an intro to C class to revive some very stale "real language" skills I've lost years ago. I've studied through some basic dynamic data structures (linked-lists, binary trees, etc.) and was quite surprised at both how much of this I could follow AND how much I learned.

snorkel• 11 years ago

That's pretty great. It's too bad most HR tools would completely screw that nice formatting, but I'd definitely bring printed copies of that into a dev role interview! That'd break the ice right away.

srameshc• 11 years ago

"They're all while loops because shut up, you're overthinking a joke." Just curious what is wrong with all the while loops ?

dtzWill• 11 years ago

Nothing, really.

There's an argument that using a 'for' construct groups together the details of the loop (initialization, the loop condition, iteration update), which can aid readability.

(You don't have to search the loop body to find how things change between iterations)

Of course, nothing forces a for() loop to have iteration behavior entirely dependent on only what's in the 'for'. In my experience this seems to be discouraged, however, preferring to use 'for' only when there is a predictable and simple iteration pattern.

In the end, it's just a matter of preference and style. :)

skrowl• 11 years ago

I bet HR people will love this

b0t• 11 years ago

Just waiting for the resume in Brainfuck

X-Istence• 11 years ago

I did my entire portfolio as a C++ project at one point. Downside is that recruiters and managers looking at my site thought something was wrong on my server and they were seeing the code for the site.

I still have a copy of it online at: http://old.bertjwregeer.com

jerluc• 11 years ago

It would help greatly to add the appropriate accents (aigus) to the title of this submission, as I misread this to refer to "resume in C" as in "resuming a suspended continuation in C" :)

jlukecarlson• 11 years ago

I really liked this project and it inspired me to write something similar in OCaml. If you are interested the link is here: https://news.ycombinator.com/item?id=9226093

Resume in C

Related Stories