At Georgia Southern University in Statesboro, Georgia, my 2011–2012 Computer Science studies gave programming its proper shape. Code stopped being a collection of syntax exercises and became a discipline: understand the problem, model it clearly, weigh the tradeoffs, then build something sturdy enough to earn its keep.
The lasting result was a durable way of thinking. Data structures, discrete mathematics, statistics, probability, calculus, C, C++, R, Visual Basic, and systems programming each taught a different lesson; together, they made software, data, and difficult technical problems feel connected rather than separate.
Georgia Southern was where academic discipline became a practical habit—one that later supported software engineering, data science, and machine learning work. The point was not to chase a buzzword. It was to stay with a hard assignment long enough to break a large question into smaller solvable pieces. By the end of 2011–2012, I was learning more than code: structure, logic, abstraction, and the patience to work without shortcuts.
The courses mattered most when they began reinforcing one another. Data structures gave information shape. Algorithms offered a route through the problem. Discrete math strengthened the logic; statistics and probability made data interpretable; calculus sharpened intuition for change; and programming languages made the work executable. This was not a random course list. It was the start of a connected technical worldview.
The most durable part of Georgia Southern was not any one assignment. It was the training effect of staying with difficult material until it became clear. Statesboro taught me focused problem solving, the discipline of working through concepts instead of skipping ahead, and a useful truth: technical confidence is usually earned through repetition more than raw talent. Persistence became part of the toolkit.
