Re-working the resume in LaTeX both makes me wonder why I keep my resume in LaTeX and reminds me why I keep my resume in LaTeX.
@craigmaloney You're not alone 😉
👍 on the LaTeX resume. I always looked for hints of LaTeX when I was in hiring 😏
@tas Pretty sure you'd notice this one; it's about as stock as it gets:
@craigmaloney Looks about right for LaTeX 😁
Job hunting?
@tas Yeah, looking for remote work as a Python back-end developer.
That or a fat wallet on the sidewalk with no ID.
Either will do.
@craigmaloney I don't know many doing remote Python stuff these days 😢
@tas No worries. Seems the world moved on when i wasn't looking. 😁
@craigmaloney @tas @zigg Yeah, I've noticed a lot of places that value polyglots rather than folks who really understand whatever language they have. Not that it's a bad thing, but it also seems the new language hotness is Go or Rust. That's partly why I learned some Scheme: to better understand language fundamentals and functional programming.
I still consider JavaScript as my nemesis, but it seems you can't even get past HR without some JavaScript experience.
@craigmaloney @zigg Where I'm at right now very much prefers polyglots in terms of business workflows / etc (what we model in software) but tends to prefer we know our internal frameworks like the back of our hand.
On one hand it's great: domain expertise. On the other: less broad knowledge of other approaches (sometimes).
I'm with you on JS though. If that's a job requirement I don't think I'd get past 'resume pile'.
@tas @craigmaloney JavaScript in particular is a sore point, and I 100% get why. Until my latest project, I didn't want anything to do with it. We needed to, though, because of the browser, and because of community attention.
But I've been increasingly working with React, Redux, and TypeScript and I think those three together have created a much more workable and solid environment. It's literally the first time single-page apps haven't been something my brain actively fights against.
@craigmaloney @tas @zigg Yeah, ECMAScript 6 is the first time I've looked at JavaScript code and not wanted to throw up.
I'm still on the fence about React. I don't trust Facebook and have been looking into alternatives like Vue.js for learning a front-end framework.
@craigmaloney @zigg +1 for FB distrust.
We need better non-corporate tools 😉
@tas @craigmaloney There's always Preact 😁
@zigg @craigmaloney Now I think you're trying to needle me 😉
@tas @craigmaloney Haha. Nah, actually, some people have discussed using that as an alternative in case Facebook goes nuclear with their patent protection license clause. Apparently it's pretty much a drop-in
@zigg @craigmaloney Wasn't there a recent ripple about the patent protection clause basically trashing the ability to re-use react in other OSS style projects?
I could see some smart people easily arguing that the patent clause is the nuclear option already. 🤔
@tas Yeah, that was the discussion.
The one thing I don't know is if Facebook actually holds any patents in React, or if they'll just pull your rights to use React if you trip the patent stuff. The latter could be dealt with by using Preact; the former is probably impossible to deal with.
