How Webpack raised $15,000 in 3 months, and the future of open source
The future of open source software is incredibly bright, and we have Webpack and OpenCollective to thank for building the foundation.
<<Focus on the problems with the most impact. If every developer on the team spends 5 minutes a day on a repetitive task that could be automated, and it would only take you 30 minutes to automate it, do it.>>
We use https://xkcd.com/1205/ as the litmus test for such automation improvements. If it’s a borderline call, just…
I agree with Eric on all topics listed. As an Angular developer myself, I’ve set a goal this year to learn React. Even with the little React that I have learned so far, I also agree on his comment made about choosing to learn React first. It’s a very light weight and incredibly powerful tool.
“My comment is for when the cause of the bug is understood.”
In my experience, a bug is almost always very trivial to fix once it is triaged and understood. The typical bug for me is a couple of hours (sometimes days) of triage and 10–20 minutes implementing the fix. Sometimes, the fix is the big part, but that is a much…
Absolutely! My comment is for when the cause of the bug is understood. I thought that would be a given. If the cause for the bug isn’t understood, even understanding it could be a huge effort. Despite the lack of knowledge of the cause, the customer pain can still be measured relatively easily, as you mentioned.