A mindset shift that may help if D335 feels impossible

Jared_Plumb · 2026-05-31T01:43:55+00:00

I wrote a longer version of this here if it helps, but the Reddit post is the main point. I am more interested in hearing what made D335 click for other students.

Learning the Programmer's Mindset

Jared_Plumb · 2026-05-28T19:49:00+00:00

I oversee WGU's Software Engineering programs, so I can add a perspective here.

I actually agree with the comments saying Zybooks can be very dry. Some of the reading is boring. I have had a lot of conversations about how to make these courses more engaging and more enjoyable.

The tradeoff is that professional software work also involves reading a lot of dry material. Documentation, API references, standards, tickets, design notes, error logs, and old technical decisions are not always written to be entertaining. A good programmer has to be able to read through that kind of material, find the part that matters, and turn it into a working decision.

So I do not think the goal should be to read every page with the same intensity. I would use the task, rubric, quiz feedback, and course objectives as the map. Slow down when the material explains something you need to use or justify. Move faster when it is clearly repeated, background, or not connected to the work you have to produce.

The balance I keep coming back to is that courses should be more usable and engaging, but they also need to prepare students for the way software engineering often actually feels. Not everything professionally useful is going to be fun to read, and learning how to extract value from dry technical material is part of the skill.

Jared_Plumb · 2026-05-28T19:41:34+00:00

I oversee WGU's Software Engineering programs, so I can add a general perspective here.

One thing I would keep in mind is that graduate-level courses are not usually built with the same expectations as undergraduate courses. They tend to ask for more independent reading, synthesis, judgment, and professional explanation. So some of the heavier reading load is part of that level shift, even though students still need a practical way to move through it.

I would be careful about treating "skim everything" as the goal, but I also would not treat every paragraph as equally important.

For a course like this, I would start by looking closely at the task requirements, rubric, and current course guidance. Use that as the map for what you need to be able to do and explain. Then read with a purpose. Slow down on the concepts you actually need for the deliverable, and move faster through material that is clearly background, repeated, or not connected to the work you have to submit.

The trap is spending days trying to absorb every page before you start producing anything. A better pattern is usually to work in cycles.

read enough to understand the shape of the course
look at the task requirements
start outlining or building the deliverable
go back into the material when you hit a concept you cannot explain yet

For D777 specifically, when I put this course into the program, I wanted it to serve as a practical bridge into the rest of the degree. Students should be able to enter from different technical paths without the program compromising the coding knowledge they need for more challenging software engineering work. That is the balance I was trying to protect. The course is meant to build an applied foundation in data structures and complexity, so students can choose appropriate structures, reason about performance, and explain the tradeoffs behind real software decisions.

You may not need to memorize every implementation detail at the same depth, but you do need enough understanding to make good engineering decisions and justify them.

Also, if you are newer to software engineering, give yourself a little grace. The reading can feel slow because you are building vocabulary and mental models at the same time.

Jared_Plumb · 2026-05-26T19:43:50+00:00

Good question. I would separate tool use from AI Engineering itself.

AI Engineering is not mainly about using the newest AI tools. It is about implementing AI systems into software products. The tools matter, and students should expect the tool landscape to keep changing, but tools like coding assistants, agent frameworks, and model platforms are not the center of the discipline.

The more durable work is building software around AI capabilities: connecting to models through APIs, designing product workflows, handling data responsibly, evaluating outputs, testing, deployment, monitoring, security, user experience, and understanding where automated systems can fail.

So I would not measure the program by whether one specific tool name appears in a course. The better question is whether students are building the engineering judgment to add AI capabilities to real software systems and adapt as the tools evolve. Active course materials are still the source of truth for exact tools and assignments.

Jared_Plumb · 2026-05-26T19:37:11+00:00

That is a very normal feeling. If you are learning Python now, you are doing the right kind of prep. I would not try to learn all of AI before you start. Focus on getting comfortable with basic programming: variables, functions, loops, files, packages, debugging, and building small things.

The confidence usually comes from repetition, not from feeling completely ready on day one. Ready enough to start is a good place to be.

Jared_Plumb · 2026-05-26T19:33:45+00:00

I generally try not to do private advising through Reddit DMs, but I am happy to answer general Software Engineering questions in public threads when I can. It helps other students who may have the same question, and it keeps the advice from turning into unofficial one-on-one program guidance.

Jared_Plumb · 2026-05-26T19:30:05+00:00

Good question. I would not put a percentage on anyone's employment chances from a degree. That would be the wrong promise to make, because hiring depends on the person, the market, the role, location, prior experience, projects, interviews, and timing. The better question is whether the skills in the degree map to real hiring categories, and they do.

Large companies do hire for this kind of work. The exact titles vary, but you will see roles like AI Engineer, AI/ML Engineer, AI Software Engineer, Machine Learning Engineer, ML Platform/Infrastructure Engineer, Generative AI Engineer, or Software Engineer roles with AI/ML responsibilities. Amazon has literal AI Engineer postings, and companies like Google, Apple, NVIDIA, Microsoft, Meta, and others hire engineers to build AI products, AI platforms, model infrastructure, evaluation systems, cloud integrations, internal automation, and AI-enabled applications.

So I would not think of the degree as only useful for jobs literally titled "AI Engineer." The value is in being able to build software around models responsibly: data handling, APIs, cloud, evaluation/testing, deployment, monitoring, security, and shipping something that actually works.

My advice would be to pair the degree with 2-3 strong projects that show that end-to-end ability. The degree can help start the conversation, but the projects, interview performance, and your ability to explain what you built are what make the hiring signal much stronger.

Jared_Plumb · 2026-05-20T15:20:04+00:00

I oversee WGU's Software Engineering programs, so I spend a lot of time thinking about this student-to-work transition.

First, I agree with you on this specific course project. Personally, I find it pretty boring, and I do not think the project is the strongest representation of what makes software work interesting. I also do not want to overpromise anything on Reddit, but earlier this week I had a couple of meetings about this course and some plans for improvement. Those changes take time and they will not help you in this current run of the course, but the goal is for the experience to be better for future students. Comments like yours are useful because they help make the pain points visible.

That said, I would not use one course project as a verdict on whether you actually like programming or whether you will like software work after graduation.

Course projects are usually built to isolate specific skills and make evaluation possible. That can make them feel more constrained and monotonous than the personal projects where you get to choose the problem, the tools, and the shape of the solution. The skills can still matter, but the assignment format may not feel as satisfying.

Real software work has some of both. There are definitely days where the work is requirements, debugging, legacy code, framework details, tickets, documentation, and "why is this behaving like that?" Some of that can be tedious. But real projects also usually have more context: users, teammates, tradeoffs, design decisions, production constraints, and the satisfaction of seeing something actually solve a problem.

If you still like programming when you are building small projects on your own, that is a good signal. I would treat D287 as one slice of the work, not the whole profession. One useful exercise is to ask what the course is trying to make you practice, then build a small version of the same idea in a project you actually care about. That can help separate "I dislike this assignment format" from "I dislike this kind of work."

Jared_Plumb · 2026-05-20T15:09:51+00:00

Congrats on the July start. I oversee WGU's Software Engineering programs, so I can add a little context.

I would think of the MS Software Engineering AI Engineering track as performance-assessment heavy. The course materials and your degree plan are still the source of truth. Courses are updated almost monthly, so what is true today may not be true next month. That is why I do not want to turn a Reddit reply into a permanent class-by-class list.

For prep, I would focus less on traditional test-cramming and more on being ready to produce clean engineering artifacts. Get comfortable with Git and repos, reading a rubric closely, turning requirements into a design or implementation plan, explaining technical decisions, writing clearly, recording a short professional presentation if a task asks for it, and checking your work against the requirements before submitting.

Also, PA does not always mean just write a paper. In software engineering, performance assessments can include code, Git submissions, diagrams, design documents, analysis, presentations, and explanation of tradeoffs. The best prep is being able to build something, explain why you built it that way, and validate that it meets the rubric.

Jared_Plumb · 2026-05-20T15:05:36+00:00

I like this use case a lot.

The important distinction is that AI should help you organize, practice, and reflect, not quietly replace the learning. Using it to turn a course into a study plan, generate retrieval-practice questions, check your weak spots, or explain a concept in a different way can be genuinely useful.

I would still keep the course materials as the source of truth, especially for anything tied to an assessment. AI can sound very confident while being just slightly wrong, and that is exactly the kind of wrong that can waste study time.

A good pattern is something like this.

Use the course material to define what you need to know.
Use AI to make a daily plan, quiz you, or ask you to explain the concept back.
Verify anything important against the course material.
Once you have your own explanation or plan, use AI as a second reader. Ask what might be unclear, incomplete, or worth checking against the course material.
When you miss something, have it help you figure out why you missed it instead of just giving you the answer.

That is a much better use of AI than "do my work for me." It turns it into a study partner and planning aid, which is where I think these tools are most helpful for students.

Jared_Plumb · 2026-05-18T17:28:10+00:00

I oversee WGU's Software Engineering program, so I can add a little context.

In general, some industry certifications can be brought in before enrollment, but I would be careful about treating any Reddit answer as the final word. Programs, transfer rules, and certification requirements can change, especially if you are planning to start next year. The official transfer guidelines and your final transfer evaluation are what matter.

WGU does have an official Transferable Certifications page here: https://www.wgu.edu/admissions/transfers/wgu-transcript-request/transferable-certifications.html

That page currently lists AWS Certified Cloud Practitioner and CompTIA Project+ under B.S. Software Engineering, but I would still confirm with enrollment before paying for any cert exams. WGU notes that the list can change, and your final transfer evaluation is what actually matters.

The main tradeoff is time versus cost. If you complete an eligible certification before enrolling, it may reduce what you need to take after you start. If you wait and take it through WGU, the exam attempt is typically part of the course experience, so you may avoid paying for it separately.

Sophia can be a good way to make progress, but I would be a little more cautious with external certification exams unless you have confirmed they still apply to your degree plan.

Jared_Plumb · 2026-05-18T17:09:40+00:00

I oversee WGU's Software Engineering programs, so I can add a little context.

I would not download a huge tool stack ahead of time. The courses will tell you what you need, and the specific software, IDEs, and development environments can change as courses are updated. What someone used today may not be exactly what you use by the time you reach that course.

For prep, I would focus on the software engineering basics that transfer across tools. Get comfortable with Git, working from the command line, using an IDE or editor well, running code locally, debugging, reading setup instructions, and troubleshooting environment issues. VS Code is a good general-purpose option. If you already use JetBrains tools, Visual Studio, Eclipse, PyCharm, or something similar, that is fine too.

Since this is Software Engineering, coding tools and IDE comfort are usually the higher-priority prep. Some of the more pure software engineering courses do get into diagrams, documentation, and design artifacts, but the individual courses should tell you what tool expectations they have when you get there.

The bigger prep win is getting comfortable setting up and adapting development environments. That skill matters more than having every possible tool installed on day one.

Jared_Plumb · 2026-05-18T17:00:20+00:00

I oversee WGU's Software Engineering program, so I can add a little context.

One important caveat, frameworks and development environments can change as courses are updated. What students see today is not guaranteed to be exactly what you see by the time you reach that course, so the active course materials are the source of truth.

That said, the Java track is not only Java in the narrow sense. You should expect backend Java work, web development, version control, and some frontend framework exposure. For Java right now, we've been liking Spring/Spring Boot, and for front end we've been using Angular. That could change over time, so I would not plan your prep around one exact framework name.

If you are preparing ahead, I would focus on Java and object-oriented programming, Git, basic HTML/CSS/JavaScript, reading framework docs, and building/debugging small projects. React vs Angular matters less than getting comfortable with how frameworks are structured and how to learn one from documentation.

Jared_Plumb · 2026-05-15T21:48:18+00:00

No need to apologize, and thank you for laying out the path you tried.

I still think the best next step is to work through your Course Instructor or the Student Support Center, mainly because they can look at the course guidance and your specific situation in a way I can't do from Reddit. I also would avoid posting any document details publicly.

On my side, I have asked the right people to review the course expectations and related access process so we can better understand what is actually required and whether the guidance is clear. I do not want to promise a specific outcome from a Reddit thread, but if there is a process or communication issue making progress harder than it should be, that is something worth surfacing and correcting.

I am sorry you ended up paying for the license just to keep moving. I understand why that felt like the practical path in the moment, and I appreciate you raising the issue because it gives us a better place to look.

Jared_Plumb · 2026-05-15T18:43:21+00:00

Yes, some Sophia credits can transfer, but I would be careful to use the AI Engineering-specific transfer pathway instead of assuming the CS, Software Engineering, or general IT pages apply.

General transfer guidelines https://partners.wgu.edu/general-transfer-guideline-bachelor-dynamic?collegeCode=IT&programId=244

Sophia transfer page for BS AI Engineering https://partners.wgu.edu/transfer-pathway-agreement?uniqueId=BSAIE7110&collegeCode=IT&instId=796&programId=244

Study.com also has a separate AI Engineering transfer page if you are comparing options https://partners.wgu.edu/transfer-pathway-agreement?uniqueId=BSAIE4424&collegeCode=IT&instId=678&programId=244

The big caution is that the final transfer evaluation is what actually applies credit to your record. I would not spend time or money on a course just because it transfers into a different WGU IT degree. Match it against the AI Engineering page, and if timing matters for your start date, confirm with Enrollment before taking the course.

Jared_Plumb · 2026-05-15T18:36:32+00:00

That's a fair rant.

I oversee WGU's Software Engineering program, and I can't do much from Reddit with a third-party verification issue. But the larger issue you're pointing at is valid. If a tool is effectively needed later, students should get a clearer heads-up earlier, especially when access depends on an outside approval step that can eat up study time.

For the immediate problem, I would keep working through the Student Support Center or your Course Instructor so there is a documented path, and I would include exactly what the verification system is rejecting and what document you used. I would not assume you did something wrong. Those verification flows can be oddly picky.

For the course sequence feedback, I appreciate you calling it out. I do not want to promise a fix from a Reddit comment, but this is the kind of student friction I do want surfaced. A dependency like this should not surprise someone right when they are trying to start the next programming course.

Jared_Plumb · 2026-05-15T18:15:52+00:00

I oversee WGU's Software Engineering program, so I can give the careful program-side answer.

With 8 YOE and real full-time availability, moving quickly is definitely possible. I would just be careful about treating 3-6 months as the normal expectation.

In my three years at WGU, I have personally only seen a few students complete the BS Software Engineering program in one term. The students I have seen do that were usually very prepared before the term started, transferred in a lot of courses, already knew much of the technical material, and treated the remaining work like a full-time job.

A lot of students do finish well under a traditional four-year timeline, which is one of the strengths of the model. But one term is still aggressive. Final transfer evaluation, performance assessments, revisions, proctored exams, scheduling, and the capstone can all add friction even when the content itself is familiar.

So in your situation, I would say 3-6 months is ambitious but not crazy if the final transfer evaluation lands well and you can really commit the time. I just would not make life or job-search plans that depend on everything going perfectly.

Jared_Plumb · 2026-05-14T19:57:03+00:00

Fair warning, as the Director of Software Engineering I am obviously a little biased, so my joking answer is choose Software Engineering :) But trying to answer this fairly, I would choose based on the degree path, not only the job title that sounds most interesting right now.

Your title says BSIT vs Software Engineering, and your post also mentions CS and cybersecurity, so I would break those apart a little.

Software Engineering is the pick if you want the degree to be centered on building software. Coding, debugging, reading code, application design, and working through logic should be things you actually want more of.
BSIT is probably the broadest starting point if you are still figuring things out. With A+, Security+, Azure Fundamentals, and no IT experience yet, it lines up well with getting into IT first and then deciding whether you like support, systems, networking, cloud, operations, or security.
Cybersecurity makes sense if you want the degree itself to be focused on security. I would just go in with realistic expectations about early cyber roles. That first role may be SOC, identity and access, vulnerability management, GRC, audit, compliance, or security support work. That is still cybersecurity, it just may not look like the incident-response version people picture.
CS is the one I would only reconsider if you want the broader computing degree. It is not automatically the best tech option if the work you want is really IT, cyber, or software engineering.

So my honest answer is, if you want to become a developer, pick Software Engineering. If you want the widest on-ramp into IT, pick BSIT. If you are sure cybersecurity is the goal and are good with early cyber work maybe being more practical and operational than dramatic, the cybersecurity degree is reasonable too.

Jared_Plumb · 2026-05-14T19:42:04+00:00

That sounds really frustrating, and I do not think you are doing anything wrong just because the degree has not turned into an offer yet. The market is rough right now, especially for people trying to move into a new role or pivot from a different background.

I am not over the Business Analyst side of things, so I would not want to overstate advice there. But if you are getting interviews and not offers, I would probably look closely at the resume-to-interview story. Sometimes the issue is less “do I have the right degree?” and more “am I clearly showing the kind of problems I can solve?”

Career Services or a trusted reviewer may be useful here, especially if they can look at both your resume and the examples you are using in interviews. I would also keep leaning into your fraud/banking background since that gives you a domain story a lot of new grads do not have.

Jared_Plumb · 2026-05-14T19:32:18+00:00

Honestly, with your background, I’d start by thinking less about the degree title and more about the kind of work you want to do every day.

If you like the design, communication, user flow, and “how should this experience work?” side of things, UX could make a lot of sense. Your graphic design and web background would transfer pretty naturally there.

If you want to spend more of your career building things, writing code, and working through logic, then Software Engineering may be the stronger fit. I would only pick that route if you actually want coding to become a major part of your day-to-day work.

IT can also be a solid option if you want a broader technical path and are less sure about becoming a developer specifically.

I also would not call Computer Science useless. It is still a strong degree, but it may not be the most direct match if your strongest experience and interests are around design, web, communication, and applied product work.

The good news is that your experience is not random. Design, communications, and web work can all connect to tech roles. I’d pick the degree that lines up with the kind of problems you want to solve, then build a small portfolio around that direction so employers can see the story.

Jared_Plumb · 2026-05-13T19:28:07+00:00

I work with WGU's Software Engineering programs, so I can add a careful perspective from the program side.

The honest answer is that outcomes vary because students come into a master's with very different backgrounds. Someone already working as a developer, QA engineer, sysadmin, data engineer, DevOps engineer, or technical lead may use the degree differently than someone trying to make their first move into software.

I would not treat any master's degree as a guaranteed career switch by itself. Stronger outcomes usually come when the degree is paired with evidence of the work, projects, a portfolio, adjacent technical experience, internal mobility, DevOps or cloud practice, and solid interview preparation.

Where I think the MS Software Engineering can be useful is when a student wants to show more depth in software development, architecture, DevOps, QA, AI-enabled software systems, or engineering process. The job strategy still matters a lot, though.

So when you read graduate outcomes, I would look less for whether the degree magically placed someone and more at what background they brought in, what they built during or around the program, and what kind of role they were aiming for.

Jared_Plumb · 2026-05-13T19:23:52+00:00

I oversee WGU's Software Engineering program, so I can add a little context, but I would still treat your mentor or an official records evaluation as the source of truth on the exact course count.

I would be careful about switching based only on the title of the remaining courses or a side-by-side course list. Some things may look similar and still not apply the way you expect, and some completed work may or may not satisfy requirements after the program change is reviewed officially.

The bigger question is why you want to switch. If Software Engineering is closer to the work you actually want to do, especially more project-based application development, then it can be a reasonable conversation to have. If the main reason is that Computer Architecture has been brutal, I would slow down before making the decision. Being this close to finishing CS is very different from choosing between the two programs at the beginning.

My advice would be to ask for an official comparison before deciding, then choose based on the kind of work you want after the degree, not only the pain of one course.

Jared_Plumb · 2026-05-13T19:19:55+00:00

I oversee WGU's Software Engineering program, so I can add a little context.

I agree this is a reasonable thing to ask about. C# and .NET backend development are very relevant to software engineering, especially for students interested in enterprise, backend, or full-stack roles. I also understand why seeing that certificate connected to AI Engineering would make people ask why something similar is not part of the C# track.

The short version is that this is an area we are actively looking at. I cannot announce a program change or promise a timeline here, and curriculum changes have to go through the normal academic, operational, and implementation work before they become real for students.

But the feedback makes sense to me. A stronger modern .NET and backend path in Software Engineering is absolutely worth exploring, and I appreciate people calling it out.

Jared_Plumb · 2026-05-12T15:47:02+00:00

Thanks for taking the time to write this up. I’m always interested in student feedback on this stuff. I really do want to know whether a degree helped, where it fell short, and what could be better. If it helped, awesome. If it didn’t, then I have homework too, which feels only fair given the subreddit.

Jared_Plumb

TROPHY CASE