[RodericDay]

Second this. Mithril.js is absolutely incredible, and my coworkers are often surprised at how quickly I can dive into a React project and fix an issue because I don't carry the baggage of doing things "the react way".

Every now and then I use software tools where rather than complaining about how x or y should be different, everything seems to be the best possible version of something I'd have come up with myself, and I have zero complaints. Mithril.js is one of those tools.

You're not "in a Mithril project", you're basically just using javascript but the VDOM is expertly and minimally handled by some key functions.

Participating in the project via Gitter was very welcoming as well. Long live Mithril!

[shady-lady]

> can dive into a React project and fix an issue because I don't carry the baggage of doing things "the react way".

Would they not want your solution to conform to existing solutions; which (regardless of being idiomatic to React) would be idiomatic to the codebase?

[RodericDay]

I usually find the issue, point it out, then they make sure they implement the fix in a way that is not alien to their codebase.

It's not many hands on one project but everyone taking care of their own projects, so it's a bit different where I'm at right now.

[Rapzid]

Some people are way better at finding issues than others, even in other's code bases.

Another good skill to have though, that is unfortunately not super duper common either, is being able to figure out and match conventions and patterns in code bases when introducing changes.