I Bought a MacBook Neo to Test Whether It Can Handle Real University Work

I just bought a blue MacBook Neo with 512GB of storage and Touch ID, and I am going to use it for real university work to see how it performs. I do not want this to stay in the realm of pricing theory or product speculation. I want to find out what the experience actually feels like when the machine is asked to support the kinds of work many of us do every day.

The test setup is deliberate. I am going to use the browser-based version of the Microsoft 365 suite rather than installing local apps. I want to know how far a lower-cost machine can go when paired with the increasingly web-centered workflows that already define a large share of campus work.

A browser-first setup is the point of the test

For many university users, the everyday workload is no longer centered on heavy local software. It is centered on email, documents, Teams meetings, shared files, presentations, research browsing, dashboards, and cloud-based services. That makes MacBook Neo interesting because it shifts the question away from peak power and toward practical sufficiency.

So I am intentionally keeping this machine light. No installed desktop versions of Word, Excel, or PowerPoint. No attempt to turn it into a power-user workstation. If this device is going to tell us something useful, it should be tested in a way that mirrors how a growing share of students, graduate students, faculty, and staff already work.

The AI layer matters just as much as the productivity layer

I am also adding Claude and ChatGPT, with Codex access, under the university's licensing agreements. That matters because any serious evaluation of a modern campus device now has to include AI. The machine does not just need to handle documents, meetings, and tabs. It also needs to support the way people increasingly move between writing, research, coding, summarization, and ideation with hosted AI tools in the middle of that workflow.

That is one reason MacBook Neo is worth testing. Many of the major AI tools people care about today are delivered through the browser or a cloud service. If the device is responsive, stable, comfortable to carry, and capable of sustaining that pattern of work across a long day, then the threshold for value may be lower than many of us have assumed.

What I want to learn from this

• Whether browser-based M365 feels fully workable for a normal university workday
• Whether Claude, ChatGPT, and Codex feel smooth enough on a lower-cost machine
• Whether battery life, responsiveness, video meetings, and multitasking hold up over time
• Whether the overall experience feels merely acceptable or actually positive

I am less interested in benchmark culture than in practical signal. Does the machine feel dependable? Does it disappear into the workflow in a good way? Does it create friction that would make faculty, staff, graduate students, or students feel underpowered, or does it quietly do the job?

Some of my old must-haves still apply

This experiment brings me back to a much older blog post I wrote in 2009 called "My Must Haves." At the time, I was thinking about lightweight portable computing, cloud services, and what it would take to live more of my work on a smaller, more mobile machine. My work then had already shifted away from code and media production and toward meetings, budgets, proposals, notes, reading, writing, and calendar management. That is still a useful frame for this test, because those same patterns describe a lot of university work today.

Back then, the tools I depended on were things like Evernote, blogs, wikis, Basecamp, Flickr, YouTube, Facebook, Google Docs, and an early look at Dropbox. What tied that list together was not any one product. It was the idea that the machine mattered less if my notes, documents, conversations, and project work were available anywhere. That same logic is showing up again here. Today the stack looks different, but the principle is familiar: browser-based M365, cloud storage, Teams, and hosted AI tools like Claude, ChatGPT, and Codex all push more of the value into the network and less into the local machine.

What has changed is that the baseline expectation is now higher. I still care about mobility, battery life, and a machine that stays out of the way, but I also need smooth browser performance, dependable video meetings, fast switching across cloud-based documents and services, and reliable access to AI tools that sit directly inside the work itself. That is part of what makes this MacBook Neo test interesting to me. It is a chance to revisit the old lightweight-computing question in a moment when cloud platforms are more mature and the AI layer has become part of normal daily work.

Why this matters for the university

If a machine like this performs well, it could have implications beyond one purchase. It could mean the university should revisit some of its assumptions about refresh cycles, device eligibility, and where lower-cost but still high-quality machines fit in the overall strategy. That could matter for staff workflows, for graduate student support conversations, and for the broader question of how to deliver more value without defaulting to higher-cost devices.

I am especially interested in whether a device at this price point could help the university save money while still delivering a positive user experience. That does not automatically make it the right answer for every role. But if the experience is strong, it may expand the range of roles and populations for which a lower-cost device is a credible choice.