WolfOliver

Try monsterwriter. It supports academic features (footnotes, cross-references, citations, captions...) and it supports export to HTML, LaTeX, PDF

MonsterWriter

Nice article, I always had the impression that we value DX a little too much. I mean developers are paid to do the jobs, but users are not.

I use MonsterWriter

Agree it is a little tricky to get startet. But once configured, it helps a lot

Do you have any references that BDD was used as a term before Cucumber?

It should be "when people started considering parts of the system under test as the “units”"

It make sense to write a test for a class when the class/method does complex calculations. Today this is less the case then it was when the test pyramid was introduced.

> It leads with considering "unit" to be "the whole system" being bad

I do not understand this statement. Could you point out which part of the article you mean.

Thats a new term for me, thanks for pointing out.

It is the safest way to make sure your test will actually fail in case your code does not work. I often had the situation where I wrote a test which is always green, if if the code is broken.

Often I do not have the clarity to write the test first, then I just write the code and the test later. But I comment out the code or introduce a bug on purpose to make sure when I run the test code it actually works and detects the bug.

Agree, this is usually a sign the team writes tests for the sake of writing tests.

Maybe the term TDD in the title can be replaced with "unit testing". But unit testing is an major part of TDD.

I've wrote some thoughts on this topic down a few months ago:

https://www.monsterwriter.app/chatgpt-in-academic-writing.ht...

[Author’s note: These are not real references, unfortunately.]

In case of HTMX I would need to?

With SPA you only need one process (The API), the static SPA files should be placed on a CDN.

Whats the benefit then? Having another process running so I can justify the Kubernetes overhead?

I do not have a problem with the inconsistencies between implementations, this is indeed not really an issue. But what I do not like:

- Inserting a link is confusing, is it [url](text), (url)[text], [text](url), or (text)[url]

- Tables are a pain

- Footnotes are a pain

- Cross referencing headings are a pain

- Bold, italic, underline are the only features that are simple to use, but I do not need it that much

- No other things than the ones which are a pain or I do not use very often are not possible at all (image captions, table of content, ...)

Of course you can say you can use a proper editor, but then I could as well use a WYSIWYG solution

I'm not saying doing it all the time, at least not for public interfaces of a library

That's why I build MonsterWriter

I work on MonsterWriter. The Desktop app is on the market for some time now but now I'm working on a SaaS version.

Sign up is possible but the link is nowhere on the website: https://app.monsterwriter.app/

lets see how the unicorn looks tomorrow

Also an interesting read: "The Big TDD Misunderstanding"

https://linkedrecords.com/the-big-tdd-misunderstanding-8e22c...

funny how many layers you can put on top of prosemirror and claiming to have implemented real time collaboration.

30$ per month seems overkill

If you have something which requires a sophisticated layout then Adobe InDesign. If you have long linear text with footnotes, references, cross references, then have a look at MonsterWriter

ChatGPT / OpenAI

I'm using MonsterWriter. It lacks some features but it is in active development.

MonsterWriter: The most enjoyable desktop app for writing a thesis or paper