This is a weekly roundup of awesome DEV comments that you may have missed. You are welcome and encouraged to boost posts and comments yourself using the #bestofdev tag.
The most popular discussion thread this week asked the following: What software development skills only come with experience?. @biros
offered their insights:
Being able to challenge the PO's requirements.
I mean: not accepting every demands without any question.
Being able to understand the business needs and feeling comfortable enough to say no when a user story adds no value to the product.
This is the first 3 come to my mind at the moment
- Being able to make a good estimation
- Do not take things personally
- Understand business needs
Have you ever heard a more beautiful phrase than this? The statement in question is:
Everything's fine with the monitoring. Turns out the site's just more stable
Ah, what a wonderful realization. Luckily, as @chiefnoah
points out, we can all capture that feeling... sort of 🙈:
I'm on a new project, and we don't have monitoring set up yet so I can live in blissful ignorance for now
answered the question What is a type of "overconfidence" you have observed in developers?, by offering a well-justified vent:
I think one big thing I've noticed is people offering unsolicited advice that tends to be there to make the advice giver feel good instead of the recipient, and that's usually inappropriate for the level of the recipient.
I get a lot of "explanations" of things in response to posts I put online that are kind of insulting. For example, I've had both the concept of Git and an explanation of what a pull request is recently, which while helpful for someone starting out, isn't relevant at all for somebody who makes a ton of pull requests and has for years. Lots of unsolicited code reviews of stuff too, I've even had my own code explained back to me! I know what my code does and why, that's why I wrote it!
Looking at the requirements of a project, then looking at the code, then... (╯°□°）╯︵ ┻━┻
In all seriousness though its taking requirements and implementing them. Sometimes its in very old bad code, some ok code, and sometimes some really good code. The hard part is understanding the big picture when there are thousands of tables, separate systems that need to talk to each other and with almost none of it documented.
See you next week for more great comments ✌