benvolio
From R v Bykovets, paras 6-8:
[6] I respectfully disagree. This analysis runs counter to this Court’s jurisprudence under s. 8 of the Charter. We have never approached privacy piecemeal, based on police’s stated intention to use the information they gather in only one way. The right against unreasonable search and seizure, like all Charter rights, must receive a broad and purposive interpretation, reflective of its constitutional source. Since Hunter v. Southam Inc., [1984] 2 S.C.R. 145, we have held that s. 8 seeks to prevent breaches of privacy, rather than to condemn or condone breaches based on the state’s ultimate use of that information. Privacy, once breached, cannot be restored.
[7] To that end, our Court has applied a normative standard to reasonable expectations of privacy. We have defined s. 8 in terms of what privacy should be — in a free, democratic, and open society — balancing the individual’s right to be left alone against the community’s insistence on protection. This normative standard demands we take a broad, functional approach to the subject matter of the search and that we focus on its potential to reveal personal or biographical core information (R. v. Marakah, 2017 SCC 59, [2017] 2 S.C.R. 608, at para. 32).
[8] Informational privacy is particularly critical — and particularly challenging. Our jurisprudence recognizes that computers are unique and present privacy risks that differ from s. 8’s traditional objects. Thus, this Court has determined that s. 8 generally prevents police from seizing a computer without a warrant — even though the device itself provides no information without judicial permission to search its contents — because seizing the computer gives the state the means through which to access its content (R. v. Reeves, 2018 SCC 56, [2018] 3 S.C.R. 531, at para. 34). (emphasis mine)
[1] https://decisions.scc-csc.ca/scc-csc/scc-csc/en/item/20302/i... [2] https://decisions.scc-csc.ca/scc-csc/scc-csc/en/item/14233/i...
Not a bad context window, but makes me wonder how embedded code models would pick that context when dealing with a codebase larger than 100K tokens.
And this makes me further wonder if, when coding with such a tool (or at least a knowledge that they’re becoming more widely used and leaned on), are there some new considerations that we should be applying (or at least starting to think about) when programming? Perhaps having more or fewer comments, perhaps more terse and less readable code that would consume fewer tokens, perhaps different file structures, or even more deliberate naming conventions (like Hungarian notation but for code models) to facilitate searching or token pattern matching of some kind. Ultimately, in what ways could (or should) we adapt to make the most of these tools?
See:
> The evolving landscape of chemical production has rendered toxicological testing using traditional models (i.e., live animals) impractical, and advances in science coupled with ethical concerns have resulted in government agencies, including the United States (US EPA 2021b), European Union, and Canada (Bhuller et al. 2021), committing to reduce, refine, and potentially eliminate the use of mammalian models from certain regulatory testing requirements, where scientifically justified. New approach methodologies (NAMs) are broadly described by the international risk assessment community as any technology, method, approach, or a combination of these that can be used to reduce, refine, or replace animal testing and allow more rapid and effective screening of chemicals. These methods may include the use of computer models or assays with biological molecules, cells, tissues, or organs as well as exposure measurement approaches. [1]
[1] https://www.canada.ca/en/environment-climate-change/services...
P.S. CTRL+F "Health effects" in that report to get a cursory idea of the risks.
Source: worked as a data analyst at the Existing Substances Risk Assessment Bureau
Location: Canada
Remote: Yes or hybrid or onsite
Willing to relocate: Yes
Technologies: Python, C++, MATLAB, Java, PostgreSQL, HTML, CSS, AWS, Django.
Résumé/CV: martyrudolf.com/resume/
Email: martywrudolf+hn at gmail dot com
Newly graduated Computer Engineer with specialization in software. 2 years of professional programming experience including positions in government, industry, and independent consulting work.On the flip side, there seems to be a lot of noise lately and it would be nice to have a break from it, so I'd almost want to be spared from being served these articles entirely. But then that's taking editorial powers to another level.
Location: Edmonton, Alberta, Canada
Remote: Yes or hybrid or onsite
Willing to relocate: Yes
Technologies: Python, C++, MATLAB, Java, PostgreSQL, HTML, CSS, AWS, Django.
Résumé/CV: martyrudolf.com/resume/
Email: martywrudolf+hn at gmail dot com
Newly graduated Computer Engineer with specialization in software. 2 years of professional programming experience including positions in government, industry, and independent consulting work.Ask HN: What HN threads most influenced your thinking about startups?
I often find that reading the comments on a HN post lead to more insights than simply reading the linked website alone or just the OP, so in the spirit of HN as a link aggregator: What HN threads have most contributed to the way you think about startups now?