The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,835 other subscribers

Archive for the ‘Documentation Development’ Category

The pitch deck is dead. Write a pitch.md instead. Oh, and do this for any presentation you need to give.

Posted by jpluimers on 2026/08/18

I have been doing presentations based on Markdown since, gosh let me look, oh, at least 2014¹!

But I’m glad it is getting traction: [Wayback/Archive] The pitch deck is dead. Write a pitch.md instead.

… the “quality” of the deck is inversely correlated with the quality of the thinking behind it …

The quote hits the nail on the head, but be sure to read the rest of the article as well: it’s inspiring, holds for way more than pitch decks: it holds for any presentation, especially because of this quote²:

William Zinsser argued in On Writing Well that the act of writing forces clarity – because you can’t write a clear sentence about a thing you don’t understand.

Markdown has so many advantages. You write. It is text based. It can be versioned. I could go on.

Let me quote the closing summary too, as it is so well written showing the advantages of writing:

Write the pitch.md first. You might find you don’t need the deck at all, or you might find that when you do build the deck, it’s better, because you finally know what you’re trying to say.

Via:

Read the rest of this entry »

Posted in Development, Documentation Development, Lightweight markup language, MarkDown, Software Development | Leave a Comment »

Generating ASCII-tables with spanning cells: manual labour still needed

Posted by jpluimers on 2026/05/28

Every now and then, documentation in source code requires an ASCII table. Sometimes table cells are spanning multiple rows or/and column.

TL;DR: The tools I tried did not support that, so manual labour is still needed.

Read the rest of this entry »

Posted in ASCII, ASCII art / AsciiArt, Development, Documentation Development, Encoding, Excel, Fun, HTML, Office, Power User, Software Development, Web Development | Tagged: | Leave a Comment »

RFC2606: Reserved Top Level DNS Names (RFC); draft-ellermann-idnabis-test-tlds-04: Reserved Top Level DNS Names (Internet-Draft, 2008)

Posted by jpluimers on 2022/01/20

Note

Though there are .example.edu and .example.info, though used in documentation and  registered by IANA, have a status is different from the official Reserved Top Level DNS Names:

This is not exactly the same situation as for say ".example.org", where IANA is the registrant *and* registrar.

Wikipedia links:

Read the rest of this entry »

Posted in Development, DNS, Documentation Development, Internet, Power User, Software Development, Testing | Leave a Comment »

Drawing with nice handwriting

Posted by jpluimers on 2021/11/10

Did you also wonder about the nice handwriting in the diagrams of yesterday’s post @adamsand0r drew up a few sketches of design decisions needed to be taken when building a #gitops-based CD pipeline « The Wiert Corner – irregular stream of stuff?

I did too.

They are from [Archive.is] Excalidraw | Hand-drawn look & feel • Collaborative • Secure, with source code at [Archive.is] GitHub – excalidraw/excalidraw: Virtual whiteboard for sketching hand-drawn like diagrams.

Via:

–jeroen

Posted in Development, Documentation Development, LifeHacker, Power User, Software Development | Leave a Comment »

Geek And Poke: The New Developer

Posted by jpluimers on 2019/07/03

Old, but still so funny because it is so true: [WayBackGeek And Poke: The New Developer

–jeroen

via:

Read the rest of this entry »

Posted in Comics, Development, Documentation Development, Fun, Quotes, Software Development | Leave a Comment »

Keep a Changelog

Posted by jpluimers on 2019/03/20

Lot’s of tips (and translations!) on how to Keep a Changelog [WayBack].

There are lots of useful tips, ranging from content (how to write, what to include) to technicalities (order of entries, unreleased, version numbering, date format) that might seem unimportant but in practice makes using the changelog.

The really cool thing: the site has a changelog of itself showing the best practices.

via:

–jeroen

Posted in Development, Documentation Development, Encryption, Let's Encrypt (letsencrypt/certbot), Security, Software Development | Leave a Comment »