435 karma · joined January 11, 2022
To the question of women in programming, I have no idea why the interest isn't there, but I have known several women programmers who were an asset to the teams they joined, I have known a few that were not, and several men who were not, but percentage wise in my experience I didn't see one group as overwhelming better than the other. You always get some defective programmers.
One company I worked with checked government issued ids at every stage of the interview process. I'm sure people will find a way around this. This also opens your company to discrimination lawsuits, "everything was going fine in the interview until I turned on the camera, then they didn't hire me."
Imagine building a house then selling it, then when neighbors you personally find undesirable move into the neighborhood demanding the home owners association load one of the houses, of which you own neither, and truck it out.
Edit:
He may own half, and the label Warner was the one that made the deal with Spotify.
https://www.ndtv.com/world-news/coronavirus-china-disinfects...
Also packages contain cardboard which is often host to roaches and other plague spreaders, but we both know you were referring to a specific virus.
There once was a person who worked to place land mines as part of their job for the khmer rouge, they spent their life trying to remove them. It didn't fix the initial destruction but it helped to set right some of the damage.
Toyota had uncontrolled acceleration and the drivers were not held responsible.
https://forums.edmunds.com/discussion/6552/toyota/x/toyota-s...
Frequent checkins with detailed commit messages including markdown and graphviz diagrams which state intentions.
Switching the flow from a status meeting low detail reponse of "still working on X issue" to a regular feed of detailed information which serves not only as a development log, documentation, but it crystallizes the developer's planning and thought process because they have to describe what they are doing rather than just "fixing the issue" , or "building the thing".
Persistent chat has made daily stand up status calls redundant. Stakeholders can subscribe to channels which have rich detailed information about what is happening at any given moment. For larger groups a resource can curate the channels and provide a thoughtful summary in a higher level channel of different teams progress. Tools like Azure Dev Ops provide meaningful charts, tracking, and velocity, and the deeper conversations on chat linked to work items, wikis, and repo level filea serve to provide an accurate picture for anyone looking into the effort. Leads, and managers can identify trouble spots and adjust priorities or provide valuable insights. Regular demos can also be linked and serve as a historical record of the development direction.
For reference.