I'm sorry to tell you, friend, that your article does this too. You don't explain what XAML is, for instance. Certain sentences almost read like the satire you posted: "how to do in C# code the things which are currently done in XAML (such as binding)". You also tell the reader to "edit the relevant line" which doesn't help a total beginner.

The fact of the matter is that writing for the lowest common denominator takes an incredible amount of time and writing skill. Most of us don't have one, some don't have both.

If you keep practicing technical writing, I'm sure you'll get there eventually. Just keep in mind that most people do not want to be technical writers

[–] SmartmanApps@programming.dev -4 points 6 days ago (10 children)

I’m sorry to tell you, friend, that your article does this too

Nope.

You don’t explain what XAML is, for instance

You know the article is about how to write a page and NOT use XAML, right?? 😂 If you don't know what it is then you don't need to (hence why I point out that it isn't pre-requisite knowledge). If you do know what it is then that's probably what brought you to my page to begin with - stop using it! 😂

Certain sentences almost read like the satire you posted:

Now read the links provided in the pre-requisite knowledge. You're the second person who thinks people learn things by reading the first paragraph only.

You also tell the reader to “edit the relevant line” which doesn’t help a total beginner

Now read the links in the pre-requisite knowledge, clone the repo, follow the instructions up to that point in the article, and guess which line you're on! 😂

I’m sure you’ll get there eventually

It's there already, if you had just bothered reading it all and following the instructions, instead of just criticising without even trying it

Just keep in mind that most people do not want to be technical writers

Probably because of people like you who criticise them without even trying to follow the directions to begin with. I'm guessing you also submit issues which say "It doesn't work. Please fix"

[–] r4venw@sh.itjust.works 6 points 6 days ago (1 children)

I don't want to make this a "gotcha", but you say no xaml knowledge needed but then talk about it and have the reader touch them (mostly delete). You say you usually delete this xaml file but I don't need to do that. Why? What do I gain or lose? I thought I didn't need to know xaml?

I read your entire tutorial. I've been in the industry for a while. I found it hard to read but mostly due to the sentence structure. I suppose if english isn't your first language (it isn't mine), that might explain it. I can give you more comprehensive feedback, if you'd like.

I know hearing constructive criticism is hard, but it is part of the learning process.

[–] SmartmanApps@programming.dev -1 points 6 days ago

I don’t want to make this a “gotcha”, but you say no xaml knowledge needed but then talk about it and have the reader touch them (mostly delete).

I only have them delete the XAML files. You don't need to know anything about what's inside a file to delete it 😂 Also, I only talk about the benefits of getting rid of them, which also doesn't require any knowledge of XAML.

You say you usually delete this xaml file but I don’t need to do that. Why?

No I don't! I say disabling implicit usings is optional, and do explain why I do it, then delete the XAML files. You seem to have conflated 2 successive paragraphs.

I thought I didn’t need to know xaml?

You don't. They're never used anywhere in the whole thing. We only delete the XAML files, then replace them with C#.

I read your entire tutorial.

Not very carefully apparently.

load more comments (8 replies)