245 karma · joined March 12, 2018
If only a few big sites went "vanilla" then you can bet a browser that could "make them look nice" would become popular very quickly.
Other people in our department rose quickly and now have international reputations. But I couldn't treat people like they did and look myself in the mirror every day.
One other thing that greatly helped me in my PhD was the mutual support of fellow candidates. On my own I would probably have had a breakdown in my final year as the intensity of writing up alone must be intolerable. That is why I was shocked to read the comment above where a supervisor pitted candidates against each other: that is criminal in my view.
And some UK recruiters play very dirty. They post fake CVs and fake job ads to mine the market. They pose as candidates to get info from other agents; and ask real candidates what other jobs they have applied for.
I can see how it should be easy to send content from foo#twitter.com to bar#facebook.com as individual messages, format issues not withstanding, if foo and bar have agreed to correspond. But which end would manage the existence of that relationship and push/pull the data?
Maybe it needs third-party brokers to do it?
Interestingly I can see some parallels here with the current status of banking in the UK. After centuries of operation as "closed systems" there are now rules to force banks to provide APIs so that new entrants can offer inter-operation services. Maybe in a hundred years social-media companies will be forced to do the same? ;-)
Would apps like Instagram be "improved" if retouched images displayed a prominent "FAKE" icon of some sort?
However, when I changed jobs and was almost completely remote it was a lot better. Firstly I was working with other remote people so we communicated in different ways and not just about work. Secondly I made more effort to contact other remote workers nearby and meet up with them for coffee or lunch.
On balance I much prefer remote working to office working.
What about a limited period for exclusivity? Do you think, say, 3 years would work? I would be happy to wait that long... in fact I only just recently watched Person Of Interest on Netflix and that has been out for ages.
As to other differentiators like quality of service, I think there is a lot of scope there but channels currently have very little need to innovate because the issue of what content they have dwarfs all other considerations.
Exclusives serve only the producer. They are terrible for consumers, as the orignal commenter lamented. Perhaps "anti-competeitive" is the wrong word, since each channel can compete at having the best exclusives ... probably "anti-consumer" is what I meant.
Exclusives are by definition anti-competitive. Some sort of compulsory licensing might work. Or it might lead to no-one producing anything...
My father and I used to compete in the same sport and I always hated it when he did well. Because however well I did, it was always how much ahead of him I got that mattered.
With my sons I have conciously either not competed against them, or only competed in events that I am rubbish at. And I don't go anywhere near their online games and social networks.
foo_t *maybe_get_foo(/*...*/) {
if (/*foo_is_available*/) {
return foo;
} else {
return NULL;
}
}
foo_t *f = maybe_get_foo();
if (!f) { /*...*/ } // REQUIRED or compile error
do_something(f->bar); // only allowed after NULL check
And I was pointing out that C++ exceptions do exactly that. foo_t *maybe_get_foo(/*...*/) {
if (/*foo_is_available*/) {
return foo;
} else {
throw FooNotAvailable();
}
}
try {
foo_t *f = maybe_get_foo();
do_something(f->bar); // f cannot be NULL
}
catch (const FooNotAvailable& ex) {
/*...*/
}
Sorry if that wasn't the answer you wanted because C++ is not fashionable. But it is a valid option for how to avoid the use of NULL.if (foo_is_available) return foo; else throw FooNotAvailable();
The occasional "I was here" picture is fine, but why even go to a gallery to just to prove that you were there? It's way beyond simple vanity.
I was surprised how one dimensional their process was. And I believe it may have changed since then. My former colleague did apologise when I related my experience and admitted that Google knew they had a problem with the process.
I had never done an "algorithms" type interview before, had done no specific preparation, and was a bit baffled by being asked to do a coding exercise in a text editor whilst talking on the phone.
Since I was an "internal recommend" they gave me a second chance. Presumably because they were surprised at how badly I did. But the second interview was worse than the first.
I came away feeling quite humiliated.
And it is surprisingly common.
The first web pages I wrote had no style information at all. And the first browsers I used allowed (and expected) you to define the default colours and fonts for pages to your own taste.
I am still a fan of minimal styling. It would save me a lot of time to write "style = article" on my pages and be done with it... but most people want their pages to look unique and exactly as they think it should.
But was it that hard before? Constructors, destructors and operators were fine... weren't they?
Another thing I noticed at university was "improvers syndrome". When I took up some new sport or hobby, I always thought I wasn't progressing very well, because I was comparing myself to the people around me who were all improving too. It was only at the start of a new year when lots of newbies arrived that I realised how much I had progressed.