Reality of Software Development

I will make more videos about the mindset to learning to code, other careers in tech other than SWE, and how I escaped tutorial hell.

Music
I have paid for the song BSGUEST_0907398001682264409

[Mars-ocgq]

Not every company does sprints, pair programming, or has experienced programmers on the team. Pick the company and role very carefully and watch out for red flags

[m_hussain_mustafa]

This is actually a pretty good video. I've been a SWE for 5 years now and this video paints quite a realistic image of what a day in the life looks like for me. Way to go champ.

[drmonkeys]

Thank you for providing an actually accurate representation of what it's like. An important bit to highlight is that when you're starting out it'll take a long while to get your bearings on things. Like when I first started my first ticket (which I didn't even start untill about another week in) took me around a week and a half and my PR for it literally changed one line of code. Especially if it's your first time working in a big codebase it's pretty overwhelming to understand everything that's going on, but eventually it gets easier (especially in healthy comps that have a culture of collaboration and pair programming)

[theastuteangler]

Loved it. Pleasant style, realistic outlook, no bs. Very Fireship-esque. More please.

[amcmillion]

I'm a Full Stack Engineer and this is one of the most realistic videos I have seen on what being a SWE is actually like.

[colbr]

I worked as a Software Engineer for a number of years for a very large corporation. At maximum 20% of the time would be spent on coding. Many of the items you mention were practiced there too. With more focus on design up front and directing changes to focus on measurable business results. Lots of things never ever get visited, because they don't really benefit the customer or the business.

[julio-dev]

I find this very useful, as someone who's getting into this world, watching a clear and concise video of the things I will be doing in a work environment makes me realize the things I have to improve beyond coding.

[findhard]

It's impressive how companies can suck the fun out of any job.

[IsaacA]

This is pretty accurate for where I work. Definitely plenty of customer support tickets, estimation is usually done by more senior devs or tech leads. Stand up is every morning, showcase, retro, and planning are once a month, I think. We also have fortnightly catch-ups with our team leads, or managers. We're also doing some squad experimentation, if there is a big blocker we have breakout rooms to discuss this issue and can attend that to either help out or learn something. This is to prevent soaking up standup time with issue related rabbit holes.

[BarisPalabiyik]

This was very accurate and funny. Most of the lingo and way of working feels complicated at start, but then you realize it's just some simple steps you need to follow at the end of the day.

[LunaticEdit]

To be fair, this is actually the _ideal_ software developer experience. It can be much better or worse. An example of "worse" is if you have "QA driven design" where qa "bugs" are QA telling the devs how to make the program work, or having code that is nested 15 levels deep in an unreadable blob of garbage logic that you can't change without breaking 6 other things. Usually problems like that can be resolved if the team pushes to do things the right way though!

[nickaguirre]

This is pretty much 100% accurate. I'm really fortunate to be working at a company whose management style maximizes dev time as much as possible and is generally pretty understanding of dev time/application needs.

[alex_lll]

Nicely explained.

This is what a well organized workflow looks like. In my 15 years career spread across more than a dozen teams - I worked like that maybe like in 3 of them. Others were fifty shades of chaos.

[codingcompiled]

Moving from a Junior developer job where I was tasked to do the grunt coding to then starting to have to have client meetings is definitely a work shift for me I have to face at the moment. But then again working in agency where your time can be billable to a client in comparison to a product is quite different.
Brilliant video, really clearly laid out.
Totally agree with the Bitbucket sentiment. 😂

[BKXIX]

Thank you, this is the first video I've seen that seems to give a more realistic scope of what I'll be doing if I get into software development.

[latedriver]

This video was an absolute gem and earned you a sub. I'll be looking out for more videos in the future. To comment on your description, I would agree that this reminds me very much of a fireship video.

[jesseElira]

I just finished a NASA internship this May after getting my Bachelors Degree in Computer Science. And I can say this is 95% what my days was like. Also, thankful to have worked with a wonderful and supportive team for my learning and development.

[stillcinematic]

You nailed it. I find it depends on the team and developer for pair programming. My current position has no pair programming because all of the experienced developers keep to themselves.

[dotunn]

Just started my first job, and you’ve 100% described the process there.

[charaznable]

This is exactly what I experience in my job! Very accurate video