Experimentation Over Polish: Inside February’s Code & Share

February’s Code & Share didn’t feel like a demo day. It felt like a studio door left open.

On a quiet Saturday afternoon, a small group of Memphis technologists gathered virtually. Not to pitch finished products, but to show work mid-flight. Senior engineers, designers, researchers, and junior developers shared the same room, asking questions out loud instead of in chat, leaning into conversation over commentary. What emerged was a clear throughline: progress happens faster when people are willing to show unfinished work.

Two moments, in particular, captured that spirit.

The room visibly shifted during Coriano Harris’s presentation.

Instead of dashboards or deployment pipelines, Coriano shared experimental NextJS projects that treated software as something closer to a living body. One interface breathed: text rising and falling rhythmically. Tap the screen, and it coughed. Move the mouse, and the breathing quickened, like exertion. Another project simulated digital injury, darkening and bruising the interface under sustained interaction. A third released gravity altogether, letting structured content fall apart and float away.

The questions that followed weren’t typed into chat; they were spoken. One came from a junior developer: What about accessibility?

Coriano’s answer landed precisely because of its honesty. Accessibility, performance, and polish weren’t ignored. They were intentionally excluded at this stage. The work wasn’t meant to be shipped; it was meant to explore. The distinction sparked a thoughtful discussion about phases of creation: when experimentation is the goal, and when production constraints enter the picture.

It was a quiet but important lesson, especially for early-career builders: not all valuable work needs a roadmap or a business case. Sometimes asking “what if?” is the work.

That theme resurfaced from a different angle during Michael Payne’s segment.

Michael introduced Are You Fullstack, a mentorship service for developers and technical teams. But the real value came from how he talked about building it. He described the clarity that comes from working on something you care about, and how momentum follows once you stop waiting for perfection.

He broke down an “attention funnel” in plain language. How posts and blogs lead to conversations, and conversations lead to services. Then he framed marketing not as a separate discipline, but as a necessary extension of building. The advice resonated across experience levels, especially his blunt reminder: projects don’t have to be perfect to be useful. They just have to exist.

Heads nodded. Questions followed. The room recognized itself in the problem.

That same generosity showed up earlier when Kevin Kawchak opened the session with advanced work in medical AI: standardizing robotic systems, digital twins, and embodied AI for oncology clinical trials. Much of the technical depth was beyond the room’s immediate grasp, and that was okay. The value wasn’t mastery; it was exposure.

Kevin’s presentation showed what’s possible when Memphis-based technologists operate at the edge of healthcare and research. And when they choose to document that work openly, through shared repositories and repeatable standards.

The final presentation turned the lens inward.

A redesign of the Memphis Tech Scene website focused on a deceptively simple question: how quickly can someone understand what’s happening in their own tech community? Events moved to the front. Impact metrics surfaced earlier. Fewer clicks stood between curiosity and participation.

One audience member asked builder JC Smiley a practical, grounded question out loud: How do you measure whether this is working? Traffic, usefulness, outcomes: metrics that move a project from a good idea into accountable infrastructure.

The conversation underscored a shared reality: Memphis isn’t short on talent or activity. It’s short on visibility. Solving that isn’t glamorous, but it’s foundational.

What made this Code & Share memorable wasn’t polish or scale. It was the willingness to show work before it was ready, to ask questions out loud, and to treat experimentation as a communal act.

A junior developer challenged an experimental artist on accessibility—and learned when constraints matter. A founder named the fear that keeps builders from shipping. A researcher shared work far ahead of the curve, trusting the room to grow into it. A platform redesign tackled the unsexy problem of discoverability.

In a city where innovation often happens quietly, Code & Share created the conditions for that work to be seen, questioned, and learned from. Together. And that, more than any finished product, is where momentum actually starts.

Rather than a single lesson, the afternoon surfaced a set of reinforcing ideas about how Memphis tech is learning to grow.

Experimentation Without Perfection
Multiple presenters emphasized that shipping matters more than polish, and that creative exploration has value even without immediate application.
Takeaway: Memphis tech grows when builders give themselves permission to release work before it’s perfect.

Marketing as a Developer Skill
Michael’s attention funnel reframed visibility as part of the build process, not an afterthought.
Takeaway: Marketing literacy strengthens a developer’s ability to turn good work into real-world impact.

Visibility as Community Infrastructure
The Memphis Tech Scene redesign treated discoverability as a solvable design problem, not a social accident.
Takeaway: Ecosystem growth depends on platforms that intentionally connect people across disconnected networks.

Advanced Work Still Matters, Even When It’s Not Fully Understood
Kevin’s oncology AI research raised the ceiling for what felt possible locally, even if the details were complex.
Takeaway: Sharing advanced work expands collective ambition, not just individual expertise.

Humanist Experimentation Expands What Software Can Be
Coriano’s projects pushed interfaces into emotional and sensory territory rarely explored in production work.
Takeaway: Not all valuable software needs a business case; some of it simply needs curiosity.

Intentional Design Reduces Friction
Small UX decisions (what appears first, what takes extra clicks) compound into dramatically different outcomes.
Takeaway: Thoughtful design isn’t aesthetic polish; it’s functional clarity.

Community Learning Through Show-and-Tell
The format rewarded openness over performance and questions over commentary.
Takeaway: Memphis tech benefits from consistent spaces where sharing unfinished work is normalized and valued.

For readers who want to explore further:

Learning doesn’t stop when the room clears.

Join the Memphis Tech Scene newsletter →

Read more community-powered event recaps →