Bluffdale ACM

A Bluffdale, Utah community chapter of the computing society

A Chapter That Computes the Tape One Step at a Time

Bluffdale ACM Chapter is a local community of students, engineers and teachers who meet to study computing from the ground up, from the state machines that explain computation to the integrated systems that carry it into real buildings and real institutions. The chapter runs a public lecture series, student programming contests, reading groups and open source mentoring so that anyone in the Bluffdale area can learn in the open. Every activity the chapter hosts is grounded in careful explanation, shared notes and patient practice rather than hype.

The Transition Table of Chapter Work

Six running programmes, each a row in the machine. Read left to right: a state circle names the mode, a read cell shows what the chapter takes in, a write cell shows what it hands back, and the rule column describes the move.

q1 1R

Lecture Series and Seminars

The chapter hosts an open lecture series where working engineers, graduate students and faculty present one careful idea at a time, from finite automata and formal languages to operating system scheduling and distributed consensus. Each lecture is paired with a short seminar in which attendees work through problems together on paper before any code is written, so the ideas land in the hands and not only in the ear. Lecture notes and worked solutions are published after every session as a shared archive that any member can study at their own pace. First time visitors are always welcome, and no prior background beyond curiosity is assumed.

See the lecture programme
q2 0L

Student Programming Contests

Bluffdale ACM Chapter organises friendly programming contests for secondary school and college students across the south valley, built around clear problems and generous time limits so that careful thinking beats frantic typing. Contest sets are written by chapter volunteers and reviewed by two readers before release, with hidden test suites that reward correctness and honest complexity rather than clever shortcuts. After every contest the chapter runs a free solution clinic where teams walk through their approaches and the judges explain the intended reasoning. Prizes are modest, the scoreboard is public, and the goal is always learning in good company.

Read about the contests
q3 1R

Systems Integration Programmes

Our systems integration programmes pair small teams of members with community organisations that need dependable, well documented software and hardware, from inventory tracking for a food pantry to a scheduling tool for a tutoring centre. Teams practice requirements gathering, interface design, data migration and handover, treating every partner as a long term owner rather than a one off client. The chapter keeps an integration handbook that records each decision, cable run and configuration so that a partner is never left holding an undocumented system. This is where classroom theory meets the messy reality of real organisations, and where members learn that quality is measured by what survives the handover.

Learn about integration
q4 0R

Research Reading Groups

Reading groups meet every other week to work through a single paper or book chapter in depth, with one member preparing a short exposition and the rest coming ready with questions. Recent themes have included type systems, memory models, replication protocols and the history of computing machinery, chosen by the group rather than imposed from above. The chapter records reading notes and annotated bibliographies so that newcomers can pick up a thread mid season without feeling lost. There is no performance requirement and no gatekeeping, only a shared commitment to understand the material well enough to explain it to a neighbour.

Join a reading group
q5 1L

Open Source Mentoring

Members who want to contribute to open source are matched with an experienced mentor who helps them choose a tractable first issue, read the project conventions and submit a patch that a real maintainer will accept. The mentoring relationship covers more than code review, including how to write a good issue report, how to ask a precise question and how to receive critical feedback without taking it personally. Chapter mentors commit to one hour a week and to modelling the patient, generous tone that healthy projects depend on. Many mentees later return as mentors themselves, which is exactly how the chapter hopes the cycle will run.

Find open source mentoring
q6 0R

Community Workshops

Short hands on workshops bring computing to audiences who might never attend a formal lecture, including parents, retirees, small business owners and returning students. Typical sessions cover digital safety, spreadsheets for household budgeting, an introduction to version control and a gentle first evening with a text editor and a command line. Workshops are taught in plain language, with printed handouts that participants take home and keep, and with loaner laptops available for anyone who needs one. The chapter treats every workshop as an invitation, never a sales pitch, and measures success by the number of questions asked rather than the number of seats filled.

Attend a workshop

Bluffdale ACM Chapter opens its spring programming contest registration this season, welcoming student teams from every school in the south valley to a day of fair problems, honest judging and generous helpings of pizza. Register early, bring a notebook and a pencil, and come ready to think.

Reserve a contest seat

Why a Chapter Still Matters

Computing is often taught as a private race, but the best engineers the chapter has known learned their craft in rooms full of other people arguing kindly about hard problems. Bluffdale ACM Chapter exists to keep such a room open in the south valley of Salt Lake County, where a growing number of students and career changers are looking for a place to think out loud. The chapter has no entrance examination and no membership tier that gates the interesting material. Anyone who shows up and contributes in good faith is a member for the evening.

The chapter takes its name from the community it serves and its habits from the academic society it belongs to, which means meetings are run on time, notes are published, and disagreements are settled by evidence rather than volume. The lecture series, the contests, the reading groups and the integration programmes all share one design principle: make the reasoning visible so that someone else can check it. That principle is older than any particular machine and it is the reason the chapter still gathers week after week.

None of this work happens without volunteers. Members write problem sets, edit lecture notes, carry equipment into partner offices, moderate reading groups and answer a stranger question with patience. If that sounds like the kind of community you want to build, the chapter would be glad to meet you at the next session, whether you are a first year student or thirty years into a career and looking for a second wind.