I recall a study which suggested that we don't really calculate the trajectory as such, but use some kind of simple visual heuristic to continually align ourselves with where the ball is going to land.
They showed that people running to catch a ball would follow an inefficient curved path as a result of this, rather than actually calculating where the ball will land and moving there in a straight line to intercept it.
It's a lawsuit because Schrems only needs enough of a basis to force the courts to consider certain issues, and to make statements about how GDPR should apply in principle in certain situations, in order to effectively restrict big tech's use of data.
It's a case brought strategically in order to trigger certain questions of interpretation of GDPR rules to be litigated.
Schrems' specific claim only needs to hold enough water to give him standing to get the case through enough filters in the court system to facilitate this.
Rather it's that, in the course of evaluating this case, the court has been forced to make statements clarifying how certain rules and principles in GDPR are to be interpreted. And this has, in effect, narrowed the way Meta etc can use data.
Which for Schrems is really his ultimate goal anyway - his case is just a way to force the courts to rule / establish legal precedent on broader issues.
Schrems has launched several strategic court cases like this to push back on privacy issues, and even runs a non-profit focused on doing so.
I think "activist" is just giving him well-deserved credit for the amount of legwork he puts in to see these cases through.
He is absolutely doing this out of principle / for a cause, and not because of his own individual grievance - he just needs to be able to point to something affecting him personally to give him the legal footing to bring the case to court.
SEEKING WORK | London | Remote (US/EU timezones)
I run a boutique software development studio, where I focus on helping startups get their MVP off the ground, or assisting companies with more intricate and involved development tasks.
Clients come to me when they want more than a copy/paste solution, as I take the time to understand their business and goals in detail, collaborating with them to deliver something highly tailored to their precise needs.
I run a boutique software development studio, where I focus on helping startups get their MVP off the ground, or assisting companies with more intricate and involved development tasks. I'm particularly geared towards projects which involve more complex interactivity or problem-solving.
Clients come to me when they want more than a copy/paste solution, as I take the time to understand their business and goals in detail, collaborating with them to deliver something highly tailored to their precise needs.
SEEKING WORK | London | Remote (US/EU timezones)
I run a boutique software development studio, where I focus on helping startups get their MVP off the ground, or assisting companies with more intricate and involved development tasks. I'm particularly geared towards projects which involve more complex interactivity or problem-solving.
Clients come to me when they want more than a copy/paste solution, as I take the time to understand their business and goals in detail, collaborating with them to deliver something highly tailored to their precise needs.
I think the "compression-oriented" term was coined by Casey Muratori. There's an article expanding on it here: https://caseymuratori.com/blog_0015
> Like a good compressor, I don’t reuse anything until I have at least two instances of it occurring. Many programmers don’t understand how important this is, and try to write “reusable” code right off the bat, but that is probably one of the biggest mistakes you can make. My mantra is, “make your code usable before you try to make it reusable”.
> I always begin by just typing out exactly what I want to happen in each specific case, without any regard to “correctness” or “abstraction” or any other buzzword, and I get that working. Then, when I find myself doing the same thing a second time somewhere else, that is when I pull out the reusable portion and share it, effectively “compressing” the code. I like “compress” better as an analogy, because it means something useful, as opposed to the often-used “abstracting”, which doesn’t really imply anything useful. Who cares if code is abstract?
I run a boutique software development studio, where I focus on helping startups get their MVP off the ground, or assisting companies with more intricate and involved development tasks. I'm particularly geared towards projects which involve more complex interactivity or problem-solving.
Clients come to me when they want more than a copy/paste solution, as I take the time to understand their business and goals in detail, collaborating with them to deliver something highly tailored to their precise needs.
Right - I think it's fair to expect somebody to come up with some kind of approach to solving this, even if they've never encountered the problem or drilled Leetcode before. At least to be able to conceptualize the problem and make a decent attempt.
I wouldn't expect more than brute force. But being able to reason about this, having some working familiarity with graphs etc, is not an unfair bar.
It's not at all unreasonable to think a company might offer a service where they make a profit on the average customer, but make a loss in some edge-cases. It's not such an uncommon model.
You'll often see responses like "but many people don't need to write sorting algorithms from scratch in their day to day work, so they're out of practice". But to me this attitude itself is indicative of the issue.
Being able to do this doesn't require sorting algorithms to be well-practiced and fresh in one's mind. It requires a general ability to visualize and reason about simple data manipulations. Which to me is an absolute fundamental for a programmer working in any field.
If the algorithm can be described with a small sketch or a couple of sentences, generally an implementation should just flow for an experienced programmer who has general fluency? For something like bubble sort, the description can be more or less directly translated to code.
The fact that someone even conceives of this as something which needs to me memorized / practiced suggests to me that they might not have that kind of basic working fluency.
They showed that people running to catch a ball would follow an inefficient curved path as a result of this, rather than actually calculating where the ball will land and moving there in a straight line to intercept it.