Lemme add my experience with companies: Usually they have their own hosted git solution (like a gitlab instance). Then the team works with some kindof process (like Scrum). So then someone writes all the issues and "backlog" items that should be done (like bugs, features, ...). Then you plan what to do next (in a team usually) and developers can start implementing it (moving item to progress, opening branch, opening MR/PR, giving it a good description, implementing (passing all tests, requirements), other dev will then review/give feedback, then its merged (often into a dev branch and not the production branch), the dev branch is connected to a CI/CD pipeline and result is hosted on a testing version of your product, then the testers jump on it and test manually, pontentially moving the issue back to the developer where they start with implementing the fix(review->merge->test)) until the testers are happy, then it can be planned into a release and eventually released (where all production server will be updated). In that whole process its often a thing where requirements arent clear so youd have to ask the one who wrote the requirements, or the tester might have questions to the developer, and many other communication that can delay the progress of a feature being implemented. Thats why big companies often take very long to finish things.
Amazing expiation man! That’s some great insight into deeper level stuff that many of us haven’t reach yet so it’s awesome to see what it could be like one day :)
@@sam-pt7rt There is a new vid from Nizar about exactly this issue. Keep searching and make you own hands dirty by working on projects and make yourself stand out.
@@Jorma___ nope that's popular WRONG statement. Actually comments help a lot and often substitute the docs. For example, the docstrings in Python can easily explain things very well - so you won't have to create a separate technical docs, README, anything. It's a big question what's better - tech docs or code comments - because they are basically very similar things and serve the same purpose. But saying that you don't need any of them, and the code itself is enough, is utter BS. Try to onboard a new developer on a new huge codebase with no comments and no docs. Good luck having him/her lost and unproductive for at least 1-2 weeks. That's just a waste of time and money
Usually there's ""Grandmaster Agile Scrum Blackbelt Ninja Overlord of Kanban, Certified Professional Extraordinaire in Synergistic Waterfall-Agile-Hybrid Methodology, Supreme Overseer of Gantt Charts and Timelines, Archduke of Sprint Planning, Commander of the Infinite Backlog, Emperor of Deadline Extensions, Master Conductor of Stakeholder Alignment and Scope Management, All-Seeing Eye of Budgeting and Resource Allocation, Guardian of Milestones, Wielder of the Holy Project Charter, and Divine Protector of All Things Asana and Jira" project manager who makes the whole process of code-production 1000 times slower.
AND making new features/refactorings/dependency updates easier, as, if you can run the tests from unit to e2e, you can be somewhat sure that everything still works. Ye
Tons of security measures, auditing tables, tons of monitoring, i18n, custom UI elements, rigorous testing, different styles of code even after linting, data migrations, library and framework verion updates, ... the list goes on. Joining a big company that has decades of legacy to it is a complete different beast than anything you could do or would need in a hobby project.
I bet! The company I work at is just a few years old so the code is at least somewhat relatable to my side projects but I bet the larger company code must be much much harder to use
Hey Nizar, Been in a programming rut of recent, Happy to see your still around. I'm gonna just feedoff your programming rizz and energy and get back on my A game. Srsly, Thx for being an amazing developer and friend. Also 😘😘
Super interesting video, as a dude who mainly codes for fun since I mainly work in Excel and never seen any large scale project, I really apreciate this video
I am still pretty early in my career have worked for a large cap company and now a small cap. I think the biggest thing that threw me off when first seeing industry code is the sheer amount of custom objects/types. I worked mainly on backend microservices and you can't just pick up a ticket go to that endpoint and find the bug these things are using like 4-8 custom types that each have their own logic, the amount of nesting that you have to sift through to even get to the base definition is 2-4 layers deep a lot of the time and you do this for all types to even understand what the piece of code is doing.
@@blacklife-s6h What library does an Angular Developer need when Angular is a full-fledged framework that has everything they'd need for UI development?
well it's not even a BIG company. In the big companies, inter-department communications become more and more common and eat time. Like, you have to write and document how all your team's microservices work, and don't forget to update these docs, because a bunch of other IT teams rely on them
I hate seeing comments that say something like ”Here I loop”. I can see there’s a loop. One comment said something like ”stop fooling around, let’s do some work”. So, all you did until this comment was to ”fool around ”
@@NizzyABI It should but it doesn’t always do. 99% of the time, the first person to fail to understand how or why some code works is the person who wrote it because the clever parts lacked a comment.
Naming is so obvious and should be done even in pet-projects, I almost clicked off the video… but the error handling is a real difference, and abstraction too
i really like your videos, lol except the video that you read 5 books in a weeek lol. you go to the point, are focused, and are topic that usually are so abvious but notbody talks so you bring up with new prespective. am already following you and subscribed. Looking up for a topic how do you learn and what resourcses do you use (beggining and now)
Nice video but you showed us the code only like 5% of the time, may be you can put yourself in the corner with the code in the background for next time, subscribed.
If you dont want to write tests, you have obviously never worked on real large scale products... well at least one that has to work all the time. Like if there is A LOT of money involved, you WILL fall in love with tests. No way around it
Lol I commented on this because I was working on a project where I was designing the comment section that looked similar to this was not expecting your reply thankyou though @@NizzyABI
@@NizzyABI what a stupid decision to make a video about showcasing code and only showing it for 3 seconds every time before cutting to your shitty webcam. THINK
Lemme add my experience with companies:
Usually they have their own hosted git solution (like a gitlab instance). Then the team works with some kindof process (like Scrum). So then someone writes all the issues and "backlog" items that should be done (like bugs, features, ...). Then you plan what to do next (in a team usually) and developers can start implementing it (moving item to progress, opening branch, opening MR/PR, giving it a good description, implementing (passing all tests, requirements), other dev will then review/give feedback, then its merged (often into a dev branch and not the production branch), the dev branch is connected to a CI/CD pipeline and result is hosted on a testing version of your product, then the testers jump on it and test manually, pontentially moving the issue back to the developer where they start with implementing the fix(review->merge->test)) until the testers are happy, then it can be planned into a release and eventually released (where all production server will be updated). In that whole process its often a thing where requirements arent clear so youd have to ask the one who wrote the requirements, or the tester might have questions to the developer, and many other communication that can delay the progress of a feature being implemented. Thats why big companies often take very long to finish things.
Amazing expiation man!
That’s some great insight into deeper level stuff that many of us haven’t reach yet so it’s awesome to see what it could be like one day :)
@@sam-pt7rt There is a new vid from Nizar about exactly this issue. Keep searching and make you own hands dirty by working on projects and make yourself stand out.
@@goosydev :(
I just started my first developer job 2 months ago and this is very accurate.
@@sam-pt7rt why are you job hunting in a replies to a random youtube comment
can confirm, this is large-scale, production grade code because there is tons of code but no comments.
lmao
Yeah same thing in the company I work. No comments.
comments are useless 90% of the time
If you need comments, then your naming is terrible or your code is over complicated
@@Jorma___ nope that's popular WRONG statement. Actually comments help a lot and often substitute the docs. For example, the docstrings in Python can easily explain things very well - so you won't have to create a separate technical docs, README, anything.
It's a big question what's better - tech docs or code comments - because they are basically very similar things and serve the same purpose. But saying that you don't need any of them, and the code itself is enough, is utter BS. Try to onboard a new developer on a new huge codebase with no comments and no docs. Good luck having him/her lost and unproductive for at least 1-2 weeks. That's just a waste of time and money
Usually there's ""Grandmaster Agile Scrum Blackbelt Ninja Overlord of Kanban, Certified Professional Extraordinaire in Synergistic Waterfall-Agile-Hybrid Methodology, Supreme Overseer of Gantt Charts and Timelines, Archduke of Sprint Planning, Commander of the Infinite Backlog, Emperor of Deadline Extensions, Master Conductor of Stakeholder Alignment and Scope Management, All-Seeing Eye of Budgeting and Resource Allocation, Guardian of Milestones, Wielder of the Holy Project Charter, and Divine Protector of All Things Asana and Jira" project manager who makes the whole process of code-production 1000 times slower.
chill man , maybe it's just your manager .
holy crap that was a read
You don’t only write tests to avoid bugs in your commits, but to prevent future commits from breaking what you wrote
AND making new features/refactorings/dependency updates easier, as, if you can run the tests from unit to e2e, you can be somewhat sure that everything still works.
Ye
Tons of security measures, auditing tables, tons of monitoring, i18n, custom UI elements, rigorous testing, different styles of code even after linting, data migrations, library and framework verion updates, ... the list goes on.
Joining a big company that has decades of legacy to it is a complete different beast than anything you could do or would need in a hobby project.
I bet!
The company I work at is just a few years old so the code is at least somewhat relatable to my side projects but I bet the larger company code must be much much harder to use
Sounds like Magento 2 😂
Hey Nizar, Been in a programming rut of recent, Happy to see your still around. I'm gonna just feedoff your programming rizz and energy and get back on my A game. Srsly, Thx for being an amazing developer and friend.
Also 😘😘
Glad to have u back bro!!!
Super interesting video, as a dude who mainly codes for fun since I mainly work in Excel and never seen any large scale project, I really apreciate this video
I am still pretty early in my career have worked for a large cap company and now a small cap. I think the biggest thing that threw me off when first seeing industry code is the sheer amount of custom objects/types. I worked mainly on backend microservices and you can't just pick up a ticket go to that endpoint and find the bug these things are using like 4-8 custom types that each have their own logic, the amount of nesting that you have to sift through to even get to the base definition is 2-4 layers deep a lot of the time and you do this for all types to even understand what the piece of code is doing.
this is an amazing video, and im so glad you contributed this here man
Thanks for the kind words :)
Dude i can see that you have been grinding real hard on your youtube channel, its nice to see youve gotten to 10k subs, you certainly deserve :0
Thanks man :)
I think my head would hurt having to deal with so many things.
That's why we get paid $$$
Yup, currently 2nd year CS and im already panicking
@@Someoneyeeted It's gonna get worse. But you're gonna learn to enjoy it.
That's great. Thank you for sharing. Keep up your amazing content!
I recently switched to Angular for the urge of writing production grade codes. React doesn't appeal to me more in terms of code quality.
yeah angular is great
Ever since I wrote backend for my pet project using nest.js, I understood why companies prefer Angular for production level apps
In terms of libraries for angular what can you do coz react has a lot of open source libraries
@@blacklife-s6h What library does an Angular Developer need when Angular is a full-fledged framework that has everything they'd need for UI development?
A very cool video! Keep it up!
Thanks 😊
😘😘Nice and informational video bro!! Thanks
Welcome 😊
Your eyebrows are well done.
thanks 😊
@@NizzyABIyea bro it got my erekASF 🔥🔥
we need more videos like this !!!
ok :)
that 100% high quality content.
god forbid the number of errors 2:05
problem on my computer (JS linter is messed up)
code works perfectly
@@NizzyABI haha i know that you are a good coder, just messing with you
After seeing the intro, I thought you were going to show a code that is better than my personal projects that makes 0 dollars
u saw software making $100k a month lol so maybe it’s ur idea 😉
well it's not even a BIG company. In the big companies, inter-department communications become more and more common and eat time. Like, you have to write and document how all your team's microservices work, and don't forget to update these docs, because a bunch of other IT teams rely on them
I hate seeing comments that say something like ”Here I loop”. I can see there’s a loop. One comment said something like ”stop fooling around, let’s do some work”. So, all you did until this comment was to ”fool around ”
comments themselves are sooo annoying the code itself should speak for itself for the most part
@@NizzyABI It should but it doesn’t always do. 99% of the time, the first person to fail to understand how or why some code works is the person who wrote it because the clever parts lacked a comment.
I only write comments for things I can't change and always explain WHY the code is there instead of how or what it's doing.
tl;dr: naming things, scalability and not pushing directly to main?
ye there’s obviously a lot more but that’s what i know rn
I was offended in the first 10 seconds 😂
Do companies create their own CMSs?
idk if they create their own but i know many (including mine) that use something like Dato, Contentful, etc.
Can you provide a link to the open source code base that your company is associated with? Would be interesting to explore.
sure here u go:
github.com/calcom/cal.com
Did you know how to use git before your first work experience?
a little (i'm talking about knowing how to commit and push code)
i learnt it on the job
Very Intuitive
Testing is everything, on that, trust me!
Yep!
What theme is it ?
If you are a web developer, you are not even enterprise. Just remember that.
Looks scary to be honest.
God help us.
"insert two kiss emojis"
:)
imagine a os written in one file one method
can't relate
Imagine an os written in JQuery (yes it exists)
Got my sub. 👍
Lfggg
Great video 😘😘
Thank you 🤗
It was obvious, it's important to refresh knowledge though 👍
Mostly large scale applications are written using java not js
fr
0:46 GIGI MURIN!!???
good video bro 😘😘
Thanks :)
Naming is so obvious and should be done even in pet-projects, I almost clicked off the video… but the error handling is a real difference, and abstraction too
Lol at 1:29 there are variables called 'z' which is impossible to workout what it means.
Usually frontend use z for Zod
Zod is a validation library
As in code you can see they're using it for validation schemas
yeah lmao
nice vid
thank uuuu
‘null’ is what it looks like
I code for myself and I made everything foo1, foo2, foo3💀
LOL
Got my sub 😘😘
:)
From germany 😘😘
Hell yeah love my German bois 😻
i really like your videos, lol except the video that you read 5 books in a weeek lol. you go to the point, are focused, and are topic that usually are so abvious but notbody talks so you bring up with new prespective. am already following you and subscribed. Looking up for a topic how do you learn and what resourcses do you use (beggining and now)
Some vids hit some miss hehe glad u liked this one :)
@@NizzyABI tell us how you learn lol :D am really curious like geniuenly (sorry typing lol)
Good morning! Posted 3min ago and 0 views... starting going down
(It's a joke)
I fell off 😫
Nice video but you showed us the code only like 5% of the time, may be you can put yourself in the corner with the code in the background for next time, subscribed.
Thanks for the tip!
u moroccan?
Lebanese
What do you suggest for the cms?
DatoCMS, Contentful is good too
wdym leave 2 kiss emojis bro?
leave two kisses
@@NizzyABI aiit bro 😘😘
❤
If you dont want to write tests, you have obviously never worked on real large scale products... well at least one that has to work all the time. Like if there is A LOT of money involved, you WILL fall in love with tests. No way around it
Preach
yo brother what's going on
Not much 😈
Lol I commented on this because I was working on a project where I was designing the comment section that looked similar to this was not expecting your reply thankyou though @@NizzyABI
Subscribe button >>>>>
:)
Two kiss emojis uwu
this typescript coders are not programmers 😂😂😂😂😂😂😂
yes the language u write it determines if you're a programmer or not 🤦🏽
🥰🥰
😘 😘
:)
3:10 don't forget unit tests
Lol nice😘😘
:)
Cool insights
😘😘😘😘
😘
Just show the code bro, no need to keep cutting to yourself 🤦♂️
no
@@NizzyABI what a stupid decision to make a video about showcasing code and only showing it for 3 seconds every time before cutting to your shitty webcam. THINK
@@NizzyABI use your brain
😘😘
😘
😘😘😂😂
HIIII
It's harsh but 99% of developers can only make projects not a industry standard product. 😢😢😢
Idk man it takes learning and time to reach industry standard but we all have to start somewhere
Amazing video😘😘
Thanks 🤗
😘😘
:)
😘😘
😘😘 real
😘😘
😊
😘😘
😜
😘😘
🫥🫥
😘😘
hehehe
😘😘
😘😘
😘😘
heyyy
@@NizzyABI nice vid dude!
😘😘
kanye
😘😘
:)
😘😘
hehe
😘😘
:))
😘😘
SUP!
😘😘
😘😘