Imagine that you have a pull request with hundreds lines of changes. The reviewer has to spend a lot of time to read all this code and understand suggested changes. As a result, the whole process from submitting a request to its approval can take several days. And it will be a pain for both the reviewer and the author of the request. And chances high that at the end of the day reviewer will still miss something. Also there may be another strategy when the request is reviewed superficially or in the worst scenario such a request can be immediately rejected.
A good overview of who’s paying to have PHP developed and maintained. I wish there was some way to pay for it more directly because our business relies on it.
A good series of helpful tips for keeping your Git repo running nicely. We’re using Gitflow at WeCare Connect and it works really well.
I love the idea of these little computers sitting somewhere to act as a utility server. I’m debating getting one for my home office to do testing.
We’ve tried very hard to place Corgibytes on the side of correcting the imbalance, and Andrea’s efforts have been instrumental. Without her energy and insistence on including under-represented groups in our candidate pool, we’d likely be another team of mostly white males. Some of the policies she’s put in place include empathy and implicit bias training for all team members, transparent salaries to ensure equal pay for all genders, reviewing job descriptions for gender bias before they’re published, and advertising job posts on boards that target under-represented groups.
These efforts have led to some interesting results. Of the five people on our leadership team, I’m currently the only man, and we’ve maintained gender parity on our technical team for the last 3 years. Of course, there are always places where we could do better, which brings us back to our core values.
As the father of two daughters who works in a male dominated field I love seeing these kinds policies. Words matter and I’m glad someone is discussing it in our industry.
I always wonder how much performance you get out of something like #3 - “Use a backslash in front of standard functions” but as someone who does have a tendency to write migration scripts that work over hundreds of thousands of records it might save me some real time.