K.W.Jeter was writing Blade Runner 2 in the office next to our small video game company. We were working on the entirely forgettable Dark Fiber title which was only published in Japan for the NEC PC-98.
"It takes five years to become an overnight success" I heard a variation of this from a VC who invested in my startup in the 8Os. I had to use it on him when we went back to the well a few times for more funding.
I don’t understand what you mean by “we don’t know”? Are you saying tech entrepreneurs don’t know education? I agree with that. Or are you saying we don’t know what problem to solve?
My interpretation of “we don’t know” is that the space of possible instruction methods is huge, and we don’t know what works best. It is easy to think of it as a kind of optimization problem, but that line of thinking quickly runs into a bunch of practical obstacles: different people learn differently, studies with good experimental design take time and resources so it is slow to iterate, and good teaching seems to require deep insights into student motivations and incentives, aspects of teaching that are hard to quantify. We also don’t have great ways to measure outcomes; grades are weakly predictive of future success.
The best teachers seem to combine deep thinking about how to teach with intuition and charisma. The ingredients are hard to replicate.
I do think that this is a nut that we will eventually crack, but it is proving to be a very tough nut.
I’ll give him the benefit of the doubt and hope for the best.
My wife has been a high school math teacher for 25 years and has seen waves of tech luminaries give their visions of how tech will radically improve education and learning. She can’t point to any startup that has had a major impact in improving outcomes. I wish I could point her to something that really will have an impact in, or even out, of the classroom for her students.
That's not unique to tech startups. Almost nothing in terms of explicit methodology has any effect on education outcomes. The literature on education research is of abysmal quality too.
That is rough. I assume this is a web application?
I went through a previous thought experiment about what would happen when we moved a paid up front feature behind a subscription. This was the outcome I came to. Unless the user bought and installed a physical app, on the desktop, outside of an app store, they were going to get the rug pulled out from under them.
Ugh, that happened to me too. But instead of researching other apps and waiting for them to decide to go premium too, I built my own workout app. Been using it for a couple months now and it's working great, but the hassle of publishing it to the app store means that it will only ever be a solution for me and I can't share it with anyone.
I actually started with it as a PWA, but ended up rewriting it in react-native. I wanted a couple features (heart rate monitor, lock screen integration) that afaik don't work with PWAs.
That is terrible and I am glad someone broke ranks to inform you of the risk.
My wife had a very agressive triple-hit lymphoma and CAR-T was eventually suggested. Fortunately, the medical team was very honest about how hard it impacts your body, with very likely chance of death. My wife decided to do it, and it almost killed her. The team actually had to "shut down" the process, so she didn't benefit completely from the treatment. The suffering was pretty immense as well. She died a few months later regardless.
We are (were) both engineers and we did wonder how many might get streamrolled by the whole medical process, where you do get this odd combination of extreme indifference and optimistic exuberance.
Sorry for your loss, I feel your pain. Your wife was very brave to give it a shot and take the fight to the limit, and you should remember her courage and honor her memory and keep fighting till the end regardless of what hardships you encounter in life.
The treatment actually killed my dad. I may be wrong but it appears with the treatment there was a 30% chance of some recovery, 40% chance that it would at least stop the cancer growth, 30% chance that it had no impact. I guess you have to take that chance when you have no other option. I don't blame the hospital (which was terrible) or the treatment, it was the last card left. And our loved ones end up in the 30% statistic and maybe as another anecdote for the risks section, but we know what we they went through and we won't forget.
It was tough because my dad was suffering, but he still was active and had at least a few months left without the treatment and I know that at that point in his battle he did this treatment to keep fighting for us rather than for him, even though it was he who had to suffer through it. So I am going to honor his memory and keep fighting until the end as well.
In retrospect though, the company wasn't making a technology decision. They were making a decision between Jobs and Gassee. Jobs came with NeXT and Gassee came with Be.
I don't think the technology mattered that much in the large scale of things.
Yes and no. The core of the purchase decision was really based on the technology. Ellen Hancock (Apple's CTO at the time) actually did a decent analysis of BeOs and NeXTStep. She was actually against some aspects of the purchase, and was not in favor of Be. She was also not in favor of the NeXT kernel. It is painful to say as a Be employee at the time, but Be internals were fragile, some technologies were very shallow, the kernel was brittle and under constant churn and we had big problems with our decision to have a C++ API. Gil Amelio liked Steve and Steve did a good job selling both a vision and the NeXT technology. BeOs was a really cool demo that was getting pulled into the direction of a real OS but had a long, long way to go. There actually was a possibility that Apple could have also gotten the Be code, but the board didn't go for it. As it turned out, most of the primary BeOs developers ended up at Apple via Eazel. The ones that didn't ended up at Google via Danger Research/Android.
Thank you for the Be-related posts. Maybe, one day, you could write a more detailed report of it in a format made for longer articles. I would read it.
As a former Be employee who ended up at Apple by way of Eazel, there are two ways to answering your question about the UI direction; 1. If Apple did not acquire Be, Apple most likely would not be in business or would be a much different company. 2. Assuming Apple did survive, Steve Jobs used the industrial design language of Jony Ive for the look of Aqua. Bas Ording was the primary designer of this and was directed by Steve with daily updates. The further evolutions of brushed metal, skeumorphism, etc. were all directly driven by how Steve wanted things to look with minimal input from others. The current bland minimalist UX disaster (IMHO) would probably not have happened, because for all of his faults, Steve had very good attention to detail and was in general a good proxy for the user.
I worked on Finder/TimeMachine/Spotlight/iOS at Apple from 2000-2007. I worked closely with Bas Ording, Stephen Lemay, Marcel van Os, Imran Chaudry, Don Lindsey and Greg Christie. I have no experience with any of the designers who arrived in the post-Steve era. During my time, Jony Ive didn't figure prominently in the UI design, although echoes of his industrial design appeared in various ways in the graphic design of the widgets. Kevin Tiene and Scott Forstall had more influence for better or worse, extreme skeumorphism for example.
The UX group would present work to Steve J. every Thursday and Steve quickly passed judgement often harshly and without a lot of feedback, leading to even longer meetings afterward to try and determine course corrections. Steve J. and Bas were on the same wavelength and a lot of what Bas would show had been worked on directly with Steve before hand. Other things would be presented for the first time, and Steve could be pretty harsh. Don, Greg, Scott, Kevin would push back and get abused, but they took the abuse and could make in-roads.
Here is my snapshot of Stephen from the time. He presented the UI ideas for the intial tabbed window interface in Safari. He had multiple design ideas and Steve dismissed them quickly and harshly. Me recollection was that Steve said something like No, next, worse, next, even worse, next, no. Why don't you come back next week with something better. Stephen didn't push back, say much, just went ok and that was that. I think Greg was the team manager at the time and pushed Steve for more input and maybe got some. This was my general observation of how Stephen was over 20 years ago.
I am skeptical and doubtful about Stephen's ability to make a change unless he is facilitated greatly by someone else or has somehow changed drastically. The fact that he has been on the team while the general opinion of Apple UX quality has degraded to the current point of the Tahoe disaster is telling. Several team members paid dearly in emotional abuse under Steve and decided to leave rather than deal with the environment post Steve's death. Stephen is a SJ-era original and should have been able to push hard against what many of us perceive as very poor decisons. He either agreed with those decisions, or did not, and choose to go with the flow and enjoy the benefits of working at Apple. This is fine I guess. Many people are just fine going with the flow and not rocking the boat. It may be even easier when you have Apple-level comp and benefits.
My opinon; unless Stephen gets a very strong push from other forces, I don't see that he has the will or fortitude to make the changes that he himself has approved in one way or another. Who will push him? Tim Cook, Craig Federighi, Eddy Cue, Phil Schiller? The perceived mess of Tahoe happened on the watch of all of these Apple leaders.
I’m asking you to judge people’s state of mind here, which is near impossible, but please bear with me…
> Several team members paid dearly in emotional abuse under Steve and decided to leave rather than deal with the environment post Steve's death.
Normally during an event like this there is a change in culture as well which I think we have seen under Cook. So why did they assume that the abusive situation would continue? Jobs was generally known to be harsh to the point of abusive, but if the situation did not change on his death maybe the abuse was equal parts cultural rather than just from the CEO, so why not leave earlier?
This question is forcing me to do some deep thinking about my time there, which I haven't done is quite a awhile.
Some people left early, like Don Lindsay. Don was instrumental in bringing Aqua to life, along with Bas of course, and led the team up and through the release of Cheetah and more. This task wasn't easy at all. To me it seems like he was finally going to receive some reward of those hard years of work. But instead he chose to leave to go to Microsoft. This boggled my mind, as leaving to Microsoft to me seemed incomprehensible. Maybe Don had enough of the abuse? Maybe he was sick of the increasingly crowded commute? The daily visits from Steve pointing out every detail of the UI that bothered him? Did you know the UX designed many of the big banners and posters for the WWDC events. Steve didn't want any old graphic designer to do those, so Bas, Imran and others would work on them. Don had to deal with that too.
When Steve left to receive cancer treatment in 2004, he still had influence, Bertrand Serlet was running engineering, Jony Ive was focussed on industrial design. We were working on Tiger with the brushed metal interface and there was a lot of activity on that. Tim Cook was running the business, but Bas and others were keeping the ball rolling on the UX with remote input from Steve.
I wasn't around for the next two leaves of absence, the last one being final, but heard that things were becoming increasingly fractious with camps emerging around Tony Fadell, Scott Forstall, Jony Ive and general politcal unpleasantness as Tim Cook was given various ultimatums about "I won't work with this or that person." Everyone was trying to say that they represented the vision of Steve and somehow knew what would Steve do given any sitution. Geez, if we knew what Steve would do or wanted, there could have been a lot of really distressing confrontations avoided over the previous years.
This type of internal sniping didn't happen with Steve around, or if it did, it wasn't very effective. I think it would have gotten you fired. Tony Fadell pushed it to the limit with Steve and Scott. I remember someone once asking Steve about getting free lunch at Apple, like you could get at Google and they were told "If all you want is free lunch, then you should be working at Google."
For me, there was a certain amount of clarity that came from Steve's abusive behavior. It could wear you down on one level, but also brought focus and drive to getting things done. I think it was very unhealthy one one level and very exciting on another. There weren't endless meeting on calendars discussing minutia. It also meant that the obvious horrors of the Tahoe wouldn't happen. Steve himself would have grabbed the windows with different corner radii, stacked them up and excoriated whoever was responsible. Some of my work was called "real bottom of the barrel shit", "the worst he has ever seen" and told "this is not the way we do things at Apple." I assure you, what he was complaining about was nothing remotely close to what we are seeing in Tahoe.
The extent of my writings are here in HackerNews comments. I don't have the time or discipline of Andy to be able to sit down and write like he does. Maybe someday, but for now I am using the free time I have outside of work to make music and ride bikes as fast as I can.
The mess of Tahoe didn't just happen on the watch of Tim Cook, Craig Federighi, Eddy Cue, Phil Schiller, it happened because of them.
Tim Cook has no taste and no sense of quality. He merely counts beans really well. Craig Federighi is responsible for the most precipitous drop in Apple's software quality since the late 80s and early 90s. Eddy Cue is responsible for some of Apple's worst software (music, iCloud, services), and Phil Schiller… what exactly does he do again?
I still have friends who work there. Some of them came to Apple from Be or Eazel, and are still working on Finder, Safari, Dock, etc. A lot has changed and in my opinion not for the best. Compared to them, my time there was a flash in the pan. When I look at Safari, Finder and the general state of the UI, I am deeply saddened. I see a bizarre combination of stagnancy, gratuitious change and general aimlessness across the desktop and mobile. I also have a deep distrust of anyone who works at big company, let alone a big company on one component for a long amount of time. To me, it leads to a focus away from external customers and to becoming an expert at internal politics. I probably need counseling, but I loved the dictatorship of the Steve era. Yes, we can point to flaws like the Mac Cube or the hockey puck mouse, but I really appreciated someone just maniacally fixated on getting things done and cutting through the BS that I saw later on in jobs in big tech.
It would be nice if veterans of the post-Steve era would post on here. Maybe they are scared, bound by NDAs or could care less. Like I said, I need some mental health treatment about my time(s) at Apple I was there working on Final Cut Pro after Be, went to Eazel, and then rejoined Apple as part of Steve's mass hiring of Eazel employees at the behest of Andy Hertzfeld.
Production methodolgies for animated films have progressed massively since 1995 and Pixar may have not found the ideal process for the color grading of the digital to film step. Heck, they may not have color graded at all! This has been suggested. I agree that someone should know better than to just take a render and push it out as a digital release without paying attention to the result.
https://archive.org/details/DarkFiberWindowsMac/(WIN+MAC)%20...
We talked a lot but I resisted asking him to help with the plot of the game. I probably should have!