Very refreshing to see actual real details in this type of video instead of "Hey I wake up and get out of bed and drink coffee and walk my dog and then go to work and code and go home THE END" Thanks for the vid 👍

@filburtcioglu3729

Жыл бұрын

Best comment ever

@crusaderpr7683

Жыл бұрын

extremely accurate

@Teksnek42

Жыл бұрын

Literally just rephrased the first 45 seconds lmao

@tex6929

Жыл бұрын

I mean it’s about what you want. When you say “day in the life” it’s about everything in that day.. if you want “what does a dev do all day” then that’s something completely different

@The242511

Жыл бұрын

Yes, and this is how it's really done

I did an internship about 6 months ago and this was literally the process that I learned throughout my 3 months. I really wish I saw this before…Great content…

Such a realistic take - I was expecting something vague, but this is extremely close to what I've seen in DevOps in the wild. I appreciate this a ton, even if only because it validates a lot of my takes on DevOps in my own day to day for a larger org.

Love this. I’ve been working on solo projects for my software development career of ~2 years, and while I had an idea of how this stuff worked as a team, I haven’t been able to get this detailed of an overview yet. Looking to create a more formalized/professional skeleton of processes for even just myself sometime, so I’ll definitely be coming back to this when I have the time to do that. (currently time = build, build, build)

Wow, a boring, but honest story about the work and coffee time or gaming at work BS 🥺? This is probably the best [a day in life of programmer] video on KZread 👍. Thank you! P. S. Looks like I subscribed to the right channel 😎.

@WebDevCody

Жыл бұрын

People try to make work seem like fun on KZread showing their work cafeteria and other perks. Work is just work at the end of the day… 🍻

Hey man. I appreciate you making this video and showing us what it’s actually like. I’m working on becoming a software developer and it’s very informative to know what to expect once I break into the field. Many thanks!

thanks for this video, from the way you explained things it all sounds very stractured with all the processes being followed and teams collaborating together. I work on a service desk myself as a controller, and while we do follow similar procedures, and stick to similar meeting structures, it's pretty much always a mess with a lot of fundamental problems that are not being addressed (constant shift of employees on the project isn't helping either). Im currently looking to start learning for some more technical IT position, but don't know what to strive for yet, so a video like this from the dev perspective is very helpful

Your day to day sounds awesome. I wish our team would pair program as much as you guys do. Sitting and just working through stuff with other developers sounds great.

@corail53

Жыл бұрын

This sounds boring and inefficient as all hell.

@TreetopGamer

Жыл бұрын

@@corail53 if you want to build teams around agile techniques and want a high quality code output then pair programming is actually very useful in many scenarios

This is 1000% more reflective of what a real day in the life of a software developer than those other day in the life videos, ESPECIALLY since more and more people are working remote. I've been on several different teams, and almost all of them follow this scrum pattern.

One of the most realistic "day in the life" videos I've seen. THIS is what should people should see if they want to be come a developer, not most of those other videos out there. Calling out a few points that stood out to me : 1. the points of kanban vs srcum: In the end no solution is perfect, and many teams do merge to the two. Not that it's always the right answer but following strict scum process can end up being a time waste for some teams that can be more productive otherwise. 2. Pointing out that sometimes more vague stories are better and letting the devs have some creativity which can sometimes result in really great implementations. 3. Standups sometimes feel pointless, but if a small bit of info is gained every day it's worth it. The small pieces of info shared add up over weeks so when a PR is made no one is seeing something for the first time. 4. Sometimes big PRs do happen and its the nature of the project. It can sometimes be less productive to try and plan every story out in small little tasks and estimating every little piece individually rather than just getting started on it. 5. "Half the time you don't even finish them within the sprint ... stuff always keeps coming up working on stories". Plans usually don't fully work, and that's ok. The point is having a general plan and short term goals in place to move towards the long term goals. NONE of these points are made to dissuade someone from getting into this amazing career but some of the sensationalization I see online is wild. Many of these things can't be comprehended until you live it. One question I had - You said that you seem to prefer vaguer stories to allow devs some creative freedom, but also mention there is a UX team involved. How does the UX team work with the dev team? Are they providing wire-frames before a story is picked up, doing full mock ups, or providing input at a later stage? In my last team we struggled with where in the process are they best to be implemented.

@WebDevCody

Жыл бұрын

Our company argues the ux and dev team should work together and only start doing the mock ups after the story is moved to in progress. In reality, our team ends up having ux make the designs before the devs start working on the story and we’ll bring in ux along the way if we find the functionality just seems bad or unintuitive as we implement it, or ask to redesign or add pagination if we think technical issues will come up with the implementation.

Your scrum tangent rings true to me so hard. It's the most frustrating thing ever.

One of the best work in a day kind of video. Keep it up!

This is the best day in the life video I’ve ever seen! The best and an actual day in the life. You are the best! I am subscribing!

Really interesting to hear that you work in Zoom with other devs and take turns driving. I've worked at 3 companies(albeit all start ups) and we all are working on independent features/bugs. We may all be working towards some overall Epic, but rarely just sitting on calls coding together. We do pair programming when needing help or wanting another opinion on architecture and stuff, but 99% of my dev time is alone and cranking out code. I agree on you points of sprints/retro feeling a little unnecessary. My last team did 1 week sprints and half the stuff just over flows and we end up being more kanban style in the end. Great video! cool to see another perspective.

This is so interesting, it looks EXACTLY like my day as a fronted dev. Great job

This is the most realistic video I have ever seen! Subscribed ✅ Can you please do a video if you could, about yearly reviews and what to talk about in 1:1 meetings with line managers? Thanks!

It would be nice to see more videos like this, what the real work is from start to finish.

Wow. This might be one of the only videos online that has this information. It's exciting and sad at the same time. Thank you for this.

Good video, always nice to compare different work environments! A little frustrated with my in name only "scrum/agile" environment

Honestly, this was great to watch. So many videos "day in the life of a dev" are adulterated & sugar coated. Good to see something geniune.

As an EAGER af student, you have both put my mind at ease and also lit up a fire in me just by showing what work will actually be like! Now I can go practice tthese things!

As a web developer, this accurate if only by the fact that it is not entertaining. Just the reality of the situation.

Your description of reducing the stories you put in during sprint planning is actually the point. The goal at the end of the day finding a useful metric for story points per sprint based on historical performance and using that to estimate future work. The problems, though, is that stories are never well-defined enough to put points on more than a sprint or two in advance, the client gets random desires to change behavior, UX never has bandwidth to put designs on backlog items, by the time QA gets back to you the sprint is over, and the whole system is pointless. But at least the PM gets a stupid, jagged burndown chart to show their bosses.

loved the honesty suscribed instantly after seeing you are a real one

Going off of this I think a good video would be 'How to estimate your time as a developer' Even though its annoying to do, companies still want developers to estimate how long something will take before they start it

@WebDevCody

Жыл бұрын

Might be interesting. I usually count the number of words or ac on the story and also how many questions are asked about the story in backlog refinement. If there are more words or more questions / confusion, higher estimate

@jww0007

Жыл бұрын

ask a senior dev on the team then multiply it by 1.5 if they reduce it tell them it will take that long because of the things you cannot forsee that will happen

@WebDevCody

Жыл бұрын

@@jww0007 well the point of the estimates are they should be your own estimates. If you don’t know, throw out a number and the group should take the average of all estimates. If they ask why it was high say “because it was an estimate”

@ahmadaccino

Жыл бұрын

@@WebDevCody i agree, when in doubt, a third party is huge, especially if their a developer on the same part of the project. I found that when estimating time, developers tend to look at the best case scenario then work down from that. I usually like the opposite, worst case scenario time and then build back up based on how straightforward or not the story is.

@jshstuff

Жыл бұрын

Estimates are my least favorite part of being a dev

Good video, thanks for taking the time.

Thanks for this. I have been contemplating working on code related jobs but I dont understand what the job entails so I never got that far in learning.

Amazing. Thanks for sharing this with us.

Thanks for this man. I'll be onboarding a client in the next 2 weeks and being a fresh grad with no experience in the industry, this really helped me a lot on what it's like working in this kind of environment.

@Mnkeys

Жыл бұрын

Get all the information on requirements that you can. Understand what they want & WHY. Also, biggest of all, CHOOSE YOUR WORDING CAREFULLY. Some clients are douches.

@jeff1571

Жыл бұрын

​@@Mnkeys Thanks for this. I always ask minimal things to the person giving the task as I am quiet afraid that they might find it annoying if I ask even the simplest things. Reading this gives me encouragement to go and improve myself even more. Thanks again!

@Mnkeys

Жыл бұрын

@@jeff1571 it may be annoying if its the same question, but its sooo much better to understand fully early on. Troubleshooting is what causes you to go over estimate.

never ever ever EVER seen a vid like this, thank you bro

Haha, I have the same feelings about the retro😂 We are on 2 weeks sprints, JIRA, gitlab and additionally JBehave BDD testing because of the nature of the system (OAuth, Open ID Connect, Spring/Spring Boot/Spring Security).

Starting my new grad position next week and this is very helpful and easing my anxiety. Thank you

@8015908

Жыл бұрын

Your first months as a new grad will just be all about learning. It's non-stop learning until you're like 10 years in. Even then you're still learning about new tech.

@XoXoEsi

Жыл бұрын

Good luck! Im 4 months in. So far so good.

@lul420

Жыл бұрын

3 months in! Not too bad, still learning lol

This actually was really helpful all the other videos just explain basic life tasks and not coding

Your work environment looks pretty hardcore, impressed with the implementation of processes

@WebDevCody

Жыл бұрын

This is actually the most laid back project I’ve been on. Again, we don’t follow scrum exactly, we evolved it to meet our project and teams needs over the years and we put less emphasis on things we find useless.

@noahwinslow3252

Жыл бұрын

@@WebDevCody you know, it might be an interesting follow up video of what you would like to take from scrum and what you'd leave out, given your critiques

@iivarimokelainen

Жыл бұрын

what do you mean, what looks hardcore?

@noahwinslow3252

Жыл бұрын

@@iivarimokelainen Its one thing for tech companies to say they implement all these policies, its another to implement them

this channel is a hidden treasure, keep going 🚀🚀

Very informative and accurate! Thank you for showing the real thing

Finally a real view of web dev work. Looks like a lot of other office jobs except it involves coding.

You sir are a unicorn! 🦄 You've got a sub just for the first 3 minutes of the video!! Thank you for this ACTUAL day in the life content!

wait a minute, are you saying i dont get to wake up every day, sip martinis, take an adventure on my yacht, write 3 lines of code, and spend the night hanging out with my D&D group? then whats the point?

Agree 100% that is my experience of a day in the life of a software engineer. I've mainly used the Atlassian suite (Jira/Confluence/Bitbucket) along with slack/teams/flowdock/zoom for comms. I've tended to favour scrum for greenfield developments and Kanban where there is any element of maintenance/high tech debt. Imho both methodologies embrace the same fundamental principal: do the work required to get a smaller piece of value live; as opposed to waterfall which is complete all analysis/design for the whole project before you really get into development. I always think of agile as "Deliver value whilst it is still valuable" - I;ve worked on a lot of waterfall projects (not in the last 8 years though) where the world moved on and the product was just not fit for purpose once it was delivered :( Another thing we sometimes get to do as software engineers is have fun with R&D (technical spikes) or hackathons. A lot of companies support hackathons where employees form teams and develop novel solutions to a themed challenge over 24/48hrs. The challenge is normally related to the business but the rules are normally quite broad. Your team then spends whatever time they like to complete their project - late night pizza ^^. One of the really nice things, I've found, about hackathons is that it is normally open to all staff; the non-technical staff just have to join a team with some techs in, although I taken part in some where the team had no technical staff and provided a presentation and mock-ups in lieu of an application.

I really enjoyed this video, thanks so much for sharing.

you sir deserved a subcribe, all these day in life of a web dev out there just showcase of people waking up, eating lunch, going gym and etc. nothing related to the actual job details at all..

Yessss we love to see what it actually looks like to be a dev. I feel like when you start it seems like this mystery 😂

do you have a video on how you organize your folders and files i always struggle with this because i guess i never learnt how to organize them

Lol loved your description of all these "day in the life of a" video because I've seen so many lately I can agree they don't show you shit except how awesome their life is.

Amazing video . Thanks for sharing work environment.

Again , Quality content.Keep up

finally a youtuber who actually works as a web developer 🖤

My team uses SCRUM methodology with JIRA and confluence suite. We have a much poorer cycle of feedback from users though, as requirements aren't always ironed out well from the Business Analysts and users, sometimes keep getting new tickets for sub-task that was not properly planned. We work on our own unless we hit bugs then we call each other. We don't have automated deploy triggers on merge and it has to be triggered after merging. The branching strategy here is also such that everyone works on their own branch and we have intermediate branch where all code is merged to. But everything else is pretty much the same like standup, meetings and work itself.

This is awesome! It's almost the same with what we do.

That's exactly what we do, the only difference is that we use Discord. The methodology helps you knowing where you are at in the project, either for you or for the Project Manager/Owner

I'm still a student and this really helps me a lot thanks

this is what im looking for, actual day of a developer...great vid...

Thank you for doing this.

Man, thank you. Thank you very much!

this is actually so relatable!

Thank you for this!

My team and I work the same way. Nice vid!

can someone tell me how to make shorts where I can show my browser and code in the same time I find it really very difficult

@WebDevCody

Жыл бұрын

I use obs to record my screen

you forgot the part where you play ping pong with your coworkers for 7 hours

How we test changes after we implemented in vs code, do we use local host, or do we have seperate links for test version of website.

@WebDevCody

6 ай бұрын

Test everything locally, then test in cicd pipeline with automated tests, then deploy to a real environment to test again, then deploy to prod

Just wanted to compare my days as a web dev to yours, thanks for the video

Nice video! I recently graduated as a Computer Science Engineer, but I'm kind of afraid to work as a dev because I keep thinking what would happen if I cant code some functionality they assign me and being judged by the team of developers 😕. Is it normal to feel that way as a no experience recently graduated developer?

@WebDevCody

Жыл бұрын

If you work real real humans they would understand you’re a beginner and give grace. As long as you show you are trying and learning every day you should be good

@mgjulesdev

Жыл бұрын

When you are hired in a dev job as a beginner, you are often hired for the prospect you show in growth. So you should not be worried about trying to match what intermediate or senior developers are putting out there but show that you are growing and contributing the best you can. That is enough to earn the appreciation of the team

Nice , thank you for sharing

Thank you this is what a day of developer videos should be not ooo lunch time oooo free swag came in

Great breakdown. This is pretty much my experience, except at my company the PO is making the majority of the UI/UX decisions and with no design standards. It has led to pretty much no consistency in UI/UX across our apps and some odd experiences that don't really follow web standards. The AC looks exactly how you described it shouldn't be, explaining UI/UX requirements and sometimes names of DB tables/columns. So frustrating sometimes 🥱

@WebDevCody

2 ай бұрын

Yeah those details should be left to the engineers. The po should change role if he is giving ux and table designs

Half way through i was like "why am i watching this? Im a web developer" lol

@WebDevCody

7 ай бұрын

😂 maybe to see if the grass is greener anywhere else; it isn’t

Good info here. Thanks

Thank you sir

how does one find a remote job? ive been looking for over 2 years and cant find any job willing to hire for remote work without either a degree or experience. :(

color theme pls? thx

Which theme do you use on Visual Studio Code?

top-tier video!!

This is quality content.

Just a quick question, how does this translate to junior devs/new hires with zero industry exp? Do they simply job shadow from the start or is this part of onboarding/training?

@WebDevCody

Жыл бұрын

You’d be part of this same process and you’d learn along the way. You won’t really understand a lot of what’s going on at first but you’ll get a hang of it

@ravengaspar5027

Жыл бұрын

@@WebDevCody thank you so much for all the insights!

Thank you for the video. It was better day in life than others because it was more about the job not human life

I like scaling problems as Fibonacci haha. I also never say time estimates. I say complexity estimates. Sometimes complex problems have easy solutions and take less time, but often will take more time for more complexity. So it’s a probability it’ll take a long time and not an estimate of time. Complex problems can benefit from stewing in subconscious so give them more time in brainstorming approach phase unless emergency.

@ponderatulify

Жыл бұрын

I really dont get the complexity metric.

Thanks for this video man, now I know I've been watching showoffs the whole time, thanks for giving us the full gist

-I'm curious what a dev with some experience such as yourself thinks of the arguably arbitrary cadence (eg 2 weeks) around which a lot of teams organize work. What is the value of doing this? What are the risks of adopting such a system but then failing to fit the work at hand into that cadence (work is finished earlier or later than the 2 week timeframe) ?- "the whole idea of scrum just doesn't make sense to me" Thanks you went on to answer this in the video! I appreciated the tangent and I don't know why these ways of working persisted for so long when just about every person I talk to can't identify significant value in them.

@WebDevCody

Жыл бұрын

Yeah idk, Kanban makes the most sense to me. I think scrum was created by consultants to make money training teams to follow some type of structure. I’m assuming many teams don’t have a good set of process or communication which is what agile and scrum try to solve.

How do you move your work across higher environments?

@WebDevCody

Жыл бұрын

Make a pr from a lower branch into a high branch. So dev into master would deploy to prod

I work on teams/outlook company with a client that uses Altasian tools. Living the most corporate dev experience here (At least we don't use a flash drive to do source control)

Thank you for your refactor videos and old videos about javascript . I'm 4 months already as a front end developer . I realized how important the basics are in javascript and react . Any advice ? Love from philippines ,

@WebDevCody

Жыл бұрын

Just keep doing deliberate practice and try to learn one new thing daily.

@jww0007

Жыл бұрын

@@WebDevCody now that's something they don't tell ya

@bonchan4404

Жыл бұрын

@@WebDevCody is doing daily codewars/leetcode challenges good or should i focus creating mini applications that focuses on front end ? whats much better . thank you !

@WebDevCody

Жыл бұрын

@@bonchan4404 maybe a bit of both couldn’t hurt

Do you and your co-workers ever use VSCode's live share feature for pair programming? It really shines for that.

@WebDevCody

Жыл бұрын

Nope, I think we tried but didn’t like it. We just take turns driving on different machines and screen share in zoom. It takes like 10 seconds to commit and pull so it isn’t bad

@Ace3260

Жыл бұрын

@@WebDevCody ah gotcha! Thanks for such an informative video regardless. Live share definitely has some quirks for sure!

LMFAO... exactly... I said to myself wtf does drinking coffee drone shots and skylines have to do with what you do as a dev... thank you so much for this video...

You just did half of the Scrum 101 course 😊

My day consists of endless meetings that could of been emails, wondering why stuff is broken, and sending the other devs memes on the teams group.

@Niaxe111

Жыл бұрын

Could work during meetings, or use your meetings to ask why shit is broken. Send memes in emails. Reuse highly upvoted comments in other youtube videos as your own.

@basspalace2920

Жыл бұрын

@@Niaxe111 this was my own comment clown 😂

Do you stick to the meeting times

@WebDevCody

Жыл бұрын

I made these times up for this video, but yes we usually start the meetings around the same days and times

are the stories seperated between frontend and backend team or both work together on the same story

@WebDevCody

4 ай бұрын

We don’t have a frontend backend team split. Every developer is responsible for the entire story

Finally! An actual day in the life of a programmer. Thanks for showing how it really goes down for many of us.

dang im glad our scrum isnt as restrictive as this , also we acknowledge that estimations are arbitrary asf so we dont use those, and we dont use burndown charts either. its is done when it is done. less time wasted on useless meetings and more coding. like it should be

@WebDevCody

Жыл бұрын

Yup our team is a combination of Kanban with scrum ceremonies. The estimates are not super important to our po, but he still wants some type of number, we don’t do burn downs. It’s done when it is done is our mentality on this project as well.

@jww0007

Жыл бұрын

it is a tradeoff though

Mine is bum rushing start of die, get hyped up, get good progress and chill for rest of day. Once I burn out once I don't go back and try again, low hours but functional.

No BS. Just the way I like it 👏🏿

Good video. I think you’re right. A lot of the daily “rituals” are unnecessary. It’s worse in the corporate world. Too many “cooks” in the kitchen.

Scrum and Agile is good to an extent but after sometime it just starts working counterintuitively, so you have a lot of garbage code, unnecessary complexity and useless meetings with stupid deadlines. Kanban is probably my personal fav out of them all because of the flexibility in time allows creativity.

nobody wanna point out that the title is missing the word "look"?

Thank you for this. I was so, so tired of seeing people pour coffee

Great video. Lots of similarities

Damn I started the video like "OMG 😊 ANOTHER OF THOSE COOL VIDEOS OF HIM PLAYING CSGO ALL DAY AND GIVING NO FORKS TO WORK AND THEN DOING IT ALL IN 5 MIN!" and left it like "Life is pain 😔, the struggle is real 😞, work is work, I need to hug, world is chaotic!" haha made me scared but this was the first real video on this theme damn nice 👏👏

@WebDevCody

Жыл бұрын

What company allows people to play csgo all day, please hire me

@isk8atparks

Жыл бұрын

​@@WebDevCody The same companies that allow people to hold two different software dev jobs at once

@WebDevCody

Жыл бұрын

@@isk8atparks sounds like I'm doing it all wrong

Whats the tool you use on github is it github workflow?

@WebDevCody

Жыл бұрын

Zenhub is the extension we use on GitHub to give us these nice workflows

This is the exact thing that I do xD but with alot of tools such as for zenhub we use trello For deployments we use Jenkins. But I am still a bad coder but mediocre/good at solving bugs 🙂😅

@WebDevCody

Жыл бұрын

Jenkins, i remember those days 😅. Luckily we use circle ci on this project I’m current on so I don’t have to manage configuring Jenkins servers any more 🎉 yeah a lot of companies follow a similar process just with different tools, then they tweak their process a bit to make to work best for everyone