Introduction to Development at Full Sail University

The moment programming stopped being abstract for me was week two of Introduction to Development 1 at Full Sail: writing a conditional and watching the browser behave differently based on the condition I'd set. That moment of control, the idea that code makes decisions, is what DEV1001 was built around. This retrospective walks through each week and how the material shaped the way I think about logic, state, and interactivity.

---

Week 1: IDE Setup and Basic Programming Concepts

My thoughts at the time

The first week was all about setting up an environment where code could be written, tested, and debugged. I remember opening an IDE for the first lecture and feeling a mix of intimidation and excitement. The layout, the panels, the terminal, the syntax highlighting, the file tree all felt foreign a bit overwhelming. I quickly learned how the pieces worked together, the system started to make sense.

We also covered basic programming terminology like data types and operators. These concepts were simple on the surface but represented the building blocks of everything that would follow. I found myself becoming more comfortable with looking at logic as a sequence of instructions rather than something abstract.

Retrospective insight

Looking back, this week gave me a crucial foundation. Understanding how to navigate an IDE and organize files properly became essential in every course that followed. Learning the basic terminology early prevented confusion later when topics became more advanced. The biggest benefit was gaining confidence in my ability to read a function, understand its makeup, and be able to make meaningful changes or optimizations to it later on.

---

Week 2: Conditional Logic and Decision Making

My thoughts at the time

Week two introduced conditional logic, which was the moment programming started to feel real. Writing code that made decisions felt powerful. I could instruct the computer to behave differently depending on a condition, and that opened up new possibilities. I remember practicing with if and else statements repeatedly until the structure clicked.

This was also the week I started manipulating basic elements and exploring how user input could change the flow of a script. It forced me to think more critically about cause and effect, and how each piece of logic leads to a different outcome. This is the point where I realized what makes a great developer. It isn't in our ability to memorize complex syntax but our ability to use coding concepts to solve problems.

Retrospective insight

Conditional logic has shown up in every project I have worked on since. It forms the backbone of most interactive behavior. Understanding it early helped me tackle more advanced concepts like state management, event handling, and data validation later on. This week also developed my problem solving mindset, thinking step by step and planning out logic before writing any code.

---

Week 3: Variables, Math, and DOM Interaction

My thoughts at the time

Week three brought variables into the picture, which made the code feel far more dynamic. Storing values, manipulating them, and using them later gave me a sense of how programs actually hold and process information. Combining variables with math expressions made everything more versatile and helped me understand how data flows in a script.

This was also when the DOM came into play. Seeing how JavaScript could reach into an HTML document and change content or styling in real time was a breakthrough moment. It made everything I had learned in earlier courses feel more connected.

Retrospective insight

Working with variables and the DOM became a stepping stone to more complex ideas such as component-based frameworks, reactive updates, and dynamic rendering. Learning this early helped me understand how the browser interprets changes and why certain approaches are more efficient. This week reinforced that JavaScript is not just about calculations. It is about interacting with the page and responding to what the user does.

---

Week 4: Forms, Synthesis, and Building a Complete Project

My thoughts at the time

Week four focused on bringing everything together. Forms were introduced, which added a new level of interactivity. Collecting user input and doing something meaningful with it felt like the first step toward building real applications. It also made the logic more complex, because different types of input required different handling.

The final project this week was the first time I had to think carefully about structure, logic, and user flow all at once. It pushed me to combine every concept I had learned throughout the course. The only flaw in how this was delivered is a better explination as to what happens once the user clicks submit on the form. That answer wouldn't come for almost six more months of class.

Retrospective insight

This synthesis week showed me how foundational principles stack together to solve larger problems. Handling user input, updating content, validating data, and structuring logic all came into play. It was my first real taste of building something functional from scratch. This experience made later courses easier because I had already learned how to break down a problem, map out the logic, and build a solution step by step.

---

Closing Thoughts

Introduction to Development 1 was a turning point in my learning journey. It transformed the way I thought about websites and applications by revealing the logic behind the scenes. This class laid the groundwork for everything I would encounter later, from event-driven programming to full stack development. The problem solving skills, debugging techniques, and logical thinking I developed here continue to influence how I approach challenges as a developer.

---

Where I Use This Now

Conditional logic, DOM manipulation, and forms were the three things this course introduced that I still use every single day. The contact form on this site, the filter logic in my portfolio filtering system, and every event listener in Typing Force trace back to the foundations built in this class. The "code makes decisions" framing wasn't just a beginner concept. It's still the mental model I use when debugging why a component isn't rendering what I expect.

---

Code: The Conditional Logic Pattern That Made It Click

The if/else pattern is trivial on paper but the moment it connected for me was building something where the output visibly changed:

function updateStatus(score) {
  const statusEl = document.getElementById('status')

  if (score >= 90) {
    statusEl.textContent = 'Excellent'
    statusEl.className = 'status--high'
  } else if (score >= 60) {
    statusEl.textContent = 'Passing'
    statusEl.className = 'status--mid'
  } else {
    statusEl.textContent = 'Needs work'
    statusEl.className = 'status--low'
  }
}

And the form input pattern that introduced DOM interaction:

document.getElementById('submit-btn').addEventListener('click', function () {
  const input = document.getElementById('user-input').value.trim()
  if (!input) return
  document.getElementById('output').textContent = `You entered: ${input}`
})

Small, immediate, and visible feedback. That's what made the logic feel real.

---

FAQ

Is JavaScript hard to learn as a first programming language? Harder than Python for pure syntax, but easier than most because the feedback loop is immediate. You write code, open a browser, and see if it worked. That tight loop is one of the best environments for learning conditional logic and debugging.

How long does it take to get comfortable with JavaScript fundamentals? Comfortable enough to build small interactive features took me about two months of structured coursework. Comfortable enough that I wasn't constantly second-guessing syntax took probably six months of building real things with it.

What's the difference between JavaScript and HTML? HTML defines the structure and content of a page. JavaScript adds behavior. HTML describes what things are. JavaScript describes what they do when a user interacts with them.

Do you need to know math to learn programming? Not really. The math that shows up in most web development is addition, subtraction, comparisons, and the occasional percentage calculation. The logical thinking matters more than arithmetic.

Credits and Collaboration

A huge thank you to Esther Allin for designing the blog banner art! If you're looking for a professional digital media specialist, Connect with her on LinkedIn!