Great points. I’m a software engineer with about 4 years worth of experience and I one thing I recently learned is being eager to take on tasks doesn’t mean anything when you can’t finish them all in that sprint cycle. Better to have 1 or 2 things on your plate that you can finish than 5 you can’t. This was a great video by the way! Got a new subscriber!
There is indeed a lot of cases where performance and correctness are vastly more important than readability, and where the requirements for every developer in a team are very high. It is, frankly, much more fun to work in such places.
I was recently working on some functionalities and obviously had to make it to prod since we were tied with deadline. It was reviewed by some peers and we didn’t want to spend days to refactor everything. As long as it passes UAT , preprod, prodTest and we were agreed that things are working We were good to go. When things are not busy , we could create some stories , passing down to juniors dev to refactor , review it and merge it again. Also , I am also working on side project but obviously on my free time. Thanks a lot. I have to work on my communication skills . This is exactly where I am stuck. Thanks for your tips and tricks
Happy to help! Thanks for the support! My recommendation for the communication skills would be to always be more verbal in meetings, this helps alleviate the fear of speaking on things and will setup a habit of effective communication.
I couldn't agree more with the points you've highlighted, especially regarding the significance of code readability over highly performant but incomprehensible code. I've encountered projects where I found myself tracing code that was simply beyond unfathomable. It was undoubtedly one of the most challenging experiences I've had as a software developer. Great content! Hence, you deserve a subscribe. :)
It has certainly been a blast to listen to the wise advise provided, straight to the point with the engagement style. Keep up the hard-work, looking forward to your growth on this platform, stay safe and blessed! 😄
I’ve said this plenty of times. Software Engineers should care about two things: 1) Is your work/code doing what the CEO and company asked for? 2) Can future junior engineers EASILY understand your work/code
There is a lot of domains in development where juniors have no place at all. The complexity of these domains pretty much require that everyone in a team are seasoned professionals (ideally with PhDs and multiple other qualifications). It raises the bar quite a bit.
thank you for this valuable content I mean these tips came from 8 years of experience it is very valuable your thirsty subscribers want more :) I'm just starting my career as a full-stack web developer
the Readability/Maintainability thing also applies to architecture. I've been involved in some projects where a single business process has been distributed to several Microservices under the name of "scalability" but you end up with a spaghetti architecture that's a pain to debug when an issue occurs
I slave away because I want to. Because it's quite cool when you conceptualize a performance capability and youre able to make itbhappen, and witness how well it works and how its solves a problem with rendering performance when you're scrolling theough list of thousands of items while having no impact on UI performance.
Thanks! I think communication is definitely one of the biggest ones, I would also say time management and project management are good ones to master that are desired in senior level and above.
On your last point, I do think that in most situations you're correct that it's better to write code for human understanding, but there's also those outliers where that's not the case. For example, in a previous role of mine I was writing graphics rendering software for game development aimed at lower end devices. In order to hit the necessary performance, easily understandable but slower code wasn't really an option. This is also something that embedded developers who are dealing with strict hardware requirements run into frequently as well.
Hey man, not gonna lie: I thought your video was _great,_ but your code example with the variable names: Horrible. I can't stand reading code like that, drives me nuts. Sorry, I'm really really not trying to be mean, just direct. It turns my brain to mush when I have to read those long camel case variable names. Maybe auditorily it works, but visually it's just ... unartistic. I think the Ruby community (generally) has done a good job with variable names that are short, pithy, well chosen, so that the algorithm of the code stands out a little, and yet doesn't go all the way towards looking like a math equation, which is very dense and compacted (e.g. APL). The old adage: "There are only two hard things in computer science...."
Nothing wrong with differing opinions. The example probably wasn’t the greatest, but as long as the variable names are easy to understand and follow you can be as concise as you would like. But I’ve seen some pretty bad code where I genuinely had a tough time figuring out what the heck the code was doing because the variable names were so vague.
Great points. I’m a software engineer with about 4 years worth of experience and I one thing I recently learned is being eager to take on tasks doesn’t mean anything when you can’t finish them all in that sprint cycle. Better to have 1 or 2 things on your plate that you can finish than 5 you can’t.
This was a great video by the way! Got a new subscriber!
Thank you very much! I appreciate the support.
There is indeed a lot of cases where performance and correctness are vastly more important than readability, and where the requirements for every developer in a team are very high. It is, frankly, much more fun to work in such places.
Honest wise advice.
No exaggerated advices to get views. Just a natural original content.
Thank you. Subscribed.
Please always be realistic like this.
I appreciate that! Thanks for watching and taking the time to comment!
Going to the gym is a yes or yes for me on my life, doesn't matter what im doing always there's time for workout
I could use more time in the gym that’s for sure 😳 It just gets tough once you have kids, a career, hobbies, and other responsibilities.
😂 The naivity.
I was recently working on some functionalities and obviously had to make it to prod since we were tied with deadline.
It was reviewed by some peers and we didn’t want to spend days to refactor everything.
As long as it passes UAT , preprod, prodTest and we were agreed that things are working
We were good to go.
When things are not busy , we could create some stories , passing down to juniors dev to refactor , review it and merge it again.
Also , I am also working on side project but obviously on my free time.
Thanks a lot.
I have to work on my communication skills .
This is exactly where I am stuck.
Thanks for your tips and tricks
Happy to help! Thanks for the support! My recommendation for the communication skills would be to always be more verbal in meetings, this helps alleviate the fear of speaking on things and will setup a habit of effective communication.
thamks@@justin-cassidy
Thank you for sharing your experience, especially talking about soft skills and the readability of code
I couldn't agree more with the points you've highlighted, especially regarding the significance of code readability over highly performant but incomprehensible code. I've encountered projects where I found myself tracing code that was simply beyond unfathomable. It was undoubtedly one of the most challenging experiences I've had as a software developer. Great content! Hence, you deserve a subscribe. :)
Thank you very much!
It has certainly been a blast to listen to the wise advise provided, straight to the point with the engagement style. Keep up the hard-work, looking forward to your growth on this platform, stay safe and blessed! 😄
Thank you very much for the encouraging words! Much appreciated!
I’ve said this plenty of times.
Software Engineers should care about two things:
1) Is your work/code doing what the CEO and company asked for?
2) Can future junior engineers EASILY understand your work/code
There is a lot of domains in development where juniors have no place at all. The complexity of these domains pretty much require that everyone in a team are seasoned professionals (ideally with PhDs and multiple other qualifications). It raises the bar quite a bit.
Great insite and tips I aim to be come a software engineer and found this very helpful on my beginner journey
thank you for this valuable content I mean these tips came from 8 years of experience it is very valuable your thirsty subscribers want more :) I'm just starting my career as a full-stack web developer
I appreciate the support!
the Readability/Maintainability thing also applies to architecture.
I've been involved in some projects where a single business process has been distributed to several Microservices under the name of "scalability" but you end up with a spaghetti architecture that's a pain to debug when an issue occurs
Loved your points. Keep going ! 🙌🏼
I slave away because I want to. Because it's quite cool when you conceptualize a performance capability and youre able to make itbhappen, and witness how well it works and how its solves a problem with rendering performance when you're scrolling theough list of thousands of items while having no impact on UI performance.
Good video, you should have a lot more subscribers
Thank you! Very much appreciated.
hhmmss: 00:53-1:50 ; 2:05-3:05 mindset leadership critical thinking soft skills goal oriented business problems
New to your channel. Good clip editing, Mr. Beast style "wait till the end", clear video, good background music, I look forward to your success sir.
I appreciate the compliments and support!
Great content! Would be interested in hearing more about soft skills. What’s important for progressing to senior developer and beyond?
Thanks! I think communication is definitely one of the biggest ones, I would also say time management and project management are good ones to master that are desired in senior level and above.
made me laugh: 'ain't nobody got time for that'. Thanks for the lessons and your experience.
keep going
hey man thanks for the advice! i was wondering: what camera do you use?
On your last point, I do think that in most situations you're correct that it's better to write code for human understanding, but there's also those outliers where that's not the case. For example, in a previous role of mine I was writing graphics rendering software for game development aimed at lower end devices. In order to hit the necessary performance, easily understandable but slower code wasn't really an option. This is also something that embedded developers who are dealing with strict hardware requirements run into frequently as well.
Cool. I’m an embedded engineer but i don’t have that issue. But i get your point
soft skills are so important. I feel like i can't get a job 'cause i lack communication
Very important!
Readability is probably better than unreadability supplemented by comments.
Hey man, not gonna lie: I thought your video was _great,_ but your code example with the variable names: Horrible. I can't stand reading code like that, drives me nuts. Sorry, I'm really really not trying to be mean, just direct. It turns my brain to mush when I have to read those long camel case variable names. Maybe auditorily it works, but visually it's just ... unartistic. I think the Ruby community (generally) has done a good job with variable names that are short, pithy, well chosen, so that the algorithm of the code stands out a little, and yet doesn't go all the way towards looking like a math equation, which is very dense and compacted (e.g. APL). The old adage: "There are only two hard things in computer science...."
Nothing wrong with differing opinions. The example probably wasn’t the greatest, but as long as the variable names are easy to understand and follow you can be as concise as you would like. But I’ve seen some pretty bad code where I genuinely had a tough time figuring out what the heck the code was doing because the variable names were so vague.
@@justin-cassidy Thanks for your thoughtful reply 😀