If Microsoft was really ambitious about building a product truly competing to the Macbook Pro, they would need to ship it with a radically different version of Windows.
Microsoft cannot just throw upgraded hardware after the Surface, and expect it to compete with the Macbook Pro. The Macbook Pro is not primarily popular due to Apple Silicon, but the combination of a focused user experience (although, Liquid Glass was a significant step-down) and high-end hardware.
I owe my whole fascination with programming from childhood to Visual Basic 6.
I was 11 and I could hardly read English, yet VB6 with the WYSIWYG-editor and an introductory book by my side was intuitive and rewarding enough for me to learn the basics of programming.
I think you might be underestimating how many potential customers are unwilling to buy from Tesla after Elon Musk decided to openly support the MAGA wing of republicans.
Not sure why that makes you more inclined to buy a Tesla or flip someone the bird?
Well, in many safety-critical industries (e.g. manufacturing of medicinal products) you actually need to maintain objective evidence of its validation.
I feel like the “investing in the customer” part always seems the case with HP. The products never work properly unless you are willing to pay them more money or live with the extreme amount of bloatware in their PCs.
Designing a prototype car for trials vs mass production are two different things entirely. Those lidar sensors will become far less intrusive once a car is designed for mass production.
Most likely, the existing Waymo cars have their LiDAR sensors equipped like that because they need to be maintained and swapped at a regular basis.
I think the value proposition is more than enough for mass adoption, once people realize they can work and commute at the same time.
It is a reflection of exactly that, but this completely dismissed all the risks:
- Maybe new ml-tech is invented that does not require as heavy equipment.
- Maybe AI does not grow as fast as expected.
- Maybe a competitor comes along and pricing comes under pressure.
- Maybe supply chain issues.
That needs some nuances. There are some processes that are just well-known by research to be standardized - like supply-chain, regardless if JIT-style or forecasted stockkeeping.
SAP does not need to touch the "unique" detailed processes that makes a company great, nor it's culture. But if you e.g. manufacture a product, the design process can still be relatively unique to your company, but most often, the manufacturing processes should follow the high-level blueprint of manufacturing companies.
That's neither feasible nor required. Copenhagen still has cars in city centre - personally I drive my bike 95% of the time, but sometimes I need to use my car. However, I much prefer my bike because it's faster, less troublesome, infrastructure is great and the exercise helps.
Create incentives for biking, but don't outlaw cars.
It is actually not only because Keto is calorie deficient, but also because it encourages ketogenic metabolism, which means that while you are calorie deficient you are more effective at burning fat. Compared with a standard calorie deficient diet, you have more stable energy levels throughout the day, because the body adapts to not getting carbs.
But the discussion of whether something is renewable is also a complex topic that is only true to some extent. Renewable energy sources (Wind and Solar) are technically not renewable - the production of the equipment uses raw resources that we (today) cannot renew indefinitely.
However, for both Nuclear and Solar/Wind energy we do know, that the energy sources are sufficiently abundant to sustain us almost indefinitely without us upsetting other ecological balances.
You could. You might even say it's difficult to make any project estimate without your plan being waterfall. Planning and execution are deliberately two very different things, and convincing the customer - or the steering committee of that - is key to a good product.
You don't have too, but it is very common to fall into the trap.
If working within a safety-critical industry and wanting to do Agile, typically you'll break down high-level requirements into sw requirements while you are developing, closing/formalizing the requirements just moments before freezing the code and technical file / design documentation.
It's a difficult thing to practice agile in such an industry, because it requires a lot of control over what the team is changing and working on, at all times, but it can be done with great benefits over waterfall as well.
The historical analogy in Microsoft is more correct than one might think. For Microsoft, it was a question of relinquishing control (e.g. going from proprietary to open) that helped them grow so much again. They are in many ways, a wholly different company than 20 years ago.
If Facebook could have embraced the mainstream interest in privacy and converted themselves to become a global digital identity provider, they could have become so much more and be on ethical side of history. Now they are almost pursuing both, while not realizing that they have to let go of one (and incur short-term losses) to pursue other.
Well it's anecdotal, but yes, our company fits directly into that space. You might ask why we don't want to just have the hardware in-house, but since we're developing Software as Medical Device products for iOS, we'd rather qualify Amazon as a critical supplier than try to operate the activity ourselves (with all the controls that come with doing so).
Microsoft cannot just throw upgraded hardware after the Surface, and expect it to compete with the Macbook Pro. The Macbook Pro is not primarily popular due to Apple Silicon, but the combination of a focused user experience (although, Liquid Glass was a significant step-down) and high-end hardware.