Category

Work

Category

Why That Big Thug May Become Your CEO Someday

What the playground and football field teach about leadership that a transcript cannot measure.

The large young man across from your daughter may have had a less than remarkable academic record in high school. He may have arrived at college because a football coach discovered that an academic scholarship, a presidential scholarship, and an alumni grant could somehow cover his entire $45,000 tuition. Your straight-A daughter may reasonably wonder which one of them is supposed to be the scholar.

Do not dismiss him too quickly.

He may be receiving an education that never appears on a transcript—an education in hierarchy, trust, fear, loyalty, public failure, physical courage, coalition-building, and the difficult art of persuading other people to pursue a common objective. Long after everyone has forgotten his grade-point average, those lessons may place him in the corner office.

That big thug may become the CEO of the company you work for someday.

The Education We Do Not Measure

We have built an educational culture that measures what is easiest to record. We count grades, test scores, credit hours, degrees, and technical credentials. Those things matter. STEM disciplines teach us how physical, mathematical, and computational systems work. Postsecondary education can develop analytical discipline and provide the specialized knowledge on which modern civilization depends.

But every company, university, government, church, team, and family is also a human system. Human systems run on rules that rarely appear in a syllabus: Who earns trust? Who gains status, and why? When should a person challenge authority, and when should he yield? How do coalitions form? How does someone lose without disappearing—or win without making everyone else determined to destroy him?

I call these the rules of the playground.

The playground is one of the earliest places where children encounter power without an adult narrating every move. They choose sides, negotiate rules, resolve disputed calls, test courage, form loyalties, suffer public embarrassment, and return the next day to do it again. It is an informal education in how people actually behave when something matters.

Different Arenas, the Same Adrenaline

The arena changes, but the circuitry does not.

I compete through code, systems, and virtual architecture. My victories may occur inside structures most people never see. An athlete competes through force, timing, endurance, and coordinated execution that spectators can see immediately. Both experiences produce the same essential reward: I faced resistance, imposed order on it, and won.

That is why even a self-described pencil-necked geek can become emotionally invested in a group of enormous men colliding over a painted line. They become visible representatives of our own competitive identity. When they win, the mathematician, musician, programmer, professor, and offensive lineman all say the same thing: We won.

A winning team makes the institution feel successful. It produces energy, belonging, alumni pride, family loyalty, and the sense that the college is a place where excellent things happen. Even when admission to the game costs nothing, the game still has economic value. The game ticket is not necessarily the product. The college is the product, and sport is part of the experience that persuades families to choose it.

No Athletic Scholarships—Just a $225,000 Coincidence

My family learned the economics of Division III football in a way that was both illuminating and difficult to explain.

We understood that Division III schools did not award athletic scholarships. Then a coach told us that my son, whose high-school grade-point average was less than remarkable, would easily receive a presidential scholarship and an academic scholarship, each worth about $15,000 per year. An alumni grant covered the remainder of approximately $45,000 in annual tuition.

Officially, he received no football scholarship. Economically, he received a five-year, full-tuition package worth approximately $225,000, wearing three nonathletic name tags.

Meanwhile, my two A-plus daughters—accomplished theater and music students—did not quite receive those full academic or presidential awards. They possessed the academic achievement. my son possessed something the institution also valued intensely: recruiting leverage and the ability to help produce a competitive football program.

That distinction was difficult to explain without sounding cynical. But the institutional logic is straightforward. A Division III football team may not earn much from tickets or television. Its value can come from attracting a large roster of students, bringing families and friends to campus, strengthening alumni attachment, creating traditions, and making the school more appealing to the entire student body. Even after tuition discounts, a large athletic program can support enrollment, housing, dining, fees, fundraising, and institutional identity.

The rules prohibited calling His package an athletic scholarship. They did not eliminate football’s economic leverage.

The Answer I Owe My Daughters

My daughters could reasonably ask, “Come on, Dad—football? Really? Is that important to society?” They deserved more than an economic answer about enrollment and tuition. They deserved an educated explanation of why societies keep creating arenas for competition and why institutions invest so heavily in them.

Organized American sport grew during the nineteenth and early twentieth centuries through clubs, schools, colleges, settlement houses, YMCAs, and rapidly expanding cities. Baseball became a shared civic language. Colleges transformed rough student contests into organized football. Basketball was deliberately created for an indoor educational setting. Sport helped institutions absorb strangers, immigrants, and young people into teams governed by common rules.

Reformers also believed strenuous games could develop character. The theory was not that running, blocking, or tackling automatically made someone virtuous. It was that disciplined competition repeatedly exercised qualities society needed: courage under pressure, self-command, preparation, loyalty, endurance, acceptance of authority, responsibility to teammates, and respect for an opponent who had voluntarily accepted the same rules.

Competition does not manufacture those strengths by itself. It can also reward vanity, cruelty, cheating, tribalism, and domination. That is why the rules of the playground matter more than the mere existence of a contest. Competition becomes educational only when victory remains subordinate to honor and when strength carries obligations toward the weaker members of the group.

There is also a serious historical idea behind the intuition that games might redirect some of humanity’s appetite for conflict. The founder of the modern Olympic movement, repeatedly argued that international athletic competition could foster understanding, respect, and peace among nations. He was not simply claiming that games would abolish war. He hoped young people could encounter foreign rivals inside a shared structure of rules rather than only as enemies.

The Moral Equivalent of War

The philosopher behind the idea belongs near the center of this argument because he understood something polite discussions of peace often evade: people do not surrender their appetite for ordeal, courage, sacrifice, discipline, and belonging merely because war is terrible. A peaceful society must give those instincts honorable work to do.

That is a profoundly practical insight. He was a founder of American psychology and a leading philosopher of pragmatism—a thinker interested not merely in whether an idea sounded noble, but in what it produced in lived experience. He knew that condemning aggression was insufficient. Society needed demanding institutions that could recruit the same human energies and redirect them toward service, mastery, construction, discovery, and disciplined competition.

An American philosopher approached the problem from another direction. He argued that war had historically cultivated qualities such as courage, discipline, sacrifice, endurance, obedience, and common purpose—and that a peaceful society would need a “moral equivalent of war” capable of preserving those demanding virtues without the killing. He was not proposing organized sport as the sole answer, but honorable sport can perform part of that function: intense conflict with agreed boundaries, real sacrifice, decisive outcomes, and the possibility of shaking hands afterward.

Sport is therefore not automatically peaceful. Rivalries can inflame nationalism, cruelty, and mob identity just as easily as they can discipline them. But at its best, sport converts aggression into achievement, enemies into opponents, violence into regulated contact, and tribal loyalty into a contest that ends without conquest. We fight symbolically, submit ourselves to rules, accept the result, and agree to meet again.

So my answer to my daughters is not that sport is more valuable than theater, music, science, or scholarship. It is not. Theater teaches empathy and collective expression. Music teaches disciplined listening and harmony. Scholarship teaches us to distinguish truth from confidence. Sport teaches another necessary part of citizenship: how to compete intensely without abandoning integrity, how to belong to something larger than oneself, and how to turn strength into responsibility.

My son did not deserve greater human worth because he played football, and my daughters did not contribute less because their gifts belonged to the stage and classroom. The financial packages reflected what the institution was organized to recruit and promote—not a fair ranking of their intelligence, character, or social value. Understanding that distinction does not erase the inequity, but it explains the machinery behind it.

That is the defense of sport I could offer them: not that games are sacred, and not that every athlete becomes a leader, but that honorable competition is one of the ways a society teaches powerful people to govern themselves before asking them to govern anyone else.

What the Athlete Is Learning

Organized sport compresses the rules of the playground into an unusually intense laboratory. An athlete learns to accept public evaluation, perform while exhausted or afraid, depend on people unlike himself, follow before expecting to lead, recover visibly from failure, and place the team’s objective above personal comfort. Different sports emphasize different virtues, but all can make preparation, consequence, cooperation, and character visible.

The athlete also learns that talent without reliability is nearly useless. Every assignment matters because someone else’s effort and reputation may depend on it. The athlete prepares for an opponent who is preparing just as seriously to win, and learns that confidence must survive evidence, criticism, fatigue, and the scoreboard.

Most importantly, he repeatedly confronts a fact that solitary academic achievement can sometimes obscure: I cannot accomplish this alone, but I can help organize people so that together we accomplish it.

The technically smartest person therefore does not automatically become the chief executive. The architect may understand every component of the system, yet the future CEO may be the person who can select a team, establish an objective, allocate responsibility, settle disputes, communicate confidence, and keep everyone moving after a loss.

One person designs the cathedral. Another convinces fifty exhausted people to carry the stones. The exceptional leader can do some of both.

Why the Geek Follows the Captain

This is not simply brains submitting to muscle. It is one form of competitive intelligence recognizing another.

Cerebral people compete constantly. We compete in ideas, designs, diagnoses, negotiations, businesses, laboratories, and code. But our victories are often private and abstract. The athlete enacts competition publicly. He provides a visible narrative—preparation, opposition, risk, consequence, victory or defeat—that allows an entire community to participate.

Humans also notice the person around whom others organize themselves. On the childhood playground, that person chooses teams, calls the game, resolves an argument, and makes everyone believe his side can win. In adulthood we use more sophisticated words—presence, command, charisma, leadership—but part of us still recognizes the playground captain.

The best partnership is not brains beneath brawn. It is the architect who can see the structure working with the captain who can make people build it. A person who masters both technical systems and human systems is exceedingly difficult to compete against.

The Bully Is Disqualified

There is one indispensable exception: the bully.

The playground does not confuse intimidation with leadership. A bully may possess size, aggression, and temporary control, but he violates the most important rules. He humiliates the weak, changes the rules when he is losing, takes credit without accepting responsibility, and uses power to protect himself rather than the game.

Bullies are not allowed—not under the honorable rules of the playground. They may dominate briefly, but they do not become legitimate champions. Fear can compel obedience for a time; it cannot create the durable trust on which great teams and organizations depend.

The true playground champion is different. He competes fiercely but fairly. He chooses sides, settles disputes, protects smaller players, accepts defeat, and returns the next day prepared to earn victory again. His strength is restrained by integrity. His confidence is accompanied by responsibility. Others follow him not merely because he can overpower them, but because they trust what he will do with power.

The rules of the playground do not say that the strongest person should lead. They say that strength earns leadership only when it is governed by integrity, honor, courage, and responsibility toward the group.

A Champion’s Education

His own path carried these lessons in unusually physical form. A catastrophic bilateral shoulder injury damaged the posterior glenoid rim and labrum in both shoulders. Each side required separate reconstruction and recovery because surgeons could not place a roughly 300-pound patient on a freshly repaired shoulder to operate on the other one.

He endured two major operations, two recoveries, and the long return to training. The injury may have redirected his trajectory from potential Division I football to Division III, but it did not end his career. He received a full five-year tuition package, started throughout college, and served as a captain for all five years.

There is an irony worth adding to the picture. This same football player was also a serious chess competitor. He finished first in the state in three of his four high-school years, and in grade school he once ranked eighth in the nation. His academic record may have been less than remarkable, but his ability to study an opponent, recognize patterns, anticipate consequences, and think several moves ahead certainly wasn’t. The athlete and the strategist were the same person.

His competitive education was not confined to the football field. He was also a serious chess player: first in the state three of his four high-school years, and eighth in the nation during one of his grade-school years. The irony is hard to miss. The young man whose conventional academic record was less than remarkable was quietly mastering a game of calculation, patience, pattern recognition, and strategy. The same mind that studied openings and anticipated moves across a chessboard was learning to read people and situations on a football field.

The transcript cannot fully describe that education. It cannot quantify the decision to return after the first operation knowing another awaited him. It cannot measure the discipline required to rebuild twice, the credibility earned from teammates who watched him do it, or the leadership developed by repeatedly placing the group’s purpose above pain and disappointment.

Grades matter. Technical mastery matters. Degrees matter. But none of them independently measures courage, honor, resilience, judgment, presence, or the ability to make other people believe that difficult work is possible.

The Lesson

We should stop treating the playground as the opposite of education. It is one of education’s oldest and most consequential classrooms.

Formal education teaches the content of the game. The playground teaches how human beings actually play it. One teaches us to understand systems; the other teaches us to understand people. Organizations require both, but the person who understands people often ends up leading the person who understands only the system.

So do not dismiss the big young man with imperfect grades. Ask what else he has learned. Ask whether he accepts responsibility, protects the vulnerable, honors the rules, recovers from defeat, and makes the people around him better. Ask whether others trust him when the outcome is uncertain and the pressure is real.

If he is a bully, he has failed the playground’s most important test.

But if he is the champion—the one whose strength is governed by integrity and whose ambition includes the team—then pay attention.

He may become the CEO of the company you work for someday.

From dragging CSV columns to describing intent

There was a time when updating 2,000 records in NetSuite began with a CSV file, a browser window, and a small prayer.

You opened the Import Assistant. You selected a record type. You chose Add, Update, or the excitingly ambiguous Add or Update. Then you dragged fields from one side of the screen to the other, checked the mappings, reconsidered the mappings, checked them again—and eventually pressed the button that could alter half the company’s item master.

It worked. Usually.

But it was slow, clumsy, and dangerous in a peculiarly human way. The danger was rarely dramatic code failure. It was a fleeting choice made in a temporary browser screen: the wrong field, the wrong reference type, the wrong overwrite option, or the right file mapped to the wrong place.

There was very little durable evidence of the thinking behind the change. The CSV survived. The resulting records survived. The exact sequence of decisions in between mostly evaporated.

Then the NetSuite developer began to evolve.

Stage One: CSV Import

The early NetSuite operator can be identified by several distinctive traits: a curved spine, a furrowed brow, and an unusual ability to stare at two columns for fifteen minutes without blinking.

CSV Import was—and still is—a legitimate, useful NetSuite tool. For a straightforward, well-understood update, it may be exactly the right tool. But a browser-guided import asks a human to translate business intent into a series of one-time interface choices.

The instruction might begin simply:

Change these 2,000 records from notImported to the correct status.

But the operator still has to select the correct record type, identify each record properly, map the field, decide how blank values should behave, choose the update mode, and verify the results.

The computer performs the repetitive work, but the human still assembles the machine by hand every time.

Stage Two: SuiteScript

The next evolutionary leap was SuiteScript.

Instead of telling NetSuite what to do through a temporary arrangement of browser fields, we could describe the rules permanently in code:

Read this file. Find this record. Confirm that its current value is what we expect. Change only this field. Skip anything suspicious. Log every result.

For large jobs, Map/Reduce was particularly well suited. NetSuite describes it as a script type for large volumes of data that can be divided into small, independent pieces. The platform can create the necessary jobs, run them in parallel, and automatically yield and reschedule work as resource limits are approached.

That was a substantial improvement. The update became repeatable. Validation could be explicit. One bad row did not necessarily destroy the entire job. Successes, skips, and errors could be counted and explained.

There was, however, a catch.

The actual business instruction might be one sentence, but a responsible Map/Reduce script could easily consume 100 to 200 lines:

  • load the CSV;
  • parse quoted commas correctly;
  • validate the headers;
  • identify each record;
  • check the existing value;
  • perform the update;
  • catch errors;
  • respect NetSuite governance;
  • log the outcome; and
  • summarize the execution.

The line that changes the field may be tiny. The other 199 lines are the guardrails.

Stage Three: Juicy Code Bytes

Once we had written a useful updater, naturally we saved it.

Somewhere in the NetSuite File Cabinet—or on somebody’s laptop—there appeared a file with a name like:

my_personal_little_item_updater.js

It was precious. Those were juicy code bytes: a concentrated chunk of hard-won knowledge about NetSuite records, internal IDs, governance, mandatory fields, and all the small ways an apparently simple update could go sideways.

So we copied it. We modified it. We saved another version:

my_personal_little_item_updater_FINAL_v3_really_final.js

This was progress, but it created a new species of problem. The code was reusable, yet personal. Its history was uncertain. Its deployment record might live somewhere else. Nobody was completely sure whether the version in NetSuite matched the version on the laptop—or whether the script built for customers in 2022 was now quietly updating inventory items in 2026.

We had graduated from temporary clicks to permanent code, but not necessarily to an organized development process.

Stage Four: AI Writes the Script

Artificial intelligence changed the economics of small, purpose-built software.

A 150-line script no longer had to justify several hours of typing. I could describe the outcome in ordinary language:

Here is a CSV containing 2,000 record IDs. Change the stale notImported value, but only if the record still contains the expected old value. Do not touch anything else. Log every success, skip, and error, and give me a final reconciliation.

AI could generate the Map/Reduce structure, CSV parsing, validation, update logic, error handling, and summary code in minutes.

That does not mean the thinking disappeared. It means the typing stopped being the expensive part.

The important work moved upward:

  • What exactly is the intended business result?
  • Which records are authorized to change?
  • What must remain untouched?
  • What conditions should cause a record to be skipped?
  • How will we prove that the result matches the request?
  • What is the recovery plan if our premise was wrong?

AI made code cheap enough that even a one-time repair could afford real validation, logging, and reconciliation. We did not eliminate the 200 lines of guardrails. We taught something else to write them.

Stage Five: AI Meets the CLI and SDF

Then AI got access to a proper workshop.

With the SuiteCloud CLI and SuiteCloud Development Framework, the work no longer begins and ends with a loose JavaScript file. It can live in a complete, file-based SuiteCloud project containing:

  • the SuiteScript source;
  • XML definitions for script and deployment records;
  • project dependencies;
  • deployment instructions;
  • configuration and preference files; and
  • other supported NetSuite custom objects.

Oracle’s own documentation describes SDF as a way to build, validate, and deploy SuiteCloud projects from a local computer. NetSuite objects can be represented in XML, and the CLI can validate a project before it is deployed. Deployment and validation logs provide another layer of evidence when something succeeds—or fails.

Put that project under version control and the change becomes inspectable:

  • What files changed?
  • What object or deployment was added?
  • What did the previous version contain?
  • Did validation pass?
  • Which account received the deployment?
  • What did NetSuite execute?
  • Which records succeeded, skipped, or failed?

This is the crucial distinction: the CLI does not magically make a change safe, and AI does not magically make it correct.

The CLI and SDF provide structure. Version control provides history. NetSuite permissions provide boundaries. Validation catches certain errors. Logs provide evidence. Backups and recovery plans provide recourse. A knowledgeable human still defines the intent and decides whether the evidence is convincing.

Safety is not one feature. It is the accumulation of constraints.

The Real Evolution: From Procedure to Intent

At first glance, the progression appears to be about speed:

Browser import → handwritten script → saved script → AI-written script → AI with CLI and SDF

But the more profound change is the gradual separation of intent from procedure.

In the browser-import era, the human personally executed much of the procedure.

In the SuiteScript era, the human encoded the procedure.

In the juicy-code-bytes era, the human reused the procedure.

In the AI era, the human described the procedure and AI wrote it.

In the AI-plus-CLI era, the human can increasingly state the intended outcome and the constraints, while AI constructs the procedure inside a controlled, inspectable delivery system.

That does not make the human less important. It makes human judgment more visible.

“Update these 2,000 records” is not enough.

“Update exactly these 2,000 records, only when the existing value is stale, change only this field, produce a before-and-after reconciliation, validate the project, retain the source and deployment definitions, and report every exception” is a specification.

And a specification is something both humans and machines can examine.

Darwin’s Missing Final Figure

The traditional evolution illustration ends with a human standing proudly upright, as though evolution has completed its work.

Our NetSuite version ends with a developer at a clean workstation, surrounded by CLI output, SDF XML, validation checks, Git history, and execution logs. On the desk is a coffee mug that reads:

SHIP IT WITH CONFIDENCE

But confidence is not certainty. The fully evolved operator is not the person who believes nothing can go wrong. It is the person who can explain:

  • what is about to happen;
  • why it should happen;
  • what is prevented from happening;
  • how we will know what actually happened; and
  • what we will do if reality disagrees.

That is a surprisingly large philosophical journey from dragging CSV columns across a browser window.

Darwin raises his pointer toward the final figure and observes:

The opposable thumb has been replaced by a deploy command.

Maybe. Maybe not. But it made me think.


Publishing Notes

Suggested URL slug: evolution-of-netsuite-development

Excerpt: NetSuite bulk updates evolved from nervous browser imports to scripted automation, reusable code, AI-generated SuiteScript, and finally AI working through the SuiteCloud CLI and SDF. The real evolution was not merely speed. It was the journey from performing procedures to describing intent.

SEO title: The Evolution of NetSuite Development: From CSV Imports to AI and SDF

Meta description: A humorous history of NetSuite development—from browser CSV imports and 200-line Map/Reduce scripts to AI, SuiteCloud CLI, SDF validation, XML deployments, version control, and logs.

Hero-image alt text: Victorian Darwin points to five stages in the evolution of NetSuite development: CSV Import, SuiteScript, saved “juicy code bytes,” AI-written scripts, and a modern CLI-and-SDF workflow.

Image caption: The evolution of the NetSuite developer—from dragging CSV columns to describing intent. Illustration created with AI from an idea developed by Jim Vanpetten.

Technical References