Apple is dealing with COVID, just like everyone else. They are not at their best. However given the circumstances I think what they are doing (CSAM aside) is remarkably good.
Fair points, I would wager that those incentives would also motivate for devs to try their own dog food.
We have all been there, probably daily, at the “why the hell this thing is broken” and the task owner says “well, it works on my IDE debug safe mode isolated protected nothing can crash side, I had fixed it”. Not enough, build it, try it on device, make sure it works there THEN push the changes.
Any work I do certainly isn’t to the detriment of millions of people.When you start working for free maybe we’ll take your comment here seriously.
I found a lock screen bypass bug and spoke with Apple engineers and they didn't pay out a damn thing. Probably because I'm not a "researcher" professionally. But I was able to demonstrate it physically happening with a screen recording a couple years ago. I thought about going to MacRumors with it but decided against it because 1. I didn't want someone to figure out how to exploit it in the wild and 2. I didn't want to potentially lose my opportunity to get paid. I should've just gone to MacRumors with it.
Just in case you guys don't believe me, here is a video I made back in autumn 2018 where I actually recorded everything and was even going to post it to the site: http://aduke.co/EeR9Qb
Can’t agree more. The board and the entirety of senior management more than likely is the culprit of such horrible decision.There is no reason that the above can’t be solved. And at this point is only because of perceptual and cultural lag, possible arrogance, clear lack of CEO priority, and definite CFO cheapskatedness.
Because bughunters are people, and they need to survive. Plus people can’t share the same integrity and values. Lots of other reasons too. Economic incentive is by far the strongest force to drive something forward, not some moral high ground bs, not public safety etc.Why does this always gotta be a race somewhere? who has the biggest bounty...
Are you even a licensed Engineer? It’s literally like Engineering Ethics and Law 101 back in university.Wow, people get jumpy when you suggest they should be financially accountable for their performance... You do expect that someone can be fired for poor performance, right? If an engineer or team introduces too many security flaws into their code then that would be considered poor performance, right? So what's wrong with having a sliding scale between “we love you” and “you’re fired”— pay for performance.
You’d expect the best engineers to favor that model, wouldn’t you? You’ve never been fed up at a being dragged down as a team when you know full well who the problem is? I still remember the one where empty password boxes were being accepted by the OS-- if busting someone's chops for that bug meant losing some of the "brightest", then so be it.
No reason you need to start at the current pay level, if you merely want to account for the fact that an average engineer will always have bugs. Create a bonus pot that gets paid out to a researcher who finds a bug, or the team if none are found within a certain timeframe. The good teams with good engineers and processes get carrots, the teams without process or talent get sticks.
You might find engineering teams more willing to put up with more quality control if they know there's a pot of gold at the end of the flowchart.
Tort law? Are you suggesting it’s illegal to set up a financial structure to incentivize performance and encourage accountability for results?Are you even a licensed Engineer? It’s literally like Engineering Ethics and Law 101 back in university.
Bug is an inevitable part of software Engineering. Just like personale casualty is an inevitable part of a shooting war with a peer adversary.
Tort law is there, study it.
A very important part of enterprise building and Engineering practice is to make sure that you are not “blameable” or “personally liable”.
Just like every time you buy a plane ticket, you are paying dollars into the disaster recovery fund. That’s for if you crash and die, that pays for the PR and cost of liability.
There is a difference between a bitch-slap and an aggravated assault.Tort law? Are you suggesting it’s illegal to set up a financial structure to incentivize performance and encourage accountability for results?
When you say making sure you aren’t “blameable” is a very important part of engineering practice, you realize git literally has a blame command to determine who’s responsible for a bad line of code, right?
To be honest, I have no idea what you’re talking about here. Maybe you’ve misunderstood my point, or maybe you’re just very worried….There is a difference between a bitch-slap and an aggravated assault.
There is a difference between a sibling fight and a trial by combat.
I think you know the difference between the two “blames” in context.
As I said my Engineering degree is in Electrical, so it’s not just software and computers. I also deal with big voltage applications. When I screw up, either in embedded software or in control systems, or in, let’s say transformer design, a lot of people will die. So, I’m much more risk adverse and we are held to a much higher ethical and legal standard than a typical consumer electronics software programmer. But the idea is the same, a mistake or oversight that’s not going to be considered a tort can still result in a national security catastrophe or other major public interest issues. You and your company may be sued separately for billions of dollars in compensation or fines. Child protection is a big one, and a very big and inconspicuous hole 🕳.To be honest, I have no idea what you’re talking about here. Maybe you’ve misunderstood my point, or maybe you’re just very worried….
Seriously though, aggravated assault? Trial by combat? How bad is the code you’ve been writing??!
And what does any of this have to do with my proposal that Apple pay engineers less if they create more bugs?As I said my Engineering degree is in Electrical, so it’s not just software and computers. I also deal with big voltage applications. When I screw up, either in embedded software or in control systems, or in, let’s say transformer design, a lot of people will die. So, I’m much more risk adverse and we are held to a much higher ethical and legal standard than a typical consumer electronics software programmer. But the idea is the same, a mistake or oversight that’s not going to be considered a tort can still result in a national security catastrophe or other major public interest issues. You and your company may be sued separately for billions of dollars in compensation or fines. Child protection is a big one, and a very big and inconspicuous hole 🕳.
You want to make sure that everything you sign off as long as you are not being negligent by the official tort law definition, you are not liable, and it’s unforeseeable or act of god.
Software being used for military purposes in Iran or North Korea, etc. You are dead. All for a benign piece of code.
Haven’t you learnt in Engineering school? Protect yourself legally, or do nothing? Same with doctors.
I just told you if they are hiring real engineers that are trained to think like one, no one would take up that kind of offers. For a boot camp WebDev? Yes, maybe, probably, not either.And what does any of this have to do with my proposal that Apple pay engineers less if they create more bugs?
I just told you if they are hiring real engineers that’s trained to think like one, no one would take up that kind of offers. For a boot camp WebDev? Yes, maybe, probably, not either.
Also, in aviation, a hobby of mine, commercial pilots are allowed to do a “no fault” go-around. If they decide to fly around after on track for a tricky or failed landing, they don’t have to explain this to anyone, why?
Quite the opposite. Apples arrogance will just lead to white hat hackers becoming black hat hackers. If apple is to cumbersome to communicate with or not willing to compensate for my time checking the quality of their software. People will go to those who are more enthusiastic and shows me appreciation for the work I did. And believe me it’s a sellers market.Sounds like I struck a nerve.
I used to say that quality went downhill after Avie Tevanian left Apple. Things are mostly better now, but there are too many things that employees at Apple should see every day and be able to quantify and therefore, be able to be fixed. I wonder if people are too busy spending their money, commuting 3 hours to this area, or too high to care.This. This 1000%.
It boils my piss to be honest… the Adobe comparison is warranted.
There are a couple of quirks that I still see happening several OSs later, dragged from Catalina to Big Sur and still expecting it on Monterey. I’ll have to start with a 100% clean state machine to see if I have just tainted it crap… but nevertheless AirPods Pro/Max still stutter at random times, pausing and resuming with a ~2 seconds no sound period (when it gets audio it’s a bit delayed also), sometimes clicking from one app window to another is met with a lag (64GB 2020 iMac here), or alt tabbing sometimes pops up another window from another application (usually safari) invading the focus of the selected one. To name a few.
Don’t get me wrong, these are really minor in the grand scheme of things, it works, I dread every time I have to visit windows… but goddamnit Apple, finish the damn job, polish it, I don’t care about that new fancy unfinished drag and drop-y thing if some key stuff still has rough corners!
It’s even simpler! If you don’t like the way apple does it find critical flaws and sell them to nation state actors for far more money than apple is paying.It’s very simple. If you don’t like the way Apple does it then don’t find their bugs. Eventually there will be some bad exploits and Apple will start paying more for the good guys to find their flaws.
Windows 10 was stable with update 1909 until a couple of recent updates. The good thing is that none of the updates ate my drive and forced me to recover my drives.Windows 11 seems better than windows 10.
It kind of terrifies me that you’re saying “When I screw up […] a lot of people will die,” but don’t think maybe your bonus should be affected that year…
To each their own. Most of the truly excellent engineers I know prefer a system where competence is rewarded.
When I do my job, I operate as a licensed Professional Engineer vowed to fulfill "the Duty to Protect" under the "Code of Ethics",
To be honest, I forgot if the client is on the list, but I don't think so, as they are often the plaintiff. If they are, then, they must be below employer. The point of this is that first the public, second the profession.
- first to protect the public,
- second to protect the Engineering Profession,
- third to protect the employer
- fourth to protect self.
What we do our job, in terms of safety, has nothing to do with bonuses.
Bonuses are for creativity, innovation, patents, commission, and seniority.
Extortion? There are people own used car lots in small towns who could afford Apples yearly bounty expenses. This attitude is why Cellebrite can unlock any iPhone and NSO group can remotely hack any iphone via iMessage. These are just some of the exploits we know about thanks to these bug bounty hunters.Looks like the hackers are moving towards an extortion business model.
It’s tied to my (commercial) performance, but not quality of my work. The quality of my (Engineering) work is regulated by the state, and the profession, but not the company, at least not directly.I'm very impressed with your qualifications, the enormous responsibilities you have been entrusted with, and the apparent seriousness you apply to them. I'm sure your family is very proud. I still don't understand what this has to with the conversation at hand.
Let me break this down one step at a time. Are you saying your compensation should not be tied in any way to the quality of your work?