Updated my resume. Any thoughts, feedback or info is always most welcome. Typos are inevitable when its this long....

jeffreyfreeman.me/resume/

Follow

@freemo That is a gorgeous formatting. Did you write it in LateX?

@freemo I was afraid you'd say that. I was hoping you'd say, "no, I used some proprietary software" and I wouldn't feel pressure to improve my LaTeX resumes (which haven't been updated in years)

@worldsendless I think i heavily hacked some other format that was out there... I dont recall... but yea its pretty damn fancy :) and sorry to say it is latex.

@freemo @worldsendless

I see you're playing mind games with it too: "Oh yeah, my totally gorgeous LaTeX based resume was made with my LaTeX skills that I only list as 'basic'. Please conclude my other 'advanced' skills are even more totally awesome, as I'm being humble about something I'm good at."

I'm on to you 😂

P.S. I'm gonna plug my resume template (based HEAVILY on Jean-luc Doumont's template) [here](github.com/johnabs/CV_Template) for @worldsendless

@freemo @worldsendless looks a lot like the modern-cv template. Mine is based on the same. Looks great!

@anderson_pa

Its been a while, i forget the name of the template i based it off of.

@worldsendless

@freemo @worldsendless
The timeline bargraphs are truly impressive once you realize what they show and how.
Do the blue bars get updated every time you compile the LaTeX with the current date?

@freemo @worldsendless So, I'd like to do more things in LaTeX, but I've noticed LaTeX (well, Mathjax) is broken on Qoto, and every time Terence Tao posts LaTeX it blows up my home page with giant letters. I'm told this is a known problem. There is a known Qoto problems list somewhere? What is known about the problem, and what do you know and not know about what needs to be done to fix it?

@radehi

I think latex is the only known problem that effects users and will be fixed soon.

@worldsendless

@freemo @worldsendless The Markdown support is also spectacularly broken, as we documented in detail yesterday. I'm glad to hear you're on a path to getting Mathjax fixed! Let me know if I can do anything to help.

@radehi

"Spectacularly"? I use it everyday. Only aspect I know that is broken is the codeblocks wrt new lines... what else am I missing?

@worldsendless

@freemo @worldsendless Search on Qoto is also broken (finds no toot hits for the search "markdown", without quotes) but I was able to find my post on the matter chronologically by scrolling down to yesterday: qoto.org/@radehi/1093850911259

This documents four or arguably three separate bugs in Markdown support, one of which is the one you mention. I've seen a fifth one as well that I can't remember right now, but finding three new bugs in the Markdown implementation while trying to find a workaround for the first one makes me think there are probably dozens.

So, there is a place to document these findings so they don't get lost, no?

@freemo @worldsendless Actually, if you count "newlines are ignored inside code blocks, but inside normal paragraphs newlines are treated as `<br>`" as two bugs instead of one, that post documents five bugs in Qoto's Markdown support rather than four.

@freemo @worldsendless By the way, I hope I'm not hurting your feelings by criticizing your code. I appreciate that there are some beginnings of Markdown support on Qoto! I want to help make it better! (I just don't know where it is or how to run it outside of Qoto yet.) But the first step to making it better is cataloging its deficiencies.

@radehi

I wouldnt could those seperate.. seems like two bugs.. 1) latex rendering 2) new lines in code blocks in markdown

@worldsendless

@freemo @worldsendless I can't parse that, but I haven't been talking about LaTeX rendering for two hours!

@radehi

thats not broken, thats intended. free text searches only allow you to search toots you were tagged in. The only time you can search toots you arent tagged in would be hashtags.

@worldsendless

@freemo @worldsendless The documentation that pops up under the search box when it gets focus says, "Simple text returns toots you have written, favourited, boosted, or have been mentioned in, ..." and this is a toot that I wrote, yesterday, so either it should have been returned or the documentation under the search box shouldn't claim it will be returned. But that second option is obviously a lot worse, just easier.

@freemo @worldsendless Also, even though you just now tagged me in a toot that says "markdown", text search for "markdown" doesn't return that toot either. I think free text search for toots is just broken, maybe there's a process that's not running that's supposed to build a full-text index or something.

@radehi

Ahh that is interesting... the search functionality is unmodified from vanilla mastodon, so you will have to file a bug report there. We use their code.

@worldsendless

@freemo @worldsendless Does it work for you, at least to the point of successfully doing a full-text search over toots you've been mentioned in?

@radehi @freemo I've never really tried search before now, but just tried it on the text from one of my toots and it seems to work fine, showing first my own matches and then related toots. Using qoto and the web interface here.

@worldsendless @freemo Thanks! I wonder why I get results that are so much worse.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.