[–] 4 points 3 months ago (2 children)

Similarly to Onno, I write everything in markdown first, and convert using pandoc. Then I use weasyprint to take the resulting HTML with CSS applied on it, and generate a PDF from all that.

The result is quite nice, and this system has served me for more thant 15 years. A friend working in HR shared that it does stand out, compared to most submissions.

Here's a fragment of Makefile to summarize the concept:

docname=2026

all:
	pandoc -t html5 ${docname}.md -o ${docname}.html
	weasyprint -s ${docname}.css ${docname}.html ${docname}.pdf
  • source
  • [–] [S] 1 point 5 months ago* (2 children)

    Thank you for the feedback. I do score on most occasions. The shot in the comment is scored, but the cut often disappears, so maybe it should be deeper. I am a bit worried about the dough running off to the sides if scored too deep.

    I also suspect proofing is the issue.

  • source
  • parent
  • context
  • [–] 2 points 5 months ago

    We jad a junior to train while we all WFH, but he was a very receptive and smart guy, so it was kind of easy. The last stage of code review, we would go through all changes together in a meeting. I would explain the reasons something may be a bad idea (e.g. harder to maintain later on). Other things were also handled in meetings, so i didn't feel it too different from what I'd do in the office, such as designs/whiteboarding.

    This does require enough capacity from seniors, though.

    In short, it can work, though some people may prefer face to face contact, and the organization/availability has to allow for some hand holding.

  • source
  • parent
  • context
  • view more: ‹ prev next ›