Project Work: Table of Contents

All the pieces are here but the most important one: You. Your mind is the missing piece that makes the magic. Nothing compares to the human mind for ability to synthesize, understand, and create. What you read and even the best advice is just a voice in the wind; real results come from adjusting the ideas to fit your situation.

This is all just words until you live it.

Introduction

Java: Intermediate

Intermediate: Learn Java Programming on Udemy

Intermediate: Using Eclipse on Udemy

Reference: Java at TutorialPoint covers all the various language features, if you already know what you're looking for.

You should understand the following before moving on to a project:

  • Variables, conditions, functions, loops
  • Packages, imports, classes, methods, interfaces, inheritance, static, public/private
  • Java Collections API: List, Set, Map, SortedSet; ArrayList, HashSet, HashMap, TreeSet
  • File IO: Reading and writing text files
  • Exceptions and exception handling

Getting Started with a Project

You've learned Java and now you want to do a project. Now what?

A project should demonstrate that you can, at minimum, take data entry from a user, save it, pull it back up later, modify it, resave it, and report on it or retrieve a list of it. That's kind of a boring way to think about software, though, so - add your own spice. What topics are interesting to you? What would be fun or intruiging to work on?

It's great if you can create software for real users. If not, at least create software you find interesting. You'll be living with the idea for quite a while, so it helps if you're curious or passionate about the topic.

You'll be learning about a ton of new things during your project. This page links you to many resources for user interface design, database design and SQL, HTML and front-end web, and so on. You'll need to self-teach many of these topics, using resources that fit how you learn and what you want to know. You won't need everything on this page, of course, but I can't guess which direction you'll go with it, so I provided a variety.

Here's roughly what the project experience will involve.

  1. Idea
  2. Design doc
  3. User interface / screen planning
  4. Database planning and creation
  5. Application coding
  6. Testing and improvements
  7. Demos and Portfolio
Click to see the steps in more detail.

You may be ready to interview before you fully complete your project. That's fine! This is about the learning journey, not the destination of a finished project. In fact, many paid software development roles never see the "end" of a project; the software just keeps getting improvements year after year. So talk with LaunchCode about interviewing after you've had some project experience and feel ready.

Project Management and Technical Resources

The other sections of this page can be found via the Table of Contents above. They're separated into individual pages for easier scrolling.

image credits