33 Matching Annotations
  1. Jan 2024
  2. Jun 2023
    1. Conversely, I've never in 16+ years of professional development regretted marking a method protected instead of private for reasons related to API safety
    2. 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().
    3. 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".
    4. Marking methods protected by default is a mitigation for one of the major issues in modern SW development: failure of imagination.
    5. Been disappointed, surprised or hurt by a library etc. that was overly permissive in it's extensibility? I have not.
    6. 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.
    1. 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.

      In other words, make the member variable itself private, but can be abstracted (and access provided) via public methods/properties

    2. As soon as you make a member not-private, you are stuck with it, forever and ever. It's your public interface now.
  3. Mar 2023
  4. Nov 2022
    1. 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:

      Post about status bar in VS Code (visible at bottom of window by default).

      I looked for this since I couldn't figure out the column numbers of where my cursor was in the editor.

      You can toggle this setting by opening command palette and searching "View: Toggle Status Bar Visibility"

      Displays Ln & Col numbers.

  5. Jun 2022
  6. May 2022
    1. 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.

      This is a salient division to create a series of collective actions: make it visible so that we can respond to the threat in a timely and effective manner.

  7. Feb 2022
    1. 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.

      It would be interesting to commission a sculpture of several human forms, perhaps fashioned in clear acrylic, glass, or some other translucent material, to represent the invisible nature of these slaves in an effort to make them visible in the present and while still making a dramatic and more visible statement about their (and millions of others') invisible nature with respect to the historical record.

  8. Oct 2020
    1. 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’

      And in an over-saturated media space, this is exactly the sort of thing that lands us a narcissistic and incompetent president.

  9. Aug 2020
  10. Jun 2020
  11. Sep 2019
    1. These guidelines define evaluation as information used for local decision making, which can also make a CTL’s work visible on campus.

      Evaluation to raise visibility of CTLs on campus.

  12. Nov 2018
  13. Oct 2018
  14. cloud.degrowth.net cloud.degrowth.net
    1. 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.
    2. 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

      Great thought.

  15. Jun 2018
    1. 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.

      Human eye/analysis is limited. Technology enhances visibility.

  16. Sep 2017
    1. friend’s friend’s friend’s

      This is called the horizon of visibility. We generally know who are friends friends are but it is really hard to know who are friends friends friends are. SNA and the internet give us sight beyond the horizon. I wonder if that makes a difference in our choices or social capital?

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

      SNA also gives you the ability to see beyond your social horizon. It is easy to know our friends friends but it is very hard to know our friends friends friends. Much less our friends friends friends friends. But do they influence us in some way? How many steps out does influence remain? Is there a way to measure this in your small paper?

  17. Feb 2017
  18. Jun 2015
  19. Feb 2015
    1. Both are private to participants

      This seems a sensible first step as a sort of soft launch but the capability of future progression to groups with limitations on annotators yet public readership will need to be considered in development.