Browser addons, rss readers, cli tools like youtube dl, light clients like chat thumbnailers, reader modes and so on don't either. This can add up depending of your site, and have a different significance than scrappers.
Nah, it's very easy to be objective when on a 5 pages homework, one write 5, and the others 0. Or if only one person has compiling code on their machine the day before the project. Of if only one person speak on the conf because the others don't have anything to say.
I've never personally seen that. I've seen cases where one person writes four pages, and one writes one page claiming it was the hardest. I've seen cases where one person writes the code, and one writes the paper about the code. The only case I've seen where one person does all the work the person who does all the work refuses to allow the others to help.
As most things in school, it's an artificial situation that bears no resemblance to the real world.
IRL:
- people has much higher stakes, while in school tanking a class project is no big deal for most slackers. IRL, they can get excluded, isolated, shamed, fired and so on.
- such group would exist rarely in the first place, because institutions filter people;
- if you are in the rare situation it happens, you can get out of it, but you it's very hard to move in the school structure, not to mention out of it.
Anecdotally, I've seen the scenario playing out many times in schools, but rarely in a restaurant, a dev team, a NGO or a sport club. There are productivity differences, sometimes immense, and an occasional slacker, but that's not the same order of magnitude at all.
I've seen the same school-type dynamic play out in companies amongst people getting paid the sort of numbers that make folks on HN say "most people don't get that, not everybody works at a FAANG."
We (as a species, really) are bad at interviewing lots of people that we don't already know well - just like we're bad at testing academically, surprise! - and we're also bad at coaching/firing/managing them.
> We can't pretend that something essential for the process doesn't matter because we do a classification handwaving. It all counts
Funny thing: in France, stats for wind energy include the cost of wiring, and cables are required to be buried. Stats for nuclear just ignore the wiring. I'm pro nuclear, but that always bugged me.
I'm not sure if you're being intentionally obtuse or not. GA phones home with vast information about user, and builds a profile of them. That profile is correlated across sites to personalize search results and sell ads.
Please omit personal swipes from your HN comments. Your post would be fine without the first sentence.
Note this site guideline, including the last bit: "Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith."
I'm not being intentionally obtuse, but I also don't know all of Google's advertising business. I didn't think Google Analytics did that? What makes you think it does?
(GA sends a message to Google, but I had thought that it was not linked to your behavior on other sites via GA?)
Googe Analytics consultant here (not Google employee).
1. Google Analytics' primary identity signal is a first-party cookie. this is not shared between domains. There is no technical way to link identity between domains with different cookie values.
1a. Google Analytics has built-in library functions to allow site owners to share first-party cookie values between a whitelisted set of domains. This effectively lets one company with multiple sites share a first-party identifier, but still not let anyone (Google or otherwise) link that identity to identities set on other sites.
1b. BUT. But. BUT. Google is rolling out "Google Signals" for Google Analytics, which will use your Google Account as the identity signal instead for users who are logged in to Chrome. This, obviously, lets your identity be correlated across sites.
(Personally, I suspect that the availability of this feature played a part in Google's decision to let Chrome follow the industry towards blocking third-party cookies. But this is a baseless opinion, one step removed from a conspiracy theory.)
2. Google Analytics can link their identifier (the first-party cookie or Google Signals) to your DoubleClick profile via DoubleClick's third-party cookie. The checkbox that does this is unchecked by default. There are many other features of GA that encourage or require you to check this checkbox.
2a. Google's documentation (including legal contracts!) places limits in the data exchanged between the two profiles. Data exchanged does include demographic and interest information from DoubleClick's profile into GA. This is one of the big reasons why people click the checkbox.
To my knowledge, GA data is not used to inform the DoubleClick profile. GA data can be used to build an "audience" in various Google ad platforms, and direct ads to those people specifically, or to use as the basis for a "look-alike audience."
3. Google is a Processor under GDPR for Google Analytics, and a Controller under GDPR for Google Ads. To a first approximation, this means they make the specific legal claim that they do not use GA data for their own purposes. Linking Analytics and Ads data is... complicated and frankly I still haven't gotten an explanation of its legal status that I fully understand.
In my personal opinion, I don't think Google actually uses Google Analytics data. Most Analytics implementations are tire fires, and they can get all the data from other more reliable sources, like Publisher data or Chrome. Given that they have based on their entire GDPR compliance strategy for Analytics on being a Processor, I don't think the risk/reward is there.
(apologies for lack of copy-editing, the thunder's about to take my internet away)
Interesting insight. Their privacy policy suggests they are able to do this however[1]:
"When you’re not signed in to a Google Account, we store the information we collect with unique identifiers tied to the browser, application, or device you’re using."
What is stopping, legally, them from taking e.g. HTTP Headers from independent connections and linking them together through fingerprinting? Maybe this is not implemented in Google Analytics, but that is certainly not the only connection made to Google on most websites (see e.g. gstatic and Firebase). Since there is practically no technical barrier, it seems that the vague privacy policy leads to the only question being what the 'unique identifiers' are exactly.
Am I missing something, or does this not address the fact that https://whatsmybrowser.info/ will always yield the same thing whether a connection is made to GA, Firebase, YouTube or Blogger? That seems to have to do with connection timing and caching, not with what the connection itself leaks.
I thought the parent was talking about using information about the network connection to link users across sites hosted by the same entity?
If you're talking about fingerprinting in general, that is also something that all the browsers are working on. I'm most familiar with Chrome's strategy, which is to first switch APIs that provide a lot of entropy from something you get by default to something you have to actively request, figure out how to provide similar functionality more privately, and then enforce a privacy budget that does not allow collecting enough information to identify users: https://www.chromium.org/Home/chromium-privacy/privacy-sandb...
Is Google going to give back the $100B is made from cross site tracking in the past?
Is Google going to consider YouTube, Gmail, Maps, and Android Location history different sites, or is "having an effective monopoly an exemption to crosss-site tracking prohibition?
Does anything in the proposal prevent server-side cross-site tracking? (No.)
Is Google going to stop buying third party tracking data like credit card transactions?
- bad trips are rare if your respect set and settings, which every responsible consumer will tell you to do.
- they have been used politically in bad faith. It's only fair to not add to the stack of propaganda.
- most of bad trips are not a bad thing. It can be spectacular, but rarely dangerous, and may actually be a good thing. My only bad trip helped me grow just like my good ones. It was not pleasant, just like throwing up stale food is not, but I was mentally healthier after it. Some dark things are inside of us all, and it's good they come out, but the experience is likely not something we crave for.
> I think splitting the market will be fine. However, I suspect many side-loading-capable iPhones are going to have many more security problems and privacy breaches.
Security and flexibility are always at odd with each other. But for side loading, I'm not really worried.
Users that are susceptible to security problems don't have the technical know-how to even do something as simple as sideloading. Those who are technical enough usually are not the entry point for malware.
>Users that are susceptible to security problems don't have the technical know-how to even do something as simple as sideloading. Those who are technical enough usually are not the entry point for malware.
If sideloading is made too difficult for average users, it would totally negate the anti-trust (competitive) benefits of forcing the platform open in the first place.
Either governments make sideloading easy and approachable to the masses, and accept the UX/security/privacy risks involved, or they make it cumbersome, and accept the continuation of the App Store monopoly.
I'm not sure about that. I do see a lot more intellectual rigor in the older techies than in the ones from my generation. Just basic grammar illustrate that well.
And it makes sense, if you can't rely on automatic systems to do part of your work, you will be trained by your daily tasks to be a more powerful thinker.
If what the company do is hard, being ok will not cut it. You cannot google your way into innovation, you can't copy/paste architecture design, and your calculator won't save you from a logical mistake.
I'm personnally very adapted to agile envs with margin of errors and a lot of feedback loops. But a waterfall is more challenging, because I'm not born in it. And you don't use scrum to build the path to moon landing.
More than that, I arised in the "a good dev is lazy" period, where working smart, not hard was praised. But hitting 30, reality calls back: there are no shortcut to awesomeness, you will have to work hard. And not many engineers are ready to do so. The ones who do often create their company.
> I do see a lot more intellectual rigor in the older techies than in the ones from my generation.
My experience has been the opposite - though as this is based on observation it's obviously subjective - and opportunities for selection-bias are also present (i.e. how many of the last-generation that didn't get promoted-out of being a technical contributor was because they were more valuable to the company that way?)
Your remark about automated tooling is interesting - because I feel that modern tooling (TLA+, Z3, constraint-provers, and cutting-edge languages like Haskell, Idris, and so on) really do require almost a postgraduate-level of understanding of the CS theory involved - whereas if you look at _the SE scene_ in the 1970s and 1980s - or even the mid-1990s, the tooling certainly did require you to do more planning and reasoning ahead of time (VB6, lol) but I can't see the entire industry of the time doing their modelling and verification entirely by themselves: on the contrary (and based on the horror-inducing programming code I've seen) a lot of it was ad-hoc and trial-and-error - Visual Studio didn't get built-in support for unit-tests until 2008 (or 2005 if you had the expensive edition). Also consider that the old SE processes used back then (Waterfall, boxed software, slow-moving-and-big release cycles, etc) meant there was more room for less-rigorous folks in large software dev teams.
> and your calculator won't save you from a logical listake.
For that, you need a spell-checker!
UPDATE: Ah, you edited your post, which ruins the joke :/
With all due respect, I think you are mixing apples and oranges here.
"TLA+, Z3, constraint-provers, and cutting-edge languages like Haskell, Idris, and so on" is not exactly the bread and butter of IT work nowadays, so why do you think it is appropriate to compare it with "VB6, lol"?
(When you say "IT work" - are you referring to software-engineering work specifically - or "IT" in general? (I'm personally not a fan of "IT" as a term at all because it's unhelpfully vague[1]).
I wasn't comparing them directly like that.
My point is that in the 1990s if you used VB in production systems then you would effectively be forced into investing a lot of company resources - and mental effort - into all kinds of entirely disconnected approaches for formalising, proving and even testing your system. Whereas the state of the art for formalising SWE work today currently lies in tools like TLA+, Z3, and others and how it's significantly easier to map those formal models to our production program code back-and-forth (when written in more expressive and formal-friendly languages like Haskell, etc) than it was 20+ years ago.
Back then the sheer effort involved to perform even automated unit testing and integration testing of VB6 code, and other languages of a similar nature, was massive because, not least, the VB6 tooling completely lacked that functionality, and their lack of terse expressivity meant time spent just writing repetitive code with little value - and things were tenfold worse if you were using one of the myriad proprietary other 4GL languages of the time because most of those vendors swore-off any kind of interoperability or extension mechanism because they saw them as a threat to their business model (as a textbook example see Progress' utterly laughable defense of maintaining their position here: https://www.progress.com/tutorials/odbc/open-source-database despite their market-share shrinking and the company quickly pivoting away from their own database system and onto being a generic component/tooling vendor).
Even so, I'm not being ageist: VB6 wasn't state-of-the-art when it came out: Java is older and far better in that regard (VB6's type system is very anemic). I was singling out VB6 for criticism specifically because even back then it wasn't very good, it's just disappointing that so many people used it as the basis for production systems.
[1] Whenever UK friends and relatives refer to me as "working in IT in the 'states" I outright deny it: I really don't feel that I work in "IT".
I’m not a Progress user. Instead I get paid lots of money to help companies move-away from Progress to Postgres :)
(Which in practice just means figuring out how to get their bloody “SQL Broker” processes running then dumping everything over ODBC. In order to circumvent the arbitrary and unfair “Users/Connections” licensing restrictions I reversed Progress’ super-seeekrit program code to figure out how their license keys worked and made my own keygen in a weekend, that was fun - I got paid to do that too!). The fact it’s possible to slam out software within a few days while drunk-and/or-stoned (I don’t remember, lol) that undoes Progress’ entire business-model built-around vendor lock-in shows what a house-of-cards they’ve built for themselves.
> I do see a lot more intellectual rigor in the older techies than in the ones from my generation
I have a theory on this. An architect in private practice told me a couple of years ago how he was having trouble getting good junior architects, so was resorting to graduates. He felt his small practice was not the best place for a rigourous training. He recounted that in the past there was a giant pool of qualified and experienced staff coming from the councils, railways and public utilities. There was also a similar pool of state supported industry, Rolls Royce, BA etc. These positions took graduates (or even apprentices) and trained them up. These were also jobs for life with opportunity for progression and final salary pensions attached. Most of these have been squeezed out by 30 years of privatisation and The Cuts post 2008.
I personally worked at a company that had grown out of a government research agency some years before. The majority of employees were from that original batch of junior engineers transferring over, even filling roles like HR, Health and Safety, purchasing etc. I don't see how this could happen today.
I feel like in lusting after what Silicon Valley has, we have undone what we had with nothing to replace it.
Ad blockers also often cut GA off.