What A Full-Stack Software Engineer At A Software Company Wishes They Had Known Before Entering The Software Industry
Channing wishes someone had emphasized the unpredictable nature of the workload as a Full-Stack Software Engineer, specifically the varying degrees of "downtime between projects" which can range from days to months and is useful for learning or refactoring, but also the "very, very short deadlines" that sometimes necessitate rushing. Both of these factors are important to note as one enters the field to become a Full-Stack Software Engineer.
Industry Realities, Project Management, Time Management, Workplace Challenges, Technology
Advizer Information
Name
Job Title
Company
Undergrad
Grad Programs
Majors
Industries
Job Functions
Traits
Channing Robbins
Full-Stack Software Engineer
Software Company
University of Mississippi
N/A
Computer Science
Technology
Product / Service / Software Development and Management
Video Highlights
1. Amount of downtime between projects can vary greatly (days to months).
2. Downtime can be used to learn new things, explore interests, and refactor old code.
3. Project deadlines can sometimes be very short, requiring you to rush.
Transcript
What have you learned about this role that you wish someone had told you before you entered the industry?
It depends on your company and its policies, but for me, it's the amount of downtime between projects. Sometimes we end up with a day or two, or even no downtime. Other times, there might be a month or two, or even longer, between projects.
This downtime is useful because you get to learn new things and explore what you want to work on. You might learn skills that you'll use on a different project later. You can also refactor old code to make things better or more efficient.
The other significant factor is deadlines for projects. Sometimes we get very short deadlines, and we have to rush to complete them.
Advizer Personal Links