Environment Setup, Safety, and Programming Fundamentals

Why Your Environment Matters

Before you write a single line of code, your tools and your workspace both need to be set up correctly. A broken environment wastes hours of troubleshooting time. An unsafe workstation causes real physical harm over weeks and months of daily use. This lesson walks you through installing Python and R, configuring the software you will use throughout this program, and auditing your workstation so it supports long, healthy work sessions.

Installing Python with Anaconda

Anaconda is a free, open-source distribution of Python that bundles the interpreter, over 250 scientific packages, and the conda package manager in one installer. Download the current Individual Edition from anaconda.com and choose the installer that matches your operating system (Windows, macOS, or Linux). Accept the default installation path unless your institution specifies otherwise. When the installer finishes, open Anaconda Navigator or launch a terminal and type `conda --version` to confirm the install succeeded. Record the version number in your lab log.

Jupyter Notebook is included with Anaconda. Launch it from Anaconda Navigator or by typing `jupyter notebook` in a terminal. A browser tab should open showing your file system. Create a new notebook, select the Python 3 kernel, and run a test cell — if output appears, Jupyter is working.

Installing R and RStudio

R is a free statistical computing language maintained by the R Foundation. Install R first from cran.r-project.org (the Comprehensive R Archive Network), then install RStudio Desktop from posit.co. RStudio is an integrated development environment (IDE) that makes R much easier to use; it will not run without a working R installation underneath it. After installation, open RStudio and type `R.version.string` in the Console pane, then press Enter. Record the version string in your lab log. Also verify that Jupyter can use an R kernel by installing the IRkernel package inside R (`install.packages("IRkernel")` then `IRkernel::installspec()`).

Workstation Safety — Ergonomics

Data professionals spend most of their working day seated at a computer. Poor ergonomics lead to musculoskeletal disorders including repetitive strain injuries of the hands and wrists, neck and shoulder strain, and lower-back pain. OSHA's Computer Workstation eTool identifies the key adjustment points you must address:

• Monitor height and distance. The top of the screen should be at or slightly below eye level, roughly an arm's length away. Tilting your head up or down for hours strains the cervical spine.
• Seating and posture. Adjust seat height so your feet rest flat on the floor (or a footrest) and your thighs are roughly parallel to the floor. Your lower back should be supported by the chair's lumbar support. Avoid slumping.
• Keyboard and mouse placement. Keep them at a height that lets your elbows stay close to your body at approximately a 90-degree angle, with wrists in a neutral (straight) position.
• Cable management. Cables on the floor create a trip hazard. Route cables along desk legs, use cable ties, or run them through a cable tray. This is also an electrical safety concern: damaged insulation from cables being stepped on or pinched can cause shock or fire.
• Lighting. Position monitors to avoid glare from windows; use window blinds or monitor hoods as needed to prevent eye strain.

Workstation Safety — Electrical

Data workstations draw meaningful electrical loads. Follow these basic rules:

• Use a surge protector with a joule rating appropriate for your equipment. A surge protector guards against voltage spikes that can destroy hardware and potentially start fires. Do not daisy-chain power strips.
• Do not overload circuits. Know the amperage of the circuit your workstation is on and keep total load within safe limits.
• Inspect cords regularly. Frayed, cracked, or pinched cords must be replaced, not taped. Report damaged equipment to your instructor or facilities staff immediately.
• Lockout/Tagout (LOTO). If you are ever asked to open a computer case or work on powered equipment during this program, follow your institution's LOTO procedure. De-energize, lock, and tag the circuit before touching internal components. OSHA's LOTO standard (29 CFR 1910.147) applies to the control of hazardous energy in workplaces.

Your First Scripts

The final activity is writing a simple script in both Python and R. This confirms your environment works end-to-end and introduces the basic syntax of each language. Your script should print your name, today's date, and one sentence describing a data analytics task. In Python, use the `datetime` module for the date. In R, use the `Sys.Date()` function. Both scripts will be pushed to the class repository, giving you your first experience with version control.

Lab Log and Sign-Off

Your lab log is a written record of what you installed, what versions you have, and what you found and fixed during your ergonomics audit. Treat it like a professional technician's work order — clear, dated, and specific. Your instructor will review and sign off on your installation checklist. You must also document at least two ergonomic corrections with before-and-after photographs. Both scripts must run without errors. All three items are required to pass this lab.