Isn't it though? It's the "password" to the secure enclave which then provides a "password" to the OS.
Edit: I agree with your statement that "a password is something i can change if it gets compromised. a password is secure from others." Which is why I like that there is a method for disabling TouchID/FaceID with iOS 11.
Thanks for being so open to sharing. Do you have a blog? How do I find your blog? Before you posted this comment how would I even know to look you up.
Just because someone on the internet had a particular setup doesn't mean I want to follow it. Or that I have time to track down several people's opinions.
Getting install stats directly from the homebrew project, which I know because I use it, is infinitely more useful to me and much more easily discoverable. that's just my opinion though and you're entitled to your own.
+1 Though I do leave the occasional TODO or FIXME comment in code I prefer using deprecation attributes so that it results in a compiler warning. I spend a lot of time in Xcode so for me I like that autocomplete shows the method with a strikethru and the compiler warning is highlighted inline. It becomes glaringly obvious to everyone that we're adding to the technical debt by using the API.
Actually that's (almost) exactly how I did it joining Apple. I had already interviewed and been turned down with the group I wanted to join twice. Now I was coming in for another interview with a different hiring manager. I was willing to put up with another possible rejection because I really wanted to work at Apple. So I worked with one of the recruiters and had setup interviews with 6 other groups. I did 2-3 interviews a week and it was grueling but in the end I had several groups that wanted to hire me including the original team I wanted to join. They could only make one offer but nothing stopped me from interviewing until I was blue in the face.
EDIT: Another note, at least three of the roles I interviewed for had homework assignments. None took longer than 2 hours and I actually enjoyed them and the subsequent interviews much better.
The title is misleading. Looking at the About Us section it appears that only the CEO/Founder worked at Apple.
It's nice to see a new entrant into the industry none the less though. Interesting idea to use audio detection but I'm a little surprised it didn't include a PIR sensor for motion as well. Would be curious if there's an eventual platform play here.
Can you elaborate on how static library support is a hard requirement for your workflow and why frameworks (LLVM modules) don't meet your needs. I'm genuinely curious as I haven't had a chance to do any real work in Swift yet.
I feel there's an important amount of context left out for anyone to give you sound advice. Do you have a wife/husband? Children? Ages? Any other commitments? A mortgage, car payments, other debt? What fields have you been in? Then, there's the personal side. What's on your bucket list? Could you earn half of what you're used to and live comfortably along with any dependents you may have?
Also, what's wrong with management? For that matter, what's wrong with being bored or confused? It seems like you have a certain sense of urgency for change, but is work where change is most required in your life?
What do you want? If nothing, then at least learn to be content. This is not advice, just me repeating what I often find myself contemplating.
I literally write more than 90% of all code away from the office. People walking by, random questions/discussions, pointless meetings that make people feel like they accomplished something even though they didn't or someone just wanting to burn a few minutes. Office hours are the least effective and unproductive hours of my day and so I've avoided being there as much as possible because I'd rather show features more than showing face.
There are some big picture, architectural design discussions covering many interrelated components that can benefit form in-person meetings but those kind of meetings are the exception and not the norm in my experience.
This was my first thought and I actually looked to see if it was a gag site. Otherwise I agree with other comments that it needs to be a CLI tool to become truly useful for me.
Negotiate for an extra $100M worth of acquiring company stock, a permanent seat on the board, and the $10M cash now. Oh yeah and a reserved double-wide parking spot near the front door for my brand new Aston Martin. If I'm gonna dream, might as well go big.
I agree. I was a little thrown off by the quick link to being racially insensitive. I figured he just left out a lot of context. It was also a little strange that something like that wasn't disclosed by his significant other (they were engaged) before meeting.
The first thing that really came to mind was why did it matter what race the soon to be father-in-law was. If I was caught in that situation I would've quickly asked "by choice or just bad luck?". Then either politely ask if I may inquire as to what inspired them to choose to be unemployed or sympathize with their situation.
Either way I think if your genuinely interested in a person you find ways to move on in a conversation. In every relationship, whether new or old, you're bound to come across some uncomfortable situations but you just keep moving along.
Though I do like his other question more. It seems like it would lead to revealing the things the person enjoys most.
self in that context would be the class. The issue he was facing is that in subclasses, "self", would refer to a different class and therefore the lock wouldn't apply. What he's pointing out is that he resolved that issue by specifying the superclass explicitly.
Personally, if I had to ensure synchronous calls to a class variable, I'd prefer to just restrict calls like this to a specific queue using dispatch_sync().
You obviously didn't read the article. This isn't an issue of someone losing their password and subsequently being locked out of their account --- something that Apple would help with. It was mom's iPad. She died. They don't have the pass code and/or iCloud password and Apple won't help them open that up. Sounds fair or unfair depending on your personal beliefs.
Having said that the article is a non-sensible emotional plea for sympathy at the expense of painting Apple as a cold-hearted villain. If they just want to be able to make use of the iPad it's simple to restore it using iTunes.
It doesn't really matter what the language is, SQL injection vulnerabilities are serious in any language. A competent web developer understands that -- especially a "Programmer Extraordinaire".