Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Softwar

Softwar

An Intimate Portrait of Larry Ellison and Oracle
Oracle’s new order system halts sales for fourteen days; the founder must confront what went wrong.
by Matthew Symonds 2003 528 pages
3.78
499 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Bet on the architecture, not the gadget that makes it easy to explain.

Ellison saw the deeper shift. In 1995, while the industry celebrated Windows PCs, he argued that software and data should move from thousands of desktops to network servers. His proposed Network Computer, a cheap terminal for reaching those services, failed: falling PC prices and slow dial-up connections made it unnecessary and impractical. But the underlying move toward Internet-based applications proved far more durable. Users kept their PCs, yet increasingly used them as gateways to software running elsewhere.

Separate principle from packaging. Oracle gained attention by selling a simple device story, but its strategic advantage came from anticipating how the Internet could expand database use and enterprise computing. The episode shows that a forecast can be directionally right while its most visible product is wrong.

Analysis

What's striking is the distinction between a platform shift and its first interface. The Network Computer was a prediction about where computation belonged, dressed up as a particular box. Technology history often rewards the underlying change while discarding the original form: the useful question is not whether a prototype wins, but which problem it revealed. Still, Ellison's confidence that the Internet represented the final architecture was much stronger than the evidence justified. Strategic conviction can mobilize an organization, but claims of technological finality are especially prone to aging badly.

Reduce complexity by unifying information, not by adding more integration glue.

Fragmentation made Oracle blind. Before its internal systems were consolidated, Oracle had about seventy human-resources databases, 130 accounting databases, and 400 customer databases. Simple questions, such as how many employees the company had or how many new customers it had gained, required reconciling separate records, formats, and identifiers. The problem was not merely redundant computing expense. Different groups could not reliably see or share the same facts.

Put information at the center. Ellison's proposed answer was a shared data model: applications for sales, accounting, service, and other work would use the same definitions and records. That contrasts with best-of-breed systems, where separate vendors supply specialized applications that must be connected after purchase. A shared foundation could make updates, analysis, and coordination less fragile.

Analysis

This is an organizational argument disguised as database design. A shared record can reduce the reconciliation work that otherwise consumes time and undermines decisions. The same principle appears in supply chains and public administration, where inconsistent identifiers make collaboration harder than the technology itself. Centralization, however, is not automatically simplicity. A common system can become a single point of failure, a security risk, or a bottleneck for local needs. The value depends on good governance, dependable infrastructure, and clear rules about who may change shared information.

Change the business process before customizing the software.

The 80 percent solution. Ellison argued that companies should first standardize how work gets done, then use an integrated software suite with minimal code changes. His practical claim was that a working system delivering most of the desired benefit is preferable to a supposedly perfect system that takes years and costly consultants to finish.

Hungary made the argument concrete. At a new GE turbine factory, managers and consultants began designing elaborate financial controls that disrupted manufacturing. Plant leader Craig Kipp saw that junior specialists were shaping the whole business around local preferences. He pushed senior managers to simplify the process and follow the software's standard setup. The system went live in about five months. When GE later identified a useful gap, Oracle could add the feature to a future release, rather than leave the factory with unsupported custom code.

Analysis

Standardization can expose waste that organizations mistake for uniqueness. It also makes future upgrades and comparisons easier, much as common standards enable reliable coordination in manufacturing. Yet software defaults are not neutral: they encode assumptions about which processes matter and whose work should adapt. A sound implementation needs a disciplined exception process, especially for legal, safety, or customer requirements. The useful challenge is to demand reasons for variation, not to treat every local difference as stupidity.

Ambitious growth without independent controls can nearly kill the company.

Oracle's first near-death crisis was managerial. Ellison urged the young company to keep doubling revenue. Sales leaders gained broad autonomy, including influence over contracts and revenue reporting, while a qualified finance function was missing. Teams offered steep discounts, booked questionable deals, and sold licenses customers might not need for years. By 1990, receivables had reached $468 million on revenue of $971 million, and the company was close to its borrowing limits.

The cost was existential. Oracle reported a $36 million loss, its stock fell to $4.88, and employees feared that the company might not survive. Ellison accepted responsibility for what he called managerial abdication: he had focused on products and ignored controls because accounting and sales bored him. The recovery required a professional CFO, central oversight, and a more realistic grip on cash.

Analysis

The episode resembles a classic principal-agent failure: leaders rewarded for growth can shift risk onto the organization, particularly when the people validating their deals lack independence. Rapid expansion does not make controls a bureaucratic luxury; it makes them more valuable because errors compound faster. Ellison's technological focus helped create a strong product, but product quality could not protect the company from cash-flow failure. The case also cautions against treating founder intuition as a substitute for governance, even when the founder is unusually capable.

Delegate authority clearly, before successful deputies become competing centers of power.

Ray Lane helped rebuild Oracle. Hired after the crisis, he professionalized U.S. sales, improved customer service, and helped grow consulting from about 200 people to 17,000. His strengths complemented Ellison's: Lane handled customers and operations while Ellison focused on engineering. But the arrangement blurred decision rights, especially over applications, where Lane and development chief Ron Wohl disagreed about products and strategy.

The partnership unraveled. Ellison first gave Lane broad responsibility, then gradually moved departments away from him while rebuilding his own role. Lane viewed this as a loss of trust; Ellison saw Lane's challenges as encroachment on product decisions. In 2000, Ellison asked him to leave. Their split shows that delegation is not a permanent handoff: executives need explicit ownership of decisions and a candid way to resolve disagreements before authority becomes personal.

Analysis

Complementary executives can create more capacity than a single leader, but only if they share a workable model of who decides what. Ambiguity may feel flexible during a growth phase, then become dangerous when strategy and execution collide. Research on teams consistently points to role clarity as a condition for productive disagreement: dissent is useful when it concerns the decision, not the legitimacy of the people making it. Ellison's error was not simply trusting Lane too much or too little; it was allowing their operating contract to remain implicit.

Make your own company the first serious customer for major software.

Oracle shipped too soon. Release 11i, the E-Business Suite, combined a vast set of Internet-oriented business applications. Oracle sold it to customers before running the complete product itself. The new order-management system, central to recording and processing sales, had not been adequately tested in ordinary operating conditions. Early users encountered bugs, delayed implementations, and a flood of patches.

Oracle learned through its own outage. At the end of 2000, the company moved its operations onto the new order system in a large-scale internal deployment. It could not place orders for fourteen days. Ellison later described releasing 11i first to customers as a mistake and said he should have delayed the launch by several months. Internal use did not eliminate risk, but it could have exposed severe defects before customers carried the cost.

Analysis

Using a product internally is a powerful form of dogfooding, but the lesson goes beyond public relations. It forces developers to face real workflows, support burdens, and failure modes that controlled demonstrations can hide. A staged rollout also limits the blast radius when assumptions prove wrong. Internal testing is not sufficient on its own: a software maker's processes may differ from customers' operations, and employees may receive unusually intensive support. It is best treated as a necessary test, not a guarantee.

Prove efficiency with operational results, while being exact about what caused them.

Oracle became its own test bed. The company replaced 97 local email systems with one global service, cut the cost of email to roughly one tenth, and consolidated thousands of servers and dozens of data centers. It also centralized processes such as pricing, reducing the number of people working on product prices from about 200 to fewer than 10. Ellison promoted these changes as evidence that Internet-based systems could lower costs while improving access to information.

The headline needed qualification. Oracle claimed $1 billion in annual savings, but the first savings came from a mixture of standard software, prototype applications, centralization, cost cuts, and changed work practices. The completed E-Business Suite was not yet running the entire company. The transformation was real, but the marketing risked implying a cleaner cause-and-effect story than the evidence supported.

Analysis

Internal demonstrations can persuade more effectively than abstract promises because they give buyers a visible reference point. The stronger analytical move is to separate the intervention from other changes happening at the same time. Cost reductions may result from software, organizational redesign, labor cuts, or all three. Without that distinction, a genuine success can become an overstated sales claim. Credible evaluation asks what changed, compared with what baseline, and whether the gains persist without degrading service or shifting costs elsewhere.

Use better data to improve judgment, not to automate judgment away.

Daily Business Intelligence aimed to expose reality. Oracle's system put current business measures, such as sales performance, expenses, and service requests, in front of managers and employees. Instead of relying on delayed reports assembled from separate databases, people could examine updated information and compare performance across teams. One important correction followed: Oracle had emphasized software bugs as its quality measure, but customers could still struggle with products that were difficult to install or use. The company shifted attention toward service requests, which better reflected customer pain.

Measurement changes behavior. Ellison believed visible results could reduce arguments based on rank or personality. Yet a measure is only useful if it tracks what matters. A sales ranking may encourage effort, but it can also reward easy accounts or short-term deals. The system improves decisions only when leaders interpret the numbers in context.

Analysis

This is a practical case for evidence-based management, with a built-in warning from measurement theory: once a number becomes a target, people adapt to the number. A dashboard can reveal patterns that hierarchy suppresses, but it can also create false confidence if the underlying data are incomplete or the metric is poorly chosen. The shift from defect counts to customer service requests illustrates good measurement design: assess the experience the organization is trying to improve, not merely the activity easiest to count.

Build the sailing crew around trust, not just individual stars.

The America’s Cup exposed a team problem. Oracle's USA-76 was fast enough to challenge Alinghi, but its crew included factions from rival sailing programs. Ellison struggled to resolve the conflict between skipper Paul Cayard and star helmsman Chris Dickson, then delayed a clear decision. Dickson was eventually restored, while Peter Holmberg continued to handle starts and driving duties. The roles never meshed as smoothly as Alinghi's partnership between Russell Coutts and tactician Brad Butterworth.

The result was close, but decisive. Oracle lost the final 5-1. Its boat sometimes showed superior speed, but tactical errors and penalties repeatedly erased its advantage. The campaign demonstrated that money, elite talent, and engineering cannot substitute for a trusted operating team. Ellison later planned to build the next effort around Dickson from the outset.

Analysis

The crew's problem was not a shortage of talent. It was a failure to align authority, roles, and trust under pressure. In team research, coordination depends on shared expectations: members must know who is making the call, and when expertise should override rank. A brilliant but abrasive leader can raise performance standards while also provoking resistance. The right question is not whether a team should tolerate intensity, but whether its structure turns intensity into coordinated action rather than factions and hesitation.

Build the family you show up for, not the one biology assigns.

Belonging came through lived relationships. Ellison learned at age twelve that he had been adopted, then spent decades avoiding the subject. At thirty-four, after Oracle's crisis, he found his biological mother. The meeting brought information, but not an immediate family bond. He concluded that the aunt and uncle who raised him, and their children, were his family. He remained close to them and later worked hard to stay present in the lives of his own children after divorce.

Success did not settle the personal question. Ellison described fatherhood as changing how he responded to other people, while acknowledging that work sometimes pulled him away. His story complicates the idea that identity is simply inherited: care, shared history, and reliability mattered more than biological connection alone.

Analysis

The distinction between genetic relation and experienced belonging is especially vivid here. Family identity is built through repeated acts of care, not just through origin stories. The account also resists a tidy redemption arc: Ellison's love for his children and adopted family coexists with failed marriages, distance, and work-driven absences. That tension makes the portrait more useful. Affection is not only a feeling; it is a pattern of attention that can be interrupted by ambition, however sincere the attachment.

Fund cures where possible, because prolonged care can consume lives and resources.

Ellison made philanthropy a research bet. Guided by Nobel laureate Joshua Lederberg, he established the Ellison Medical Foundation to support research into diseases associated with aging, including Alzheimer's, Parkinson's, and osteoporosis. Ellison argued that preventing or curing disease could be more humane and less costly than supporting years of illness. He also invested in Quark Biotech, a commercial company pursuing cancer treatments and diagnostic tools.

The wager is long-term and uncertain. Ellison committed hundreds of millions of dollars, but basic research does not produce predictable results on a donor's timetable. Lederberg cautioned that cancer is many diseases and that cures would arrive incrementally. The foundation's focus also raised questions about whose illnesses receive research attention, though it later included infectious diseases affecting poorer countries.

Analysis

The distinction between cure and care captures both a humane ambition and an economic argument: preventing suffering can avoid downstream costs borne by families and health systems. Yet research portfolios cannot be judged like ordinary investments. Breakthroughs are uncertain, attribution is difficult, and a focus on diseases of aging can reflect the priorities of wealthy societies. A strong philanthropic strategy therefore needs patience, transparent evaluation, and room for neglected conditions, rather than assuming that a large budget guarantees a cure.

Analysis

Softwar is both a technology history and a portrait of a founder whose strongest trait, impatience with complexity, keeps producing consequences he does not control. Matthew Symonds builds the story around a repeated pattern: Ellison spots a structural weakness before competitors, stakes Oracle on a different architecture, then discovers that an elegant idea still depends on people, process, money, and timing. The network computer failed while Internet computing prevailed. The integrated suite offered a coherent answer to fragmented business systems, yet Oracle's early release exposed customers to the cost of unfinished software. The contrast is the book's central lesson: strategic vision creates advantage only when execution and accountability catch up.

The biography's double voice matters. Symonds reports scenes and disagreements, while Ellison's own commentary supplies explanations, corrections, and self-criticism. This makes the book unusually revealing, but also calls for caution. Ellison can acknowledge serious errors while framing them as the tuition for eventual victory. His account of the 1990 crisis, the Lane split, and Oracle's marketing claims sits beside other participants' conflicting memories. The reader sees not a neutral corporate record, but a contested history shaped by ambition and retrospective interpretation.

The richest tension is between centralization as a technical remedy and centralization as a leadership habit. One database can reduce duplication and make useful information available. One dominant executive can also make decisions faster. But a system that concentrates information and authority can suppress local knowledge, dissent, and the warnings that prevent costly mistakes. The book offers no simple answer. Ellison's success depended on both his willingness to challenge conventional practice and colleagues willing to tell him when his certainty exceeded the facts. Oracle's durable advantage came not from vision alone, but from the difficult work of making vision testable.

Summary in 30 Seconds
A sound technology forecast can outlast the product built to embody it, but vision needs sound execution. Shared data systems reduce fragmentation, while standardizing work before software customization can cut delays and costs. Oracle’s weak financial controls helped drive a $36 million loss in 1990. Clear decision rights, internal testing, and measures tied to customer experience help prevent ambition from outrunning accountability.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.78 out of 5
Average of 499 ratings from Goodreads and Amazon.

Softwar receives mixed reviews, with an average rating of 3.79 out of 5. Readers appreciate the intimate portrait of Larry Ellison and Oracle's history, praising the unique format with Ellison's commentary. However, many criticize the book's length, repetitiveness, and lack of objectivity. Some find it invaluable for those in the software industry, while others feel it's overly detailed and biased. The book's insights into Oracle's business strategies and Ellison's personality are frequently highlighted, though some readers desire a more balanced perspective and updated information.

Your rating:
4.3
262 ratings
Want to read the full book?

Glossary

Internet computing architecture

Server-based network computing

A computing model in which applications and data are held on network servers and accessed through relatively simple client devices, often using a browser. Ellison promoted it as an alternative to client/server systems that distributed software and databases across many desktop computers. The proposed Network Computer was one possible device for this architecture, but the architecture outlasted that particular product.

E-Business Suite

Integrated business applications

Oracle's suite of applications for business functions such as finance, human resources, manufacturing, supply chain, sales, and customer service. Its defining design goal was to share a common data model and database, reducing the need to connect separate vendors' products. Oracle also promoted standard installation with minimal code modification to lower implementation and upgrade costs.

best-of-breed

Specialist products from multiple vendors

An approach to enterprise software in which a company selects the strongest available product for each function, such as sales, accounting, or supply-chain planning. The products may come from different vendors and were often not designed to share data or work together. Integrating and maintaining them can require extensive consulting, custom interfaces, and ongoing coordination.

single global database

One shared enterprise data store

Oracle's objective of holding an organization's operational information in a consolidated database accessible across locations and departments. Applications using the same data model can rely on consistent records rather than maintaining separate, conflicting versions of customers, employees, or orders. The concept was intended to improve analysis and coordination while reducing duplicated systems and data entry.

Daily Business Intelligence

Frequently updated business measures

Oracle's system for presenting current operational data to managers and employees through reports and dashboard-style displays. It aimed to make business performance visible without waiting for separate data warehouses to combine fragmented information. The book describes its use for measures such as sales, expenses, and customer service requests, while emphasizing that the choice of metric affects behavior.

Real Application Clusters

Database across linked computers

Oracle's clustering technology, which allows multiple computers to run a shared database for applications. Oracle presented it as a way to increase capacity and reliability by adding lower-cost machines instead of relying on one large, expensive server. The company's claim was that applications could use the clustered database without being rewritten to manage the separate machines.

management by ridicule

Publicly attacking colleagues' ideas

Ellison's self-deprecating name for an early management style in which he used prolonged argument and intellectual criticism to establish dominance in meetings. He later recognized that public humiliation could make people afraid to contribute or eager to see the leader fail. He became more cautious about using the approach, especially as CEO.

alternative stress

A demanding escape from work

A phrase used in the book for activities such as competitive sailing and flying that absorb attention through intense, immediate demands. Ellison described these pursuits as ways to displace the pressures of business with a different kind of challenge. They were not passive relaxation: they required concentration, risk management, and performance under pressure.

FAQ

What is Softwar: An Intimate Portrait of Larry Ellison and Oracle by Matthew Symonds about?

  • Comprehensive biography and company history: The book provides an in-depth look at Larry Ellison’s life, his management style, and the rise of Oracle Corporation from a small startup to a global software powerhouse.
  • Focus on technology and business strategy: It explores Oracle’s technological innovations, especially in databases and enterprise software, and Ellison’s vision for integrated software suites versus best-of-breed solutions.
  • Coverage of major events and challenges: The narrative includes Oracle’s internal crises, competitive battles with Microsoft and SAP, the rollout of the E-Business Suite, and Ellison’s personal pursuits such as sailing and philanthropy.

Why should I read Softwar: An Intimate Portrait of Larry Ellison and Oracle by Matthew Symonds?

  • Rare access to Ellison: The author had unprecedented access to Larry Ellison and Oracle executives, offering candid insights into Ellison’s personality, leadership, and decision-making.
  • Understanding tech industry evolution: Readers gain a deep understanding of the software industry’s transformation, including the shift from client/server to Internet computing and the challenges of enterprise applications.
  • Lessons in leadership and innovation: The book provides valuable lessons on leadership, risk-taking, and the cost of rapid growth, as well as the importance of vision and execution in building a tech giant.

What are the key takeaways from Softwar by Matthew Symonds?

  • Visionary leadership and risk: Ellison’s bold vision, willingness to take risks, and relentless pursuit of innovation were central to Oracle’s success and survival through crises.
  • Integrated software vs. complexity: The book highlights the importance of integrated software suites in reducing IT complexity and cost, contrasting Oracle’s approach with the best-of-breed model.
  • Management and culture: Ellison’s management style—intense, demanding, and sometimes contradictory—shaped Oracle’s culture, driving both innovation and internal conflict.

What are the best quotes from Softwar by Matthew Symonds and what do they mean?

  • “Gardens last for hundreds of years, companies don’t.” — Ellison reflects on the transient nature of business versus personal legacy.
  • “It’s the information age, not the fucking operating system age.” — Emphasizes the shift from OS-centric to data-centric computing.
  • “You cannot lead if you’re filled with uncertainty...” — Highlights the importance of confidence and decisiveness in leadership.
  • “When I say Oracle clusters can run real applications and DB2 clusters can’t, some people think I’m lying. I’m not. It’s a fact.” — Ellison defends his bold, fact-based marketing style.

How does Softwar by Matthew Symonds portray Larry Ellison’s management style and leadership?

  • Intensity and complexity: Ellison is described as intense, passionate, and sometimes contradictory, combining sensitivity with ruthless business tactics.
  • Visionary yet pragmatic: He has a clear architectural vision for software but is also deeply involved in execution details, valuing engineering excellence and integrated solutions.
  • Demanding but loyal: Ellison places huge trust in key subordinates but acts decisively against those who disappoint him, fostering both competition and cooperation within Oracle.

What is the significance of Oracle’s E-Business Suite in Softwar by Matthew Symonds?

  • Integrated software vision: The E-Business Suite represents Oracle’s strategy to provide a complete, integrated set of applications sharing a single database and data model.
  • Challenges and recovery: The suite’s rollout was rocky, with quality issues and customer skepticism, but it eventually stabilized and gained a growing customer base.
  • Market impact: The suite became a key weapon against competitors like SAP and Siebel, with Oracle betting on its architectural purity and comprehensive coverage.

How does Softwar by Matthew Symonds explain Oracle’s “war on complexity” and integrated suite strategy?

  • Complexity as the enemy: Ellison argued that fragmented data and complex integrations caused IT failures and poor value.
  • Integrated suite solution: Oracle’s E-Business Suite was designed as a unified set of applications sharing a single global database, reducing customization and integration costs.
  • Changing customer mindset: Ellison urged customers to adapt business processes to the software, emphasizing standardization and modernization for efficiency.

What were the main challenges Oracle faced in its applications business according to Softwar by Matthew Symonds?

  • Late to client/server and GUI: Oracle’s applications lagged behind competitors like SAP and PeopleSoft in adopting new architectures and user interfaces.
  • Internal management struggles: The applications division suffered from poor leadership, factionalism, and tension between development and sales/consulting.
  • Best-of-breed strategy difficulties: Integrating third-party applications was costly, complex, and often unprofitable, leading to internal conflicts and strategic pivots.

How did Larry Ellison and Oracle recover from their near-death experience in 1990 as described in Softwar by Matthew Symonds?

  • Financial crisis and management overhaul: Oracle faced a cash crunch and accounting scandals, prompting Ellison to bring in experienced executives to restore order and credibility.
  • Product turnaround with Oracle 7: The release of a stable, feature-rich database helped regain customer trust and market share.
  • Cultural and organizational changes: Oracle shifted from a cowboy sales culture to a more disciplined, service-oriented approach, restructuring sales and building a stronger consulting organization.

What is Oracle’s Real Application Clusters (RAC) technology and its significance in Softwar by Matthew Symonds?

  • Breakthrough clustering: RAC allows multiple low-cost servers to operate as a single, fault-tolerant database system, improving reliability and scalability.
  • Cost and performance benefits: RAC lowers hardware and operating costs while enhancing performance, making it a major advance since Oracle’s original SQL database.
  • Industry impact: RAC positioned Oracle as a leader in database technology, differentiating it from competitors like IBM and Microsoft.

How does Softwar by Matthew Symonds describe Larry Ellison’s personal interests, philanthropy, and life outside Oracle?

  • Passion for sailing and adventure: Ellison is deeply involved in competitive sailing, including America’s Cup campaigns, and uses activities like flying and guitar as stress outlets.
  • Philanthropic efforts: He established the Ellison Medical Foundation, focusing on diseases of aging, and invested in biotech ventures like Quark Biotech Inc.
  • Complex personal life: The book covers Ellison’s adoption, family relationships, multiple marriages, and his pursuit of personal legacy beyond business.

How does Softwar by Matthew Symonds depict Oracle’s competition with Microsoft and SAP?

  • Microsoft rivalry: Ellison views Microsoft as a formidable competitor, especially in desktop and low-end server markets, and criticizes its lack of true innovation.
  • SAP competition: SAP is Oracle’s main rival in enterprise applications, with both companies vying for dominance in the integrated suite market.
  • Best-of-breed vs. suites: Oracle criticizes best-of-breed vendors as transitional, betting on integrated suites to reduce complexity and cost, and predicting industry consolidation around Oracle and SAP.

About the Author

Matthew Symonds is a British journalist born in 1953. He co-founded The Independent newspaper in 1986 and has since established himself as a respected writer in the technology and business sectors. Symonds gained unprecedented access to Larry Ellison for his book Softwar, spending three years closely observing the Oracle CEO. This intimate approach allowed him to create a detailed portrait of Ellison and Oracle's operations. Since 2018, Symonds has served as the executive director of the Larry Ellison Foundation. He is also known for his personal connection to British politics, as his daughter Carrie is married to former Prime Minister Boris Johnson.

Download PDF

To save this Softwar summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.46 MB     Pages: 21

Download EPUB

To read this Softwar summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.45 MB     Pages: 28
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...