A different experience than Nikon F.

I didn't buy into Nikon Z as I have no need for it. I did but into Sony Mirrorless because I wanted the video features, which I know Sony has but Nikon "may or may not"

Nikon got itself into almost irrelevance.

In the "early" youtube era, "pro" creators were using Canon as it had far better suport for video than Nikon. Sony saw the writing on the wall and pivoted their Alpha line to focus more on video. TBF, Sony had far more experience in video than in photography. Practically everything you've seen on broadcast TV passed through some sort of Sony device at some point. They had to buy Minolta to get into the serious camera business. Then they took their video and cine expertise and put it on small consumer cameras.

This year I got myself a Sony system (a6700) after a decade with Nikon. I won't be selling my Nikon gear anytime soon but I have to admit Sony mirrorless is a different experience.

If Nikon can catch up with Sony for video it'll be interesting. But it will take at least 5 years so i'm not holding my breath.

Remember when DVDs had trailers and ADVERTISEMENTS, and players respected the PUA (Prohibited User Actions) that disabled fast forwarding?

Expect new generations of audio devices to respect Amazon's wishes of disabling certain buttons on your remote unless you pay extra.

And in a few years we'll get to the point of smart TVs with subject recognition and eye tracking cameras that will detect if you aren't looking at the screen when the ad is playing. You WILL look at the ad AND listen to it, or else you won't get your freemium content. They will give you the TV for free, though.

I am indeed addressing how things work, not how they would work if they were completely changed.

from my comment:

they will most likely add

why would you address "how things work" when i was very obviously speculating on how things would work?

You got it wrong, you wanted to correct me, and got called out like a fool. And instead of saying "oh, I thought it was about how it works now" or hey, just shutting the fuck up, you decided to double down on it.

the problem is that they will most likely add a mechanism for apps to detect (and refuse to run) if your device has this option enabled.

a lot of banking apps will refuse to run if you have a rooted phone, for example.

blocking sideloading effectively kills android app development. how are you going to test on real hardware if you can't sideload an app? makes no sense.

I've learned to try and look past the "harsh language" as often I work in international teams and none of us are native english speakers. The first thing you lose when speaking a different language is nuance. I've found that "jumping into a call" always makes the other party "nicer". Either they're just terrible at conveying their thoughts in words, or they are just too scared to "look you in the eye" and say "harsh" things.

That said, we had this one guy in the team who had to be removed because even though he performed well (and all of us did, since we're all senior devs), he was truly an asshole. Too many coworkers complained, and corporate decided he wasn't worth it. This guy's PR reviews where always ("WTF??? WHY?" and similar comments with nothing to add).

For a different client I'm "mentoring" this guy. I sat with him on a call. Showed everything he had to do. The thought process, the implementation, and even gave him a branch to start from. He spent two weeks and wasn't able to finish his task. I'm not going to waste time yelling at him or using harsh language. I just wrote my review to corporate and they will decide what to do with him. It's really not his fault, though. This company wants to prove they have a "Career path" in the company and he was "promoted" to programmer. He didn't know how to program. He could do small "chores" in code, but couldn't really come up with something on his own. But he didn't even make the effort of sitting down and watch a fucking youtube tutorial. He just asked ChatGPT for code.

It's like that meme: "Place/Place, Japan" but it's "Thing/Thing designed by Apple in California"

Feelings may not change the quality of coding but yelling doesn't make you a better coder either.

If you feel the urge to mistreat someone it just means you're a sociopath, not that you're particularly talented. there are plenty of people who are very talented and have the ability to express themselves without going off

btw, if you applaud such toxic behavior you're not only an asshole, you also don't want to recognize you are one.

"If you have problems with everyone, the problem isn't everyone, it's you".

In the end, the company had to remove one of the contractors for repeatedly using unnecessarily harsh language. He was tolerated by (slightly less) toxic coworkers but the rest of the team found this guy was not worth it.

The problem is that we're a senior team. everyone has a lot of experience. there is very little chance that you as an individual can contribute more than the people you're annoying. he got under enough people's skin that management decided his contributions weren't worth it.

if I can work exactly the same workload with a team of competent and nice people, and a team of competent assholes, why would I choose the second team?

being an asshole doesn't make you a better developer. it just makes you an asshole. there's already enough bullshit in everyday life.

I'm a software developer based in South America. And I often get to work with young developers from Europe. In general, the experience seems pretty OK with spanish and portuguese, and becomes worse the closer you get to central europe. The experience with south american devs has always been very positive.

I like to attribute the problem to sheltering first-world societies. People living in countries where kids don't learn at a young age (their teens and 20s) that words out of place do have physical consequences in real life. Down here most adults would have learned that responses such as Linus' that have too many uncalled for remarks usually come with loss of dental pieces.

It's my hypothesis, anyways, as of why south american developers are often careful in their wording, and people from, say, Germany, usually have very strong words. I often get PR comments with unnecessary adjectives and comments (which I also like to attribute to the fact that most people in the team aren't english natives, so they don't really understand the nuance of "This doesn't make any sense" when all they want to ask is to change one line.

Recently I got one of such reviews. The reviewer said "This doesn't make any sense, it's completely wrong because this and this and that". The PR had a React component with a "convenience prop" to specify the order of elements, but he wanted me to order the elements before passing to the component instead (alas, now instead of having a single prop that can do it in one line, you have to add 3 lines of code and make your outer component also concerned with ordering the elements).

Since of course I'm not there in person to look at them in the eye and ask them to repeat the same comments in person (which they are, oddly, not able to... not even in a call. for some reason everyone is a keyboard rambo but shits their pants on a video call), I responded to his comment:

"Thanks for your feedback, I'll be refactoring as suggested. Meanwhile, I have a suggestion for your comment: This doesn't seem to me like the correct way to implement this, as IMO it violates the open-close and single responsibility principle. I think you should order outside instead. Please refactor it this way so it follows the standards we've decided, or if you believe there's a good reason to do it your way, let's discuss it on a call".

way back in 256kbps ADSL days I was running an old 386 with two NE2000 clones booting from a floppy disk. running this: https://www.zelow.no/floppyfw/

In my experience, certain devs have a tendency to try to "refactor everything at every chance". And will introduce breaking API changes "it's difficult, but it's for the best" they justify. How changing one endpoint name "is for the best" is beyond me.

And don't get me started on the "new guy" that wants to change EVERYTHING. The client doesn't care how many lines of code you changed or how much nicer your architecture is this time around. They want a working system with bugs sorted out, not the latest version of this Javascript framework that came out 1 month ago and is on version 22.3 already (incompatible with 22.2)

"anti iMessage". grow up a little, would ya?

And really, no one really cares about this.

Latin America and a big chunk of Europe use Whatsapp
Asia uses Line
Russia and Eastern Europe use Telegram
China uses WeChat

Pretty much no one outside the US cares about the color of a message bubble.