Part 1

Coding: start earlier than you think you need to.

I would recommend learning programming as soon as possible. Scripting and Programming Foundations is not especially good at teaching real-world coding. It uses a language called Coral. Coral is easy to read, but it is not an actual language you are likely to use outside the course. You can understand Coral and still feel like you are starting over when you reach Python, Java, or JavaScript.

The Java, Python, and JavaScript classes are better at teaching the languages, but I still would not wait until you feel fully prepared before starting the project. Open the task early and begin working through it. You will bounce between the course material, documentation, examples, the internet, and your own code. That back-and-forth can feel messy, but it is where the learning actually starts to stick.

Coding is much easier to learn when the code is supposed to do something you care about.

Build small things on purpose.

For HTML, CSS, and JavaScript, make a simple website. A portfolio is a good first project because it can grow with you. You can look at mine at kennethlasyone.org, then build something that feels like yours.

For Python and Java, build the same basic calculator in both languages. Doing the same project twice helps you notice what is shared between programming languages and what is different. You begin seeing the underlying ideas instead of treating every language as a completely unrelated subject.

The basics you generally need first

1. Variables and common data types. Understand integers, strings, booleans, and decimal values such as double or float.
2. Printing output. Know how to display a line of text or a calculated value.
3. if, else if, and else. You need to make the program choose what to do based on a condition.
4. Basic math and operators. Addition, subtraction, multiplication, division, remainders, comparisons, and assignment.
5. Simple functions or methods. Be able to pass in a value, do something with it, and return or print the result.

AI can be your friend or your enemy.

AI is excellent at showing examples, explaining an error, or demonstrating how one small piece of code works. It is also very easy to let it do so much of the thinking that you make faster progress while learning less. I look at it this way: with AI, you can move faster but absorb less. Without it, you move slower but usually learn more. The useful middle ground is to ask for examples and explanations instead of complete projects.

For a practice assessment, you can use screenshots or copied questions to ask an AI how it would solve the problem, then make sure you can repeat the process yourself. That can be especially helpful for coding questions. Keep that assistance to practice and study. A proctored objective assessment is your work alone.

Think of AI like magic at Hogwarts. Till you pass your OWL's, use it only inside the castle wall.

Part 2

Tests: the time limit is usually scarier than the test.

Proctored tests are not too bad. I would still bring your calculator whenever it is allowed. I could have finished most of my assessments without it, but there were moments when it was useful, even on a programming-related test. The same goes for the whiteboard. You may barely touch it, but there is no prize for making the test harder than it needs to be.

Some assessments show a four-hour time limit. I have never needed anything close to four hours. Treat the limit as room to think, not as an estimate of how long the test should take.

The assessments I found most difficult

1. 1
   Data Structures and Algorithms I, C949

   This is commonly treated as one of the hardest classes in the degree, and it deserves focused study.

2. 2
   Applied Probability and Statistics, C955

   This was not especially bad for me, but many students struggle because the practice and objective assessments do not feel perfectly aligned.

3. 3
   Hardware and Operating Systems Essentials, D386

   This one surprised me. The difficulty was less about the subject itself and more about the objective assessment feeling different from the practice assessment.

Do not panic over one weaker competency area.

On many objective assessments, one area marked “Needs Improvement” does not automatically mean you failed. Stronger performance in another area may balance it out. The overall score is what matters. This does not work exactly the same way on every assessment, so always read the course information, but do not assume one imperfect section means the entire test is gone.

Coding assessments with a group of individual problems are a little different. You do not necessarily need every single problem to pass. If you have completed most of them and one or two are consuming all your remaining time, skip them, finish what you can, return at the end, and submit rather than melting into the keyboard. Missing one or two does not automatically mean failure.

Part 3

Projects: they can take the longest, even after you are done.

Performance assessment tasks can take the most time in two separate ways. First, the project itself may take longer than studying for a test. Second, evaluation can take up to several days. When you are accelerating, those evaluation windows matter because a class is not fully finished until the task passes.

This is another area where AI can be helpful and dangerous. You can give it the task instructions and rubric and ask it to explain what each requirement means, help you plan the order of work, or identify what evidence you will need. I would be careful with generated examples and templates. AI tends to produce the same polished, generic structure repeatedly, and a project built from that can look like every other project built from the same prompt.

One of the best AI uses is pre-evaluation.

Once the work is actually yours and you believe it is finished, give the rubric and your completed submission to an AI and ask it to act like an evaluator. Ask it to identify anything missing, unsupported, unclear, or inconsistent. It will not replace the real evaluator, but it is very good at catching a forgotten screenshot, an unanswered rubric item, a mismatch between a diagram and an implementation, or a sentence that claims more than your evidence proves.

My project checklist

• Read the task and rubric separately. They are not always worded the same way.
• Turn every rubric requirement into a concrete deliverable or piece of evidence.
• Name files clearly and use the exact formats requested.
• Verify links, screenshots, diagrams, code, and written explanations agree with each other.
• Do a final rubric-by-rubric review before submitting.

Part 4

Mentors: they are both your friend and your gatekeeper.

Before talking about acceleration, you have to talk about mentors. They are there to support you, but they also control a large part of your experience at WGU, especially when classes are added to your term. Mentors are not all the same. Their communication style, availability, willingness to accelerate, and level of experience can vary a lot.

Your mentor usually follows you across terms, so this relationship matters. If you do not feel supported, cannot reach them in a reasonable time, or your goals clearly do not match the way they manage students, you can request a different mentor through Student Services. I did that personally, and it was the best decision I made during my time at WGU.

Part 5

Acceleration: keep moving, but do not leave a mess behind you.

Acceleration means completing the classes assigned to your term and then continuing into future classes while time remains. After your original term courses are finished, your mentor can move additional courses into the current term.

The general approach is often one additional class at a time, but there is flexibility based on your mentor, the amount of time remaining, your history of finishing what you start, and the types of classes left. I personally receive three or four at a time, then ask for more when those classes have either passed or all of their tasks are already in evaluation.

If you cannot reach your mentor, Tier 1 Student Services may be able to add one class at a time when every other active class is fully completed and passed. That can help in an emergency, but the ideal setup is still a mentor who knows your goals and keeps enough work available that you are not repeatedly stuck waiting.

Expect mentors to become more cautious near the end of a term. WGU does not want you pulling in a course that cannot be completed before the term ends. The closer you get to the deadline, the more important it becomes to choose classes with realistic completion and evaluation timelines.

Part 6

Study tips that actually saved me time.

NotebookLM and similar study tools

You can feed chapters, notes, or practice assessment topics into NotebookLM or a similar study tool and generate flashcards, quizzes, summaries, and practice questions focused on the exact material you are struggling with. This is far more useful than studying everything equally when only two topics are causing trouble.

YouTube

Nearly every class has videos and playlists covering its major topics. Search the course code together with “WGU,” such as D123 WGU. You can often find hours of student explanations, condensed reviews, and topic playlists already organized for the class.

Take the pre-assessment early.

Take the pre-assessment as soon as the class opens. For anything you do not know, make your best guess. Afterward, use the results to identify what you missed and ask for explanations of those topics. Do not change answers during that first attempt just to improve the score. The value is seeing what you know before studying.

When you think you are ready, take it again without help. If you pass comfortably and can explain why the answers are correct, you are probably ready for the objective assessment. Remember that the pre-assessment does not meaningfully change. Taking it ten times can teach you the answer pattern instead of the subject, which creates false confidence. Coding practice assessments may be more directly representative, but you should still understand the process rather than memorize the final code.

Know what you do not know.

This sounds obvious, but it is one of the hardest and most valuable skills. The course material is a study resource, not a ritual you must complete from beginning to end. If you already understand a topic, do not spend three hours proving it to yourself. Focus on the areas you cannot explain, cannot apply, or consistently miss.

Accelerating is mostly the art of being honest about what you already know and what you absolutely do not.

Part 7

My workflow: Test, Task, Test.

For learning, it helps to leave information and return to it. You do not have to finish one class completely before touching another. In fact, I usually do better when I alternate between objective assessments and project classes.

1. 01
   Test

   I open an objective-assessment class, take the pre-assessment, study the weak areas, and reach the point where I believe I could pass it again.

2. 02
   Task

   I stop and complete a performance-assessment class. Once the task is submitted for evaluation, that waiting time becomes useful instead of dead time.

3. 03
   Test again

   I return to the first class and retake the pre-assessment. If I still pass after stepping away, I schedule the objective assessment.

That gap matters. Passing immediately after studying can mean the information is sitting in short-term memory. Passing again after working on something else is a much better sign that the knowledge will still be there during the real test.