typeofnandev

This is so ruby

MDN gets better, and better, and better. Their discussion on "Things to consider when using frameworks" is so on point and makes me happy to read. Back when I was hiring front-end engineers, I would often ask questions that are nicely answered in this article--things like what kind of problems do front-end frameworks solve, what are the downsides of using front-end frameworks, and digging into over-engineering (i.e., seeing if the person realizes that a front-end framework isn't always the right tool). Great stuff from MDN here, yet again.

The last sentence of this piece makes it for me, and it's this optimism that generally gets me through my day:

But I think we need to make a conscious effort to realize: every time is different. Even if you put the same effort in and make the same decisions, the world, the people in it, and you, have all changed. What worked before, might not work now. The idea that failed before, well - maybe its day has come.

>The problem with Jira (or at least used to) is that it has so much complexities that let people make it overly complicated.

I actually really like this take, because a lot of the times it feels like a tool's complexity is from what it lets you do. I feel like if Jira was "dumber" (i.e., less feature "rich") it'd be so much better.

If only it _was_ the case!

There's a lot of truth to this. I feel like I'm willing to really dig in and learn a tool if I can sense that the power of wielding that tool will be commensurate with the difficulty learning it.