> Cook's aim since becoming CEO has been reported to be building a culture of harmony, which meant "weeding out people with disagreeable personalities—people Jobs tolerated and even held close, like Forstall," although Apple Senior Director of Engineering Michael Lopp "believes that Apple's ability to innovate came from tension and disagreement." Steve Jobs was referred to as the "decider" who had the final say on products and features while he was CEO, reportedly keeping the "strong personalities at Apple in check by always casting the winning vote or by having the last word", so after Jobs' death many of these executive conflicts became public.
The tragedy of Apple, and perhaps Steve's biggest oversight, was his own irreplaceability. He failed to procure a suitable successor. Or perhaps there was not enough time. People are Culture. And Steve was a big part of it. The hopes of Apple living on without him are just that, hopes. He built Apple like an orchestra with himself as the conductor; when he left, the music didn’t fall apart immediately, but the score became safer, flatter, more repetitive.
I especially dislike the "let's make spotify, but on blockchain" approach the community has. They simply don't get that people won't switch over to their solution just because it's running ethereum blockchain.
Are you kidding? Who doesn't want an Uber for the Blockchain, where they can enter into a smart contract with their driver before getting into the vehicle?!
I've wanted that. Barring privacy, safety and quality concerns.
If it is possible in ETH to build smart financial contracts but also encode state into the "wallet", such that reputation was earned or lost, then they really might have a winning strategy.
There is no real reason why distributed Uber/Lyft shouldn't exist.
I want that. Then it would be truly peer-to-peer. Where intermediaries are needed, the services the intermediaries offer can be debundled so that there's competition for the various services, driving fees down and quality up.
Worked with RN for a year now, after 2 years of native iOS dev with Obj-C/Swift.
Declarative UI, hot loading, code reusability, modularity, etc. You name it. Because of all these I feel like a dinosaur whenever touching non-react code.
Native covers the parts where React is clunky - for example some unorthodox UI elements that can't be created with simple views and flexbox styling
Core functionality is there already and with time it's only expanding.
What size is the project? Trying to guesstimate if it's worth investigating using 3rd party vs. [google] cloud container builder - speed tradeoffs, convenience, friction etc. Cheers.
I am simply building a Python container with about ~15 dependencies installed via pip and some ~50 MB of static assets added to the container. The base image comes from Docker Hub (hosted on S3/AWS CF).
If the final destination of your Docker image is GCR, it is really fast. You're basically not waiting for your build box to start up. Based on my experience the build starts almost right away after you push to the source control system, whereas CI systems like TravisCI/CircleCI spend quite some time preparing the build env (i.e. container) and running some preliminary commands, collecting artifacts/logs etc. Google Container Builder is looks like it is designed to build containers (not to run tests) and it does that quite fast.
This is essentially what React Native has done for UI <~> Logic communication, allowing the latter (think iOS/Androind/Apple tv os/macOS etc.) to be replaced by any compute platform - even Compute Card in theory I think.
You're applying the same mental model to hardware which can be seen in the similarity of tools that can be enabled on top of such abstraction. Way to go!
The flexibility that emerges from decoupling our software and hardware solutions is a [recent] trend that will only gain on traction as more people become aware of it's implications to how we create solutions to technological problems.
How can we evangelize this better? From my experience it's complicated to communicate this idea well.
not sure if true, may be recency bias or the fact that I'm still young and inexperienced in many ways and lack historical background knowledge in tech
but migration of all this personal knowledge / context en masse is not convenient.
and i’m sure openai won’t make it easy to escape the little labyrinth they’re building for us