Design, maker, and hacker cultures that originate in working-class communities, center women and femmes, and/or are based in communities of color don’t receive the resources, visibility, validation, and respect that those centered on white, cisgender, heterosexual men do. These communities have deep but less-recognized histories of hacking, making, design, and innovation.

ZenHub’s Issue dependencies not only help teams visualize relationships between pieces of work, but they save team members a lot of time that would otherwise be lost just hunting down information.

When relying on just a list of GitHub issues and comment references to other Issues, there’s a strong possibility that visibility into how these changes impact other tasks get lost or forgotten.

Conversely, I've never in 16+ years of professional development regretted marking a method protected instead of private for reasons related to API safety

I just wanted to tweak Java's BufferedReader to handle custom line delimiters. Thanks to private fields I have to clone the entire class rather than simply extending it and overriding readLine().

I'm not saying never mark methods private. I'm saying the better rule of thumb is to "make methods protected unless there's a good reason not to".

Marking methods protected by default is a mitigation for one of the major issues in modern SW development: failure of imagination.

Been disappointed, surprised or hurt by a library etc. that was overly permissive in it's extensibility? I have not.

The old wisdom "mark it private unless you have a good reason not to" made sense in days when it was written, before open source dominated the developer library space and VCS/dependency mgmt. became hyper collaborative thanks to Github, Maven, etc. Back then there was also money to be made by constraining the way(s) in which a library could be utilized. I spent probably the first 8 or 9 years of my career strictly adhering to this "best practice". Today, I believe it to be bad advice. Sometimes there's a reasonable argument to mark a method private, or a class final but it's exceedingly rare, and even then it's probably not improving anything.

Are protected members/fields really that bad? No. They are way, way worse. As soon as a member is more accessible than private, you are making guarantees to other classes about how that member will behave. Since a field is totally uncontrolled, putting it "out in the wild" opens your class and classes that inherit from or interact with your class to higher bug risk. There is no way to know when a field changes, no way to control who or what changes it. If now, or at some point in the future, any of your code ever depends on a field some certain value, you now have to add validity checks and fallback logic in case it's not the expected value - every place you use it. That's a huge amount of wasted effort when you could've just made it a damn property instead ;) The best way to share information with deriving classes is the read-only property: protected object MyProperty { get; } If you absolutely have to make it read/write, don't. If you really, really have to make it read-write, rethink your design. If you still need it to be read-write, apologize to your colleagues and don't do it again :) A lot of developers believe - and will tell you - that this is overly strict. And it's true that you can get by just fine without being this strict. But taking this approach will help you go from just getting by to remarkably robust software. You'll spend far less time fixing bugs.

As soon as you make a member not-private, you are stuck with it, forever and ever. It's your public interface now.

Derived classes need to follow their base class contracts, but may choose to expose a subtype of base class with more capabilities. This includes making protected members public:

Member Visibility

dsmdavid commented Mar 8, 2021 @tchakabam if you right click on the status bar, do you get many options? Might be worth not showing some of the other options (in my case the line/column was not shown because there were too many options already there) and, after unselecting one:

The three key enablers of the hyperthreat—its invisibility, its ability to evade all existing human threat-response mechanisms, and human hesitancy—will be targeted with three corresponding lines of effort, which will be pursued across multiple task groups:10 Make the hyperthreat visible and knowable; Reduce hyperthreat freedom of action; and Achieve mass and speed of response.

When I did, I tried to see beyond the museum’s opulence to appreciate the nearly invisible hands of the Black laborers who made the Carroll family’s comfort and prosperity possible.

Gradually, we begin to conflate visibility with value. If something is being talked about and seen, we assume that it must be important in some way. – An Illustrated Guide to Guy Debord’s ‘The Society of the Spectacle’

These guidelines define evaluation as information used for local decision making, which can also make a CTL’s work visible on campus.

a fantastic website- Vikalpsangam- in terms of what stories to share. In practical terms, just creating visibility for all these experiences and then linking themup. Website should be a useful start.

If we are so sick of war, we have to stop thinking of fighting against something. We cant fight the big system, but rather making visible all the small beautiful stuff, so that all the bad things would lose power. So observing our own pattern of seeing. The need for celebrating and sharing is so important. We can pass years without even knowing each other. So learning how to embrace diversities, and other ways of communicating

arguments scholars make about The Making of Americans are based on limited knowledge of the text’s underlying structure because the underlying patterns are difficult to discern with close reading.

friend’s friend’s friend’s

friends of our friends’ friends.  

the discipline aims to identify the key actors within networks, where influence is concentrated in these networks, and how that influence is disseminated.

When I share an annotation the link doesn't work for other people, only for me.

Both are private to participants