Comment on You're overcomplicating production
just_another_person@lemmy.world 5 weeks agoWell, apologies for being bluntly critical. I can offer a few constructive tips to help with writing about technical topics:
- Try starting with a simple topic flow: topic -> synopsis/purpose of why you’re writing -> background -> observations -> point<>counterpoint loop to elaborate on purpose -> closing
- Stay away from asserting your point in the title unless you’re showing definitive proof of something
- Find ways to speak to who may find your writing useful towards the beginning. “If you have a similar problem like X…”, “People who use X may find…”, or “Anyone having similar X experience may find…”. Something like that.
1984@lemmy.today 5 weeks ago
I can offer some constructive tips to you as well: dont speak for all of us.
I liked the article. I didn’t interpret it as “everyone must do what I say”. It was simply a viewpoint from a person on the internet. That is what a blog is.
The complexity of tech stacks have increased enormously in the last 10 years, and it’s only sane to see what tradeoffs we are making to be able to scale easily. Perhaps it’s not worth the trouble for 90% of us. If we follow best practice from cloud providers without thinking for ourselves, we will not learn to think for ourselves either.
So let’s do that. Let’s think, wrote blogs, discuss, and allow for discussions. Don’t shut people down.
just_another_person@lemmy.world 5 weeks ago
Wow, nobody should ever say anything then unless they’re on the right side of everyone else’s opinion or else they might be speaking for everyone. Great tip.
1984@lemmy.today 5 weeks ago
You just criticized the OP for the exact same thing.
just_another_person@lemmy.world 5 weeks ago
I criticized the WRITING of what turned out to be the OP for not having any content in their posted piece aside from a complaint about something. Never said he was wrong to feel how we feels about whatever.