The main thing you’ll learn is that actually the static and inflexible abstractions of an operating system do a lot to protect the system integrity and prevent everything from blowing up. Many smalltalk VMs rely on recovery features for a reason
recovery features? how do they work? and what smalltalk runtime do you have in mind? I still have a very vague understanding on how changes could be applied to a production running images, or if there is one and preferable way to do that.
What do you mean for the sake of Apple? This didn't benefit Apple. He screwed with this guy for months because of a mistaken idea that the guy should have somehow known Apple's attitude towards secrecy without being told, and after months of messing him about sent him back the signed contract the second he had given up. There was no benefit to Apple here. In fact he harmed Apple by limiting their music collection in the initial stages. It's also not on the limits of ethics. It's unethical.
> should have somehow known Apple's attitude towards secrecy
I have to assume you and the author (at that time) aren't familiar enough with the corporate world to realize all discussions containing privileged information (contract details that would never get a press release) are confidential by default.
Of course Apple would never think they'd have to explain this. It's a reasonable expectation for them to have.
I work in the corporate world, I have detailed confidential discussions about technical details of upcoming products and contract details. The first thing we do in those situations is we all sign NDAs. The idea that you'd do a presentation to a hundred people and expect that information to stay confidential without specifically informing them is just absurd. Which is part of the reason Jobs just screwed him around rather than doing what you're meant to do - get the person to sign an NDA and then sue them if they break it.
I don't doubt you, but my experience is different.
Every company I've worked for (mostly F500s) has had an onboarding document you sign in which you're notified that everything inside the company is confidential by default. It doesn't expire.
Most of these companies also had annual training (the usual corporate policy refresher stuff) and this was mentioned during that as well.
I've worked on some very hush-hush projects. In my experience, NDAs were for people outside the corporation...partners, vendors, etc. Everyone who was employed by the corporation was under an NDA by default. I don't think I've ever signed a subsequent NDA for something my employer was working on, because I was already under one.
And even if they didn't do all this formally...it's a reasonable expectation. I would never think I'm allowed to discuss anything that wasn't publicly announced with outsiders.
Pricing details in contracts are trade secrets. You don't even need an NDA to sue someone for leaking that.
They're lucky Apple found a quick remediation. They delayed signing the contract because they had to wait and see if any damage was caused. Next steps would have been renegotiating or lawsuit.
lol, if you don’t put an NDA (or otherwise make it clear it’s a trade secret and try to protect it), you lose the protection the moment you start sending that out. Including in contracts.
You mean on the limits of being sued for. Coz this man had zero ethics anywhere in his life unless "being ethical" was somehow correlated with also making money
> coding was never the main goal, it was always the means to create the finished end product
I think that's the main difference. For many of us, the process and how we grow through that process really is as important as, if not more important than, the result
Also, not having to deal with the kind of assholes that are capable of both setting up and maintaining your physical infrastructure and are willing to travel on a moments notice to put out fires. Worth the price of AWS just to not have that dysfunctional lot to deal with.
“Relatively safe to” is a very official sounding rubric. I guess tell him that and see if you agree on the timing of when that safety threshold has been met.
Telling your kid to not drink beer is giving them the courage to say no to drinking beer. I personally don’t just bark out rules with no context. I also have discussions with my kid about why drinking beer can go awry. We all expect that they will, likely before we’d feel it’s relatively safe. So I want him to at least know what’s in store and how to not make compounding mistakes.
Overall, DB Regio (the regional trains which are covered by the Deutschlandticket) has around a 89% punctuality score[1], which is very comparable to the Dutch numbers. There are certain hotspot regions though where the regional trains are truly fucked, but for most of the country they're totally fine and quite reliable.
It's mostly Germany's long-distance high-speed ICE trains which have punctuality problems (the much discussed 60% punctuality [2] score), but those are not covered by the Deutschland ticket, and the Netherlands has no comparable service to these trains anyways, so if one is envious of the state of Dutch trains, they can happily pretend that German ICE trains simply don't exist. In my experience though, the ICE's are a pleasure to ride.
Sidenote, but the ICE punctuality score is not really directly comparable with the Regional train scores, since they measure different things. The ICE score is about the passenger arriving at their final destination with less than a 15 minute delay including connections, whereas with the regional trains they don't have granular passenger level data, so they measure whether or not a train gets to the platform within 6 minutes of the scheduled time.
The Netherlands runs around 3000 trains a day vs. 50k in Germany. That doesn't excuse Germany's problems which were also predicted years in advance when they stopped investing in maintenance and infrastructure but also shows that the comparison is not entirely fair.
reply