dan-0

In the same way as walking. Stick to well trafficed places you know and your risk drops significantly.

Ah, that makes sense.

My time as a digital forensic investigator was short and over a decade ago now, but it was standard where I was to put each phone in a faraday bag to help reduce concerns around remote wiping capabilities.

What's odd to me in this article is it doesn't seem like faraday bags are being used. I'd assume concerns over this type of thing are greater than ever now.

I called out my high value solely because I fall into the "privileged propagandist" rhetoric the comment I responded to and some other siblings are pushing.

Yes, the notion you need 300k to be comfortable anywhere is absurd, but just because someone makes more doesn't mean their desire to achieve a better quality of life is any less valid than anyone else. Do people with higher salaries need more? No. But why assume that just because an individual or group of people want a better quality of life they're "privileged?"

FTR, 100k as a average base salary is pretty low for tech in NYC. When the other 90k is bonus and RSUs that probably vest over 4 years, the stock has fluctuated 50%, and this being the journalism space, I wouldn't expect to see the full value. They have every right to try to negotiate better quality of life improvements out of NYT, especially for something as low impact on revenue as pet bereavement, as ridiculous as that is. I feel a lot of these comments don't understand tech compensation, where sometimes companies can't meet market value in cash so resort to all kinds of quirky benefits to attract/retain skilled workers. That is exactly where I see such a crazy request coming from when a company pushes back against giving more than a 2% annual raise.

Sorry, I don't see a valid point in any of these salary arguments. In fact, they're down right insulting and ignorant.

I did strenuous manual labor for next to nothing once upon a time. After about 8 years of that, on top of regular 60 hour work weeks, I spent almost every waking moment of 4-5 years to learn and better myself with about every sacrifice you could imagine short of divorce. I'm now making significantly more and working much less with an extremely happy family.

I'm not some trust fund kid. I have a high school education. My father worked 3-5 jobs to provide for my family growing up. So if you haven't picked it up, I know what the other side looks like.

I work in tech now, I wouldn't even reply to a recruiter presenting a 190k job offer if it meant living in New York. I can get more working remote. It's not because I'm spoiled, it's not because I make bad financial decisions, it's because I know my value and won't compromise and I sure won't reduce my family's quality of life because some multi million dollar company wants to short change me.

I get paid fairly for my experience and what I bring to the table, I make sure of that. If my employer isn't matching what I know I can get on the market, I will first negotiate (which is right where the NYT Tech workers are at), then leave for greener pastures if that falls through. I can do that because I worked hard to bring more value to myself in an in demand field.

I'm sorry if you're making a lower salary, but that doesn't mean everyone should just take what they're given. That's how people are exploited.

These arguments aren't just wrong. They are backwards and self limiting.

The opposite side of this is unpredictable or unintended behavior from too much moisture, which in my experience has been an acknowledgement with touch screens for quite some time.

As touch screens for applications started to become common, this naturally filtered into tactical and service work fields. There is an advantage in this as it allows a more compact interface that can change more easily based on what the user needs. However the down side is, in harsh fast paced environments where the user may be moving quickly and sweating, it's much harder to register intended user feedback to the interface.

The problem is not just if touch screens should be used, but also how they should be implemented. Especially on the side of general consumer electronics, like mobile phones, iOS and Android have built in interfaces for accessibility. In some cases you can get built in accessibility out of the box with very little effort, but the reality is, it takes a decent effort in most cases to get it right and users who need this behavior are not a heavy majority. This results in a deprioritization of accessibility in many mobile applications.

This gets much worse with more hardware centric devices like thermostats, ovens, refrigerators, etc which have a higher tendency to have user interfaces developed in house and lacking any accessibility. Compounding this problem, with the popularity of touch screen interfaces, and post COVID supply chain problems, many users who needed accessible functionally were (maybe still are) left without many options, likely either having to pay a heavy premium for something with usable accessibility features, but probably more realistically, just taking what they can get.

Modern technology makes accessibility easier than ever now, and enables accessibility in places that didn't previously exist, but the lack of willingness to implement accessible features on the part of some corporations is not just providing terrible accessibility, it's taking accessibility away from places where it previously existed.

Back to the flea market example, if that's the only market available, you can either abide by their policies or not, if not you can't sell.

The fact that Apple has made itself the only market available is what makes it anti-competitive. Even then you could argue that's what you bought on to when you opted into their currated ecosystem.

Apple and Google's customer reach is a direct result of them footing the effort to create a store and relationship with OEMs and currating the store in a way that works for the customers that use it.

If Google hadn't tightened the rope on the Play Store polices, it'd be a mess, just like it used to be and like some 3rd party stores are, not user friendly and full of low quality or malicious apps.

This doesn't change the core of the argument. Companies and customers have their free will. If a company doesn't serve quality products in their store, customers will leave, if they make their store too painful for other companies to host in, so will they. If you agree to a contract and don't follow that contract and get booted, that's in your.

If you want reach into Apple's customers, you have to buy in to the whole deal, doesn't make them right for being the only store for their ecosystem, but doesn't make you right for giving them the bird and crying foul when you violate the policies agreed upon.

I won't buy the argument for Android you're throwing out there. Publish to another store of you don't like the Play Store, I do. Google's store is their customers, and their customers to make policies to protect from bad apps. If another store was better, people would use it readily, and they have the open option to. That's why FDroid exists, don't like closed software, well it doesn't exist there, and the customer made that wants it uses it.

Bottom line, you sign a contract and agree to the policies, don't cry foul when you get bit for violating it, like anything else. You put yourself and your company at risk by not reading and understanding what you agreed to.

I agree to a degree, in that the policies are a lot to take in.

When your work poses a risk to the bottom line of another company, they have every right to be protective and implement the policies they feel will bring in more customers and money. If the store policies are too much for you to understand, that's on you for blindly adding to the risk of that company.

I'm speaking specifically from the Android side of things. People want to be on the Play Store and not FDroid or the many others because that's where the customers are, but you're free to use another store or distribute directly, which is not the case for iOS, particularly outside Europe. I do believe Apple is anti competitive in the US due to this, but it doesn't change the fact that you're your own victim for wanting to be in their store and not following the contact you agreed to. They take in the risk of hosting your app, you take on the risk and pain of dealing with their store policies.

It's no different than having a stall at a flea market, if they say you can have a stall, but have policies against selling certain items, and you sell them anyways, you can get the boot. If someone falsely accuses you of doing so and they suspend your stall while they investigate, then you come back the next week under a different name, don't be surprised about the result when they recognize you.

The process should be more accommodating of these situations, but if you're a developer you should know the policies and limitations of your deployment environment. If you don't and get bit by a policy violation, I feel bad for you, but it is still on you to know and your failure to own it.

Development isn't just slamming in code because Product wants a feature.

This is exactly what Google has been trying to clean up. The Play Store is much cleaner and safer now than it was 10 years ago.

Unfortunately small companies and independent devs take the brunt of the downside as their ability to get timely support is almost non existent. Big companies often have a Google rep they can reach back to.

That is the most human behavior imaginable. Something bad happens to you, it's now an emergency, so you try every avenue to address it simultaneously.

I don't know the Apple ecosystem much, but on Android, it's very well known that this is a quick way to get completely banned from the Play Store. I would imagine it's the same.on iOS.

I don't like that this is the way it's handled, but don't disagree with it either or it'd be a fast path to bypassing quality and compliance checks in the app stores.

Even if Apple was to globally allow 3rd party app stores, 3rd party stores would hit this problem at scale eventually.

That's not it, not what I said, and not what I meant. I didn't say anything about shooting in the dark.

You're not hunting deer in the dark. You're getting to your blind before sunrise or you could be recovering your deer in the dark from a day time shot.

I mean, yeah, but have you ever tried to follow a blood trail through thick brush in the dark?

I'm not fully disagreeing, but there's a distinction to be made. I can find my blind, my car, and maybe a carcass on a pristine forest floor on some pretty dark nights, but if that thing jumped into some greenbrier or other brush, good luck. It's hard enough seeing them in that stuff during the day, I've had multiple occasions where I walked by a thicket in the day only to see deer flush out after I'm past it.

Also, some people just can't see in the dark well, regardless of how well they see in the day.

It really is a complex subject with a lot of considerations going down to even very small geographic areas in some cases. Part of it is to avoid over hunting, part safety, part sportsmanship, part for state revenue, and part for whatever crazy law got lobbied (ie in Virginia in some places you couldn't, even still I think, hunt fox with a gun because horseback fox hunters lobbied local governments against it, or maybe less crazy in a historical context, blue laws still apply some places).

For over hunting you have concerns over what sex or age a deer may be, time of day (more vulnerable at night), time of year (you don't want to kill a doe while it's pregnant or taking care of a fawn), and of course total count/limit.

For safety. Night hunting can be pretty risky, some locales don't allow rifles due to how far the round can travel, some require a certain distance from homes, etc.

For sportsmanship and ethics, things get a little more weird, because you're potentially pitting morals against each other. It's it ok to spotlight and take down 10 deer at a time? Maybe if you purely hunt for food for your family and this was the one time of year you planned to do it, but that'd get taken advantage of quick broadly. Even weapons are hotly debated in the hunting community, bow and arrow seems fair due to having to be real close, but your chance of missing or worse, only wounding the animal, is significantly higher.

I could go on for a while on all the above, but from my understanding, your premise is generally the original intent of conservation laws. They were to create a baseline of how many deer are taken a year. What happens though is people find loopholes they exploit, leading to overly broad, complex, and sometimes conflicting laws created to counter the problem.

What's wild about this case is Pennsylvania seems to want to make it hard to recover a potentially suffering animal, where many states have laws to protect you in recovery of the deer so it doesn't die suffering or needlessly go to waste. Many states make the distinction between recovery and hunting and have laws that apply to each separately. Pennsylvania in this case seems draconian and counter intuitive, which is frankly unsurprising from what little I knew about their hunting laws before.

It's not wrong, but it's also a bit more nuanced if you're unfamiliar. Many state wildlife departments use this money to put it back into public parks and protecting more at risk wildlife. There are some species that continue to live purely because of these structures.

all under the, seemingly false, guise of enhanced security.

Maybe just me, but this became excruciatingly hard to read after this. At this point, I don't know what they're talking about, but they're implying something being done for security reasons is wrong without an understanding of the problem and it's already sounding like a rant.

That was before even mentioning the feature is adb, which yes, that is a security concern because you can bypass Android's security model. Why that's been open for so long in the first place is an even bigger story IMO.

Regardless these app and cache killer apps are at best barely useful and often scams. This functionality is handled by the OS on its own. And it should still be possible to kill apps and clear caches manually from the device settings if needed.

Oh come on. It definitely couldn't be that it's surveillance technology produced in a country known on a massive scale for stealing information via electronic means, especially against the US, right?

Your statement reflects little knowledge on US national defense matters, shows a lack of knowledge about the technology, ignores recent historical knowledge of China's hacking efforts against the US, and provides zero information to back up your claim.

This has been a litmus test for me over the years honestly. I tend to trust people much less if they speak in absolutes on complex topics.

Yes, it can make your argument more strong, but you're lying if it doesn't cover 100% of the cases for the subject. For the lay person, this might be fine, they don't know, but for anyone who knows the subject matter in depth, chances are you sound like an idiot.

I'd argue this mentality plays a good part in making some social media so toxic. People generally aren't going to read detailed explanations on a topic, so people who would write them have less incentive, meanwhile some pop star's 10 word tweet over simplifying some complex global crisis, like you can just make it go away overnight, will get a million likes.

This was interesting to me as well. I'm assuming the more limited IQ resulted in more of those soldiers falling into inherently more dangerous roles such as the Infantry due to inability to qualify for more technical and safer roles.

Why stop there? Why not just title it "Four Bombings in Europe?" You wouldn't want to give an unhealthy outlook toward Sweden when bombings happen elsewhere too.

But seriously and respectfully, my point being the title is not accurate to the article. "Residential bombing" is not a real description, it could be aerial bombings, it could be gas leaks, it could be terrorism, or something else.

Context is important. I'm not interested in random bombings. If a foreign nation is attacking Sweden, I want to know everything in real time. If it's an explosion due to a gas leak I'm probably not going to click in and read it, but maybe someone who is interested in public safety or that geographic area will. If it's gang violence, maybe someone with an interest in safety and law enforcement is interested.

"Residential bombing" doesn't tell me enough to make me want to understand it more, it _does_ sound like a gas leak, but I am interested in gang violence in Sweden because it's something I know very little about.

When I have a limited amount of time to read the news, I'm only going to prioritize articles that look like I'm going to get something out of it, I'm not going to read articles with vague headlines. To me that's click bait just like any other.

There's plenty of reasons to complain about the things Google does, but this isn't one. This failure is purely on the author.

1. Google had been mentioning this change for a while 2. Target SDK update is a big deal, especially if you don't know what legacy stuff the app was built on, and surprise, can impact OS versions differently. 3. The emulator is not a good gauge of reality. I get this for a constrained team, but if it didn't cross your mind to even think of if Samsung or some other manufacturer has issues, you're showing you've done little Android Dev. 4. Straight 100% rollout. WTF. The other three, I can see some very isolated reasons for not knowing, but you manually have to change the rollout from 20% to 100% when you release. You said nah, I'm 100% sure of this code I don't know and pushed it. 5. The issue was realized after the customer reported the issue, and was almost ignored. Author released the app and didn't bother to look at crash reporting in the console which would have a strong indicator if any fresh crashes. If you gave half a care, you'd have been all over this the day of a release.

I get it if you're a fresh web dev or something experimenting with Android, there will be surprises. And we can complain about Android backward compatibility and play store practices all day (I often do), but this isn't that. This was the mental equivalent of wanting to find out what lives in a hole in the forest by putting your hand in it first. Little to no thought of consequences or what a professional would do.

I don't care if you don't like mobile, you're telling someone you know mobile enough to maintain their apps. You don't. This is negligence to a degree I'd be worried about getting fired, if not also sued over.

This is part of the problem. You know your constraints, other people do not, but like to assume they do. So you end up having to write a defensive argument about your problem rather than just plainly asking your real question.

This may help less experienced engineers not understanding their problem set, but for a more experienced engineer it's absolutely obnoxious to think of all the ways to defend my question so I don't have to deal with a rush of "oh but you should do this instead" answers getting up voted that don't actually answer my question, then asking to accept the answer.

To one set of users it's possibly helpful, to another it's useless if not also condescending, often condescending to both sets.

The bottom line is now, SO is so filled with these types of responses, I can't expect to get a very specific question answered, which is really the only reason I'd ask a question in the first place, so why use it?

There are plenty chat groups now via Slack and discord in my field where I can get much more direct answers. People aren't worried about getting down voted for a bad question, people aren't giving low quality answers to boost their points. So for me, SO is practically dead except for the occasional obscure error message that I can query for there.

Maybe it's the fact that I have a lot of recruiter contacts on LinkedIn, or maybe it's my engineering field, but I disagree with a lot of the comments here. In the past #opentowork has been a huge help even up until I started my latest role in November. I've never had to be worried about finding a job except when I left government work for private sector.

The amount of recruiters that would reach out once I set myself to open to work was beneficially and notably more significant and I wouldn't have had nearly the number of opportunities presented if it wasn't for that.

I've done this both while still employed and after quitting a position without any noticable difference.

This is a tangent, but dropping resumes to companies directly has proven to be ridiculously time consuming and ineffective for a lot of reasons. If I can get a phone screen, which happens at a pretty decent rate with a recruiter that reaches out first, I've rarely had an issue getting to the next round. There's some pretty good opportunities I've been given just taking cold calls from recruiters, and #opentowork has played a big role in that.

FWIW, my strategy has been to apply to a few companies I want to work at directly, turn on open to work, take recruiter calls while I wait on the companies I initially targeted to respond. I'll focus ~75% of my effort on my targets and use everything else as a backup or opportunity to discover some companies I wasn't aware of.

When I was a hiring manager, the hashtag meant nothing to me. I'd ask everyone why they're leaving their current position and what they expect to accomplish at my company just the same. I'm not getting your performance review from your last company, so all I can go off of is what you tell me anyways. Maybe some references, but those are marginally reliable at best. If you're denying candidates based on a hashtag or profile flair like this you probably shouldn't be in that position, you're not assessing the candidate objectively.

I don't get the "desperate" signal some people are claiming this to be either. If you're looking for a job, why not face the large end of the funnel towards your input? I don't mean any offense, but just my internal take, it comes off as a pride thing to me where you think too highly of yourself to allow external help. It seems like a self limiting outlook with little upside.

That all said, I don't think the numbers in the article have any easily actionable significance. It's a great conversation piece and something to mull over, but there isn't enough information to draw real conclusions on especially given the social and economic changes over just the past few years.

"only eats meat he kills himself"

Not sure what you're trying to get at. He eats meat and wants to respect where it came from rather than grabbing a factory raised, killed, and processed McRib and not thinking about it.

That sounds like the right way to me if you're going to eat meat. Personally I think it's a bigger problem when someone doesn't know or care (especially if they don't want to know/care) how the meat ended up on their plate.

Do you truly believe that someone who would kill and butcher an animal is a threat to _you_?

Exactly this. Even if your demographic is the same as the chart, dropping 2% of users can be the difference between profit and destruction. Maybe it's margins that you'll save but keeping those users, possibly bad reviews, maybe market share over a competitor, there's plenty of reasons supporting older versions is not a definitive "waste."

Is it a pain to support old SDKs? Yep. But that doesn't make it inherently a waste of time to do so.

Teams is horrible, but not nearly as horrible as an argument equating use of Teams to the Holocaust. There's a very big difference between using an app to communicate if you want your job and murder.

Maybe it's just the segment I'm in, but I feel like Salesforce was hiring pretty hard up until recently. They wouldn't be the only company to go from a hiring spree to layoffs that quickly over the last quarter.

We really need to lock this absurdity down and increase severance requirements for large companies heavily. It's one thing to gamble risk for the company, it's something completely different to gamble employee livelihood when you're signaling job security by hiring.

How so? Remote attestation and other SafetyNet features are a product decision to use. If a company has an app that only allows itself to be run on a device with SafetyNet isn't that on them? Google doesn't force you to use it.

Keep in mind, not everyone here speaks English proficiently or primarily. Nuances in definitions can lead to widely different interpretations.

This was the single biggest "driver" to me moving to Mac from Linux. I had a really nice system that I built and used for work. I was working on a project with a 24 hour requirement, it was only an hour of work. I needed to update for a particular dependency, but decided to update everything and low and behold, my video output broke after the update. I made the deadline, but spent literally all day and night trying to get everything working and done. The next day after a long nap, I shelved what should have been a perfectly good piece of hardware and bought a Mac after using Linux for well over a decade.