I would love to use this for E2E testing. It would be great to make all my assertions with high level descriptions so tests are resilient to UI changes.
Seems similar to the Amazon Nova Act API which is still in research preview.
This coin is issued by Paxos. Paxos, by the way, hands down has the worst interview process of any company I've spoken to in my 30 years of working in engineering. So while I am rooting for regulated stable-coins as a technology, I have to admit some feelings of schadenfreude.
This was the beginning of an avalanche that led to most of the remaining engineers at Atari to leave and try to start their own third-party game companies to follow in the success of Activision.
Atari in 1983 went from the leader in video game production to completely imploding. In 1979, four of their best programmers left after demanding equity in the sales and were refused. Their CEO Ray Kassar famously said, "You’re no more important to those projects than the person on the assembly line who put them together. You’re a dime a dozen. You’re not unique. Anybody can do a cartridge.". They left and formed Activision which led to a sequence of failures by Atari until they finally died unable to compete with the likes of Intellivision, Colecovision, and Commodore.
The reason Apple doesn't do this is they want to make the AppStore a safe-place and a worry free experience. If anyone can run whatever they wanted for whatever length of time they want, then it opens the door for malicious apps to exist. It's a trade off between safety/experience and flexibility. For folks like my Dad, who I took away his PC and replaced with an iPad, it's been great. I just don't worry about malware, viruses, or trojans he might install on his iPad because the odds are he can't get into too much trouble.
I'm going to answer but I should preface by saying I'm not going to try to proselytize you to Swift. If it doesn't work for you and you're happy with Objective-C, then by all means do what makes you happy and keeps you productive. I have a couple of apps that have about 50k lines of Swift, one also with 60k lines of Objective-C and another with 40k lines of Objective-C. We use MVVM as well as a fairly involved mechanism of VM abstraction with intercommunication using RAC. Common code is in a cocoapod as well as other third-party dependencies otherwise the other target is the iOS app itself. I think LOC is a poor metric to measure complexity, but it does have a relevance to compile time. Others have also said that Swift and Xcode are not perfect, but as an engineer programming in Swift makes me quite happy.
I hear this argument a lot that it's not production ready but my personal experience does not agree. I use Swift in production for several apps with relatively large codebases that sustain many hundreds of thousands of sessions per day. I would agree that a full clean/rebuild is not as fast as Objective-C and that the incremental build system sometimes seem as though it is compiling more files than you'd like. However, for most part the incremental build system is fine and in daily use it is not a problem. I could never imagine going back to writing objective-C again when I compare the net gains we've realized coding in Swift. The readability and succinctness of the language, as well as catching bugs at compile-time rather than run-time, is a huge benefit. Value-based programming, functional(-ish) programming, and protocol extensions have made my code so much easier to maintain and test, as well.
Similarly, the number of git-commits is also a poor judge of how much work was done. When CI builds automatically build release notes based off of the git-log since the last successful build, this can be deceiving.
Are the founders legally obligated to return the $6MM they took off the table or is it a moral obligation? (Or is there no obligation whatsoever) And if it is a moral obligation, what would incentivize them to do so - is it to save their reputation in the future?
I've used voice authentication with Nuance's SDK before and having a cold or gaining weight does not affect the verification process. It is based on acoustioc signatures in your voice and not necessarily a precise recreation of the original recording. This isn't a problem with this approach.
C syntax really isn't that hard to understand, it has persisted for a reason, and I am quite happy when I get to write C. It's not the ideal language for web-programming but it is certainly the right language for a lot of things. Statements like "good programmers who know or knew C at one point don't use C in their projects and will never contribute to open source projects written in C" are just unsubstantiated fabrications.
It is worth noting that Xsser only affected jail-broken phones so the point of the article, that Apple's "closed-ness" was to fault here, is a factual error. In fact, it is that very closed-ness that prevents these types of software off of the AppStore.
I was experiencing the GPU panics as well and it turned out to be a hardware issue. Did it only happen when you were using the NVidia GPU and not when using the on-board?
I was just at the keynote in NYC. I didn't hear them mention anything about allowing you to edit files in the browser. The only thing I saw demonstrated was preview of documents with comments collaboration but no create/update functionality. It felt like a read-only version of Google docs with commenting.
It's a timing trick to get past it! This scene mirror reverses so you may need to invert left/right but the solution is that once you've gone left-right and then jumped forward you'll have to do something like left-right-left-<press right again IMMEDIATELY after pressing left before the animation stops>. Then a final forward, then sword. Then you go on.
Dragon's Lair and Space Ace are both on iOS AppStore. Space Ace was a much easier game to beat in the arcades but I never got far on Dragon's Lair. Now, thanks to the mobile app, I can finish the game while my son watches on - amazed at my dexterity. A so the torch is passed.
When I graduated from college, it was 1994. Most people who were making good money at the time were Unix C programmers so that's what I did out of school. Honestly, I felt more ageism because I was young at the time (contrary to this article) than than I ever do now as a 40+. I was getting paid a relatively low salary and was expected to work insane hours. My accountant friends were probably making more money out of school. So, I wouldn't say it was harder to find a job then, but it was harder to find something cool or interesting than it is now.
I also think I wrote kind of silly code then. I always laugh when I think about a persistent hash table I had to write and how I went out of my way to find prime numbers for M slots using Fermat's Simple Theorem (not his last theorem) and testing for Carmichael numbers. Of course, there aren't that many prime numbers in the first place and a static table would have worked just fine! I always remember this as part of my evolution from an inexperienced academic kid solving a problem that doesn't need solving vs. experience to know where to comprimise and just get it done.
Even then, I knew it was important to start specializing where the needs were evolving, which was win32 programming at the time and eventually Windows MFC programming. This all dove-tailed nicely years later when I started working on the Playstation 3, where you develop in MS DevStudio but the PS3 was essentially a Unix box. It's funny how things work out.
The only thing that sucks about being a 40+ engineer is when I say "whachoo talkin' bout Willis" or "it's tricky to rock a rhyme", half the people don't know what I'm talking about.
I'm a 40+ engineer in the NYC metro area and I've never felt more in-demand in my life! I think it boils down to a simple idea: computer-science is a dynamic field and THE FUN PART is that you need to always be learning.
There are still some colleagues my age who still wax about the days of writing JCL for their mainframe jobs and never evolved past the 80's and perhaps they gave a bad name for others who built on their of years of experience with evolving knowledge.
I decided in 2009 to specialize in mobile, when I realized how impossible it was for the startup I was working for to find any high throughput engineers, let alone high throughput engineers with niche expertise in mobile. I think it is an advantage in some ways during interviews that I can talk about decades of awesome projects I worked on while also being among the first to ship an iPhone app or a top ranking iPad app.
As they say, luck is when preparation meets opportunity. It's my job to make myself lucky.
This promotion is of course targeted toward writers but how amazing would it be to have 2-5 focused days to hack while on the train? Perhaps mobile connectivity would be an issue in some locations but the upside of the focus-time would probably be greatly productive. A train hack-a-thon.
For live demos, I use Airplay to mirror the display to an AppleTV. For online demos, I use an app like AirServer or Reflector that make my laptop an Airplay-receiver and then share my desktop/screen over G+ hangout.
I highly recommend adding the "Fingertips" Cocoapod to your project and it will highlight finger presses and taps when it detects you are using an external display. You just need to replace your UIWindow with MBFingerTipWindow.