re: 19 Tips For Software Engineers In 2019 VIEW POST

TOP OF THREAD FULL DISCUSSION
re: What I noticed is that there is quite no criticism here on DEV. I think that if we want to grow as a community and to be more valuable, we have to ...

I totally agree that constructive criticism is much more valuable than blanket praise. I can't speak for the level of either on dev.to: I've seen some articles generate good discussion, but perhaps your experience has been different.

I do agree with reporting Menil's comment though. It wasn't constructive and amounted to, "this wasn't the article I wanted to read". I found the tone of it insulting too - calling it "cheesy" and dismissing it as "common sense" - although I'm sure it wasn't meant that way.

If there's something to add - 'I don't agree with that, but how about this' - then great but otherwise it's in danger of descending into mud-slinging, which nobody wants.

From what I can see Menil looks to be a good Android developer and I'd really like to see them write a technical article on getting started with a simple Android app, because it's something I know nothing about.

I don't promote hate speech or mud-slinging and I apologize to the community and especially to the author if I'd cross as such. I didn't want to sound condescending either, but I probably did.

My issue was that maybe the title was misleading for me, and I expected something more technical. Again, my fault.

But, my comment was downvoted so fast, and honestly, that scared me a bit. A community that tries to silent people by downvoting, and doesn't discuss is not a place I'd like to be.

Thank you both Boris and Graham for interacting and possibly opening a topic that is important for DEV.to to grow.

Also as you said Graham, I should've been more constructive and I will. Here are some of the tips I find interesting and valuable in addition to Emma's post:

  1. Consistency
    It has shown with both juniors and more experienced developers that consistency is hard to maintain, especially in long-term projects. Find something interesting every day and keep your level of work consistency at it's optimum.

  2. Deliver often
    This is something I've been practicing for over a year: Show your progress on a daily basis, be transparent about it and deliver often.
    Why?
    Well, you want to show you're going forward, and you want feedback for your work. How will you know you're doing a good job if no one sees it for 2 months straight?
    Make smaller chunks, and deliver often.

  3. Ask for feedback if you don't get any
    We all want to think that we're doing the best work possible, but instead of assumptions, use real data. How? By asking for feedback. Very often you will get one anyways, but whether it's positive or negative, always be grateful: they invested their time to give you a piece of advice or a critic.

Thanks for this, Menil. I really like your additions.

I'm really thankful to you both for engaging in a very reasonable way - it doesn't always happen that way online!

my comment was downvoted so fast, and honestly, that scared me

Challenging something negative is better, of course, but the down vote is a quick option to mark something that's unconstructive. I'm sure the community will get better at this as time goes on.

I'm very glad that you've illustrated number 1 from Emma's article and given some nice additions. Looking forward to your first article on Android development, Menil!

code of conduct - report abuse