It's sometimes seen as a security issue, especially if you are not provided with a company-issued laptop. Or your work may require specialized equipment like beefy machines for 3D rendering or local access to a server.
I wouldn't say that working efficiently with people directly counts as "meta". Productive cooperation with others sounds like a straightforward skill to improve, with no new rules being introduced.
Maybe new company/team organizational approaches or methodologies (Waterfall, Kanban, etc.) can count as playing the meta and give you an edge over the competition.
Both can be classified as 'anecdotes', I agree, but talking about your work conditions when asked, is a completely different anecdote as opposed to someone not actively complaining when they are with friends/acquaintances.
The difference between having a coding team manager that expects everyone should work 60+ hours and a non-coder who is against it, can be huge. I prefer the latter.
I always preferred to have a boss/manager that has some knowledge of what I do. Maybe not the best. But if I explain an issue or problem, they're not lost. Thus, when I say "this is going to take a while" they don't say "you need to do it faster". They let me do the work and on the backend try to find an extra hand, information or anything that might help me. Because they KNOW what I'm going through.
I've never met or heard of a manager whose only skill is managing and was actually helpful in the work process. Plus, the useless managers are typically the ones who think the peons should work at 60 hours, because they were never the peon.
Hey! I get to say this. I am triggered when I hear people only want to be managers because I know they're incredibly useless meat bags.
I vaguely remember all of those things as separate phases.
- Moving away from IE, I fell in love with Opera (lots of built-in features), most others with Firefox
- Chrome comes in, it's Google, it's lightweight, people try it and like it
- Chrome gets really fast, it appeals to even more people
- Meanwhile, Firefox has enough extension power to replace Opera for me (who can live with the tabs BELOW address bar or without mouse gestures?)
- Chrome implements the aforementioned technical stuff (separate processes, etc.), appealing to power users (this may have happened before speed improvements or at the same time)
- Chrome finally gets extensions and I start using it personally, but it's impossible to be a web dev without Firefox+Firebug. (IE6 still sucks, but combined with Visual Studio, feels superb for JS debugging)
- Chrome's dev tools gradually get better at everything. I start living in Chrome.
... years later ...
- A year ago I often used Firefox for its great Canvas debugger. They broke it. I've since forgotten about Firefox.
... 2019 ...
- Microsoft is trying to drive people away from IE, hoping for Edge adoption. I don't care for Firefox. Opera is almost Chrome with extensions. Edge sounds like it wants to be Chrome. Chrome won on most battlefronts. I don't like that fact, because of the "free from corporate greed" reasons mentioned, but it's going to be hard to change the status quo.
That is not correct. MS is ditching Trident for Blink but Edge and Chakra are still remaining technologies. This is unfortunate because Chrome is super slow on large CSS animations
> If the guy examines Samsung Galaxy phones, it would almost be the same.
This is just guessing. If I have to bet, I'd as well bet that Google/Samsung/ISPs/Everyone is spying on you, but just guessing and shrugging it off is not helping.
We should be inspired to check even more devices and inform users about backdoor traffic.
Comparing is not judging or blaming. The GP suggests that both TPB and Google are in a gray area, which I partially agree with, but I think they are in different gray areas.
TPB, as described, is in a moral gray area - "We know some of the uploaded stuff is immoral" - so they delete what's immoral (their judgement - child porn/copyright stuff/anything between), they arbitrarily decide what you see
Google is in an algorithmic gray area - "The algorithm decides what's best for you, we want the best for you, but we won't judge what's best for you" - so they do nothing and hope for the best (and least damage), the algorithm arbitrarily decides what you see
TPB said "We are not responsible for the content people upload." Except then they deleted CP, probably for many good as well as self-serving reasons: CP is bad, obviously, but also brings bad press (hard to get the public on the side of piracy when it leads to ease of CP access), as well as the holy wrath of pretty much every criminal federal agency in countries around the world, as opposed to just whatever branch of whatever agency is in charge of copyright protection. Doubt they could get hosting in any country if they didn't take the CP down.
But by taking CP down, they demonstrated that they do and can monitor content, that they can take it down, that they do take responsibility for at least some of it. Legally that's a shot in the foot, I thought, but they still find hosting so who knows.
Thank you for explaining. That's what I meant by the uploader defense. I'm fairly sure Google removes CP from their search results so obviously they can exercise some control over their content. So they can't blame it all on the algorithm.
Personally, I think unit tests shine best when you're designing an API. I can swing from hate to love and back about TDD in minutes, but when it comes to thinking about how your code will be used, unit tests (did we stop using that term?) are a tremendously useful tool I have.
I guess if all code written could be seen as an API, TDD would be great, but that's not the world I live in.
This is why I prefer free to implement open standards that are (hopefully) well designed and specific.
Inter-operablility and interchangeability of parts means that it's possible to validate an implementation to at least some degree.
The best example that I can think of off the top of my head is the OpenGL 4.4/4.5 work that is nearing conformance for the Mesa3D project ( https://en.wikipedia.org/wiki/Mesa_(computer_graphics) ); while the functional coverage for the main modern drivers is 'complete' the official conformance testing has already resulted in some bug fixes and additional areas to focus on improving.
That real life case study is yet another example of how an API and conformance tests built around that API result in better code and in a more consistent experience that isn't dependent upon a mono-culture implementation.
> I guess if all code written could be seen as an API, TDD would be great, but that's not the world I live in.
If not an "Application Programming Interface", isn't all code an Interface? There's input and there's output.
With Object Oriented programming, that there is an interface is more explicit (even if all you're doing is implementing objects that are already tested). There are function call argument (type) specifications (interfaces) whether it's functional or OO.
