smb big sur

Enterprises are made up of individual people.- When you're building solutions, keep in mind that you're building your tools for peoples' benefit.Workflow strategiesTake advantage of strengthsUse the right tool for the job you're working onIf all you have is a hammer, all your problems look like nails.In reality, only part of the problems you're trying to solve will be nails.Make your workflow modularDesign your workflows so that different modules are being connected together to do the job.Enable repurposing, adaptation and expansion.Code re-use is a good thing.Optimize your workflowProblems will always appear in a enterprise workflow. Anticipate the issues and optimize your automated solution's workflowsEliminate bottlenecksReduce repetitionRemove complexity / confusionDesign your workflows for your usersPeople will avoid complex solutions, they won't like using them if they're hard to understand or operate.People will use convenient solutions, all the time.Pursue inclusionSuccess uses AND (inclusion) conditi

I had a posting in the older forums about this issue. I never really found a solution. Maybe I can try posting again and see if anyone has some good advice.I am a big fan of TDD. One of the techniques I picked up was dependency-injection. Objective-C is a very laid-back language when it comes to type-checking. It is very easy for the compiler to let you swap a test-double class for a production class. I am having a problem in Swift that you might be able to help with.class ChildClass { } class ParentClass { func child() -> ChildClass { return ChildClass() } } protocol ChildProtocol { } extension ChildClass: ChildProtocol { } protocol ParentProtocol { func child() -> ChildProtocol } extension ParentClass: ParentProtocol { }This code is failing to build. Swift does not believe that ParentClass can conform to ParentProtocol. This is a contrived example. I will show you a real example where I would use this pattern in a real app.import Foundation protocol SessionTaskType { } extension NSURLSessionD

It is a very common technique to create generic recursive closures in swift, like that demonstrated in WWDC2014 Advanced Swift Session.But somehow I find it is very possibile to create a Strong Reference Cycle with it.Here is the simple code. I used the foo function scope to simulate life cycle, beyond which all objects are supposed to dealloc.class Nested { func print() { println(Print Nested) } deinit { println(Nested dealloc) } } typealias ClosureType = Int -> Int func foo() { var myClosure : ClosureType = { value in value } func setClosure() { var date = Nested() myClosure = { input in date.print() return input <= 1 ? 1 : input + myClosure(input - 1) } } // do something setClosure() println(myClosure(5)) } // test it foo()the output didn't include the deinit stringI think it is because myClosure is capturing itself. It is not a very big memory leak until some extra objects are involved (like that Nested object which may contain very large amount of objects).The problem is when I no longer n

I've found the session Optimizing Your App for Multitasking on iPad in iOS 9 really interesting.Thanks to a Carmack quote in 2011 I started to know about memory mapping in iOS, but I've never found a concrete example about how to achieve or where to apply that.The session comes whitout a sample code or playground file and is a pitty because I'd like to recreate a sort of a scenario to profile.Back into 2013 out of curiosity I wrote this answer on stack overflow about how to memory map big images, I never had a clear reply.Since the session talks about memory map sets of images whithout impact the RAM I'm not getting if I didn't understand some base concept or what I was doing wrong.I've test memory map with these simple lines of codes, but profililing with allocation I always saw the image allocated in RAM as dirty and crashes on real device due to the huge size of the image.NSError * __autoreleasing error = nil; NSData * mappedData = [NSData dataWithContentsOfFile:[[NSBundle mainBundle] pathForResou