Hope you all find this video enlightening! And by the way, for those of you who are curious about the Data Structures crash course on AlgoExpert, it’s coming out _very_ soon-just a few more days (from December 9th, 2019)!
Hi can i have your help please, am working on my project how to communicate to a machine but current its hard for me to make the machine understand that i have finish to talk now it the time for it to reply can you help me how i can work on this my email is danielpoul.dp@gmail.com
Thank you for sharing all of this great knowledge and advice Clement 🙌🏽 Here are the TIMESTAMPS for those that need it ✨ 1:05 What is a Design Doc? 4:40 Design Document Example
I think it was Blaise Pascal who, in a letter to a friend, said, "I'm sorry for writing such a long letter. I didn't have the time to write a shorter one." 😊 Good, clear writing is not easy, even for something as practical and prosaic as design docs. Like you said though, there are benefits and there are downsides to design docs. When the benefits outweigh the downsides, take the time to write a good design doc. 😊 Thank you for this video. It was useful and fun, as usual.
This is actually one of my favorite quotes of all time, and I occasionally add it at the end of very long emails (I also actually took that from one of my managers at Google 😛).
Your transitions and humor is great. I just feel obligated to smash that like button on every video. Can't wait to dive into AlgoExpert in the next coming weeks. Finishing up school for the semester & it's my last one after 5 1/2 years of work!
I had Software Engineering subject last semester, learned all about SDLCs, SRS Documentations, UML diagrams, Testing, etc. I feel will help me in the long run.
Whenever I write a PRD (think of it like a product manager's version of a design doc), I include an "Open Questions" section where the whole team writes down questions about tricky edge cases that dont have clear answers. I then prioritize each open question (P0, P1, P2, etc) based on urgency so we all know what to devote our attention to and which questions (though important) arent really worth answering at the moment. Super recommend to all doc writers!
Design Doc: implement the feature using natural language, so other people can easily understand how it works. Code: implement the feature in computer programming language, so the machine can make it work.
You're doing great work Clement. So refreshing to see videos about things software engineers have to deal with time to time. Also I love that you covered both the upside and downside of design doc.
In university I have been taught about ER Diagram (backend engineers focus heavily on Database design before any web framework like SpringBoot2(Java)/Hibernate or Phoenix(Elixir)/Ecto) then UML Diagrams (Class, activity diagram) but when I did internship for an average company, there are only UI draw + some notes on the feature. It takes 6 months to design database with a few hundreds of tables but only 2 weeks to implements all the features! Coding is so fast! Ha ha
I would say, designing things for big projects are a big time and resources saver, although the same can't be said for small projects. Implementation is fast after completing design documents as it takes away 90% overhead of implementation and is super maintainable.
Am ajuns aici deoarece cautam un tutoria despre tech doc in Confluence si tare mandra sunt de ce aud. Poate ai sau nu origini romanesti, dar oricum ar fi, succes si bravo!
Ok. I was driving and listening to the video when you said about the background. I was the one who mentioned something about it. I had to stop and see it. So now I'm in the middle of the road writing this comment. Thank you Clement for reading suggestion, and that of other's.
Good start point. I think this video contains only the high level feature description aspect of the design doc . In my experience, the design spec goes quite in details i.e. design pattern, class, methods, use cases, etc. It boils down to what the team standardized for the design doc which actually helps and does not hinder the development.
Thanks Clement for sharing your take on this, I am writing one right now and it really requires a deeper understanding on the technologies you are using, for example I have just learnt so much more about Git after writing a Git workflow for the team.
After going through this video, one thing is clear, I definitely have become a fan of algo expert, I thought it was developed by a big team, but little did I know that there is only a small team of few developers doin that ♥️
Really love this kind of videos talking about "non-programming" part of building a real-world application/website. There are lots of tutorials about programming, whereas there are much less about design, UI/UX, speed, etc. I would like to see videos about how we could build prettier UI/UX application in small companies, how you work on UI/UX of AlgoExpert...
Been waiting for this video, thanks! I knew the purpose of a design doc (it's fairly obvious), but I hadn't seen an actual example before. I might just smash the like button for this 😉👍
So I guess I'm gathering that the mindset for drafting a design doc (as opposed to a white paper) is more like: going into the room with an idea armed with back-up plans to ensure that there is no way for ALL of the time spent on the project will go lemon? I was secretly hoping to see a standard template that Google uses, but I guess TC isn't a big issue at most companies. I just thought it would be easier for everyone to read faster if docs were built on a template. (Yes, I did catch you mentioning that sometimes it's just extraneous, depending on the product being designed.) Thank you for sharing your company's, tho. I really enjoyed this one!
Yooo, I clicked on the video so fast! Also for some reason I liked it before I even watched it! ;) Thank you Clement, this was very informative and also entertaining. Turns out I was already kind of doing it, as I'm always writing down for myself before I start working on things, just to make sure I really know what I want, and to make sure I don't forget along the way why I even started.
Hello sir,my question is little bit different from software engineering. My question is "Do you really know magic or this coin trick is video editing? " I am asking, just because I like watching your videos and it gives me right path to my career. Watching your videos is never a waste of time. I continuously learn new things after watching your videos. Please don't mind sir.
Now please make a video about 1) Backend Tech Stacks 2) What is the process you follow to build a feature from concept to backend, frontend to deployment?
The contentious part of the design and the comment about using PDF instead of an Email should have been addressed in the PRD if you were working at a big company like Google. But I totally understand that the engineers at startup usually take more responsibilities like defining the product.
I think design doc is Important because there is always new developers join the company and others they leave, if you don't have design doc the new developers will struggle to understand the software features, i think it's not an option to build a software without documentations and it's a best practices to work and understand this Important part in software engineering life cycle.
Amazon design doc culture is exactly the same as at Google. It was interesting to know, as I thought the design doc for everything was only an Amazon thing.
I also made a design doc before starting to work on an open source project for Mozilla under Google Summer of Code program this year. My mentor gave me a Project Requirements doc for this.
when you did that magic trick i knew this was gonna be a great video and subbed already. youre hilarious man digging the dad jokes and thank you for the information.
Thanks for the video: really informative! I have a question: where are these design docs stored? How are they linked back to the source code that implements the feature? Thanks!
When it comes to develop some REST API within some micro-services, I suppose we can only have API spec (OpenAPI) as the design doc prior to start implementing the designed APIs ? how does this sound to you ?
Hello Clement, can we please get a video about some hard/unexpected questions asked during the behavioral round in an one site interview with a big tech company (most notably google) and thanks :)
Apart from the comprehensive video explanations, written solutions, and detailed complexity analysis that we provide for every question, AlgoExpert gives you everything in one platform in a very streamlined and guided format. This "all-in-one-place" aspect of the platform is something that our customers have valued a lot and that sets us apart.
@@clem Thank you. I will be making a purchase soon. I have benefited from your youtube content and I do believe that your work is authentic. Thank you and keep it up.
This seems very similar to our developers reviewing the work items in refinement. We discuss how it will be implemented and question the workflow in refinements. Is a big goal of this design doc to have multiple teams have discussions asynchronously over contentious issues and a replacement of a refinement in a way or done before refinements? Perhaps I'm questioning it's place because our work items are so high level already and not specific and our company is not a Google sized engineering group. Maybe we should do this for large features like you mentioned at the end of the video. Great video :)
Is there a common template when writing design documents for software engineering projects? *edit: The key takeaways from your example, at least to me, is that it should have the name of the feature to be implemented (e.g. your example design doc is I believe about gamifying your company features); the abstract; and the brief description of that specific changes.
So I have a question. I'm currently a junior in CS. I'm been learning python. Better improving on data structures. Just what are things I should learn to better improve my chance of getting hired thank you. Great video.
I would be very reluctant to evaluate a design doc that did not include some sort of graphical representation. I find that when designs are presented too abstractly, as is the case with just a big wall of text, it is too hard to conceptualize the design and often leads to mistaken assumptions about the design's feasibility and appropriateness.
I think you should start with a strong point about the video topic instead of trying to do a scattered intro for it as it is distracting and might make people click away. But I personally like the core content you put out. Just offering my point of view
Hi clement, I was just curious to ask how i can become a world class engineer as yourself. Am actually starting out with learning javascript ...using w3schools..etc. But am not sure i have the right path to follow And i dont hav indepth knowledge of what it takes. I really would like to be exposed and mentored by you. I would really love to know what steps you took when you were starting out and will be ok for me to follow and proberbly land a software engineering job . More over i am a student(undergraduate) in africa (Nigeria). I would really appreciate a feed back Thanks.
Lol i got the secret behind your magic trick. He dropped the coin just before transferring it to the other hand. And if you listen closely, you can hear the coin smashing the floor.
Is there not a universal standard for design doc? Similar to PRINCE2 for projects, i.e. a project needs to have as a minimum X and Y, otherwise it wouldn’t be considered or classed as a “PRINCE2 project”. Surely there’s something for design docs / Software design? Great video !
After seeing your project for applying at Google , I came up with my own little project , basically a meme website that's displays memes only from a few subreddits sorted by top,
Do you know for a fact that anyone actually read those docs? In my experience nobody actually reads them, but say they do. I find it better to get everyone in a room and draw them picture, and get a live discussion happening.
Hi Clement, Recently I started a swe internship. Unfortunately, I am running into some serious imposter syndrome. Luckily the person I report to is very kind and has been teaching me some great skills but I feel as I am asking dumb questions and making myself look 'dumb'. As someone who managed and taught interns, do you have any feedback on how to get over/feel better about this? P.S I posted this here because I am sure there are more people in my position (or eventually will be) and thank you for all the great content!
Hey! So first of all, the good news is that, as you probably know, you're far from the only person with impostor syndrome. Tons of people, especially in software engineering, have impostor syndrome (I guess if everyone's an impostor, then there's no such thing as actually being an impostor, is there 🤔#mind=blown). But more concretely, what I told all of my interns, repeatedly so, was that there really are no "dumb" questions; your job as a software engineer is to solve problems, and often times that involves asking questions, even ostensibly silly questions. Also, it's very much expected for engineers who are new to a team, project, or codebase to ask questions, and this is particularly true for SWE interns. So overall, I'd say that your mind is likely playing tricks on you. And finally, here's a video I made specifically on impostor syndrome (with actionable advice) that you might find useful: th-cam.com/video/JnZvhzAX9IE/w-d-xo.html
Hope you all find this video enlightening! And by the way, for those of you who are curious about the Data Structures crash course on AlgoExpert, it’s coming out _very_ soon-just a few more days (from December 9th, 2019)!
Wow, so will it be free for the members. And what language it will be, please make it in c++
:
Would there be a course on System design, in future?
Hi can i have your help please, am working on my project how to communicate to a machine but current its hard for me to make the machine understand that i have finish to talk now it the time for it to reply can you help me how i can work on this my email is danielpoul.dp@gmail.com
Thank you for sharing all of this great knowledge and advice Clement 🙌🏽 Here are the TIMESTAMPS for those that need it ✨
1:05 What is a Design Doc?
4:40 Design Document Example
I think it was Blaise Pascal who, in a letter to a friend, said, "I'm sorry for writing such a long letter. I didn't have the time to write a shorter one." 😊
Good, clear writing is not easy, even for something as practical and prosaic as design docs. Like you said though, there are benefits and there are downsides to design docs. When the benefits outweigh the downsides, take the time to write a good design doc. 😊
Thank you for this video. It was useful and fun, as usual.
This is actually one of my favorite quotes of all time, and I occasionally add it at the end of very long emails (I also actually took that from one of my managers at Google 😛).
Mark Twain*
Clem's videos are so much more useful and interesting than Tech Lead's videos, at least for me
D3FKON Music™ Maybe tech lead is too eager to ask people to enroll in his class, and many ads
As a millionaire I have to disagree
why can't you just enjoy both?
this is exactly what i thought, he is way more informative than techlead.
Clement is a real person, unlike....
Really appreciate the light-hearted humour mixed into the video. Makes it all the more digestible.
Your transitions and humor is great. I just feel obligated to smash that like button on every video.
Can't wait to dive into AlgoExpert in the next coming weeks. Finishing up school for the semester & it's my last one after 5 1/2 years of work!
Love this comment; thanks a lot, and I hope you find AlgoExpert useful!
I had Software Engineering subject last semester, learned all about SDLCs, SRS Documentations, UML diagrams, Testing, etc. I feel will help me in the long run.
Whenever I write a PRD (think of it like a product manager's version of a design doc), I include an "Open Questions" section where the whole team writes down questions about tricky edge cases that dont have clear answers. I then prioritize each open question (P0, P1, P2, etc) based on urgency so we all know what to devote our attention to and which questions (though important) arent really worth answering at the moment.
Super recommend to all doc writers!
Spoken like a true ex-Googler!
Design Doc: implement the feature using natural language, so other people can easily understand how it works.
Code: implement the feature in computer programming language, so the machine can make it work.
and there is your 16 minutes
Good way to sum it all up!
OMG i was treating my design doc as a research paper. And all sorts of other things thanks for the new mindset!
this is a really informative even for a software engineer w/ a few years of experience!! keep up the great work Clem!
you're genuine clement. thank you for being that
You're doing great work Clement. So refreshing to see videos about things software engineers have to deal with time to time. Also I love that you covered both the upside and downside of design doc.
In university I have been taught about ER Diagram (backend engineers focus heavily on Database design before any web framework like SpringBoot2(Java)/Hibernate or Phoenix(Elixir)/Ecto) then UML Diagrams (Class, activity diagram) but when I did internship for an average company, there are only UI draw + some notes on the feature. It takes 6 months to design database with a few hundreds of tables but only 2 weeks to implements all the features! Coding is so fast! Ha ha
I would say, designing things for big projects are a big time and resources saver, although the same can't be said for small projects.
Implementation is fast after completing design documents as it takes away 90% overhead of implementation and is super maintainable.
I love your presentation and content depth! All the best!
Thank you, thank you a million thank you! This video couldn't have come at a better time.
interviewer: what's a design doc.
me: design doc is a document where you design stuff.
interviewer: welcome to the team.
Am ajuns aici deoarece cautam un tutoria despre tech doc in Confluence si tare mandra sunt de ce aud. Poate ai sau nu origini romanesti, dar oricum ar fi, succes si bravo!
Ok. I was driving and listening to the video when you said about the background. I was the one who mentioned something about it. I had to stop and see it. So now I'm in the middle of the road writing this comment. Thank you Clement for reading suggestion, and that of other's.
Good start point. I think this video contains only the high level feature description aspect of the design doc . In my experience, the design spec goes quite in details i.e. design pattern, class, methods, use cases, etc. It boils down to what the team standardized for the design doc which actually helps and does not hinder the development.
Thanks Clement for sharing your take on this, I am writing one right now and it really requires a deeper understanding on the technologies you are using, for example I have just learnt so much more about Git after writing a Git workflow for the team.
After going through this video, one thing is clear, I definitely have become a fan of algo expert, I thought it was developed by a big team, but little did I know that there is only a small team of few developers doin that ♥️
Really love this kind of videos talking about "non-programming" part of building a real-world application/website. There are lots of tutorials about programming, whereas there are much less about design, UI/UX, speed, etc. I would like to see videos about how we could build prettier UI/UX application in small companies, how you work on UI/UX of AlgoExpert...
Really glad you enjoy this type of stuff, and I'm planning on doing more of these other-aspects-of-software-engineering videos!
@@clem Thanks for your reply, really looking forward...
@@clem Je viens d'apprendre que tu es français... Notre entreprise est en France...
Great video pal. Very informative explanation for something I was meaning to research but forgot about. Keep in up.
Awesome; glad you liked it!
2AM on a Monday, ❤️ your dedication! 🤩 loving your content, keep up the awesome work! 👍
a minor observation: it\ seems common to confuse capitalism with trade. Both exists but trade is far older.
Was looking forward to this one. Thank you!
Been waiting for this video, thanks! I knew the purpose of a design doc (it's fairly obvious), but I hadn't seen an actual example before. I might just smash the like button for this 😉👍
So I guess I'm gathering that the mindset for drafting a design doc (as opposed to a white paper) is more like: going into the room with an idea armed with back-up plans to ensure that there is no way for ALL of the time spent on the project will go lemon?
I was secretly hoping to see a standard template that Google uses, but I guess TC isn't a big issue at most companies. I just thought it would be easier for everyone to read faster if docs were built on a template. (Yes, I did catch you mentioning that sometimes it's just extraneous, depending on the product being designed.) Thank you for sharing your company's, tho. I really enjoyed this one!
I haven’t seen anyone making the immature joke about the 69K subs so I’ll be the one to make it:
69K subs!! 😏😏
nice.
noice
Gotta 😏while we can; it'll soon be 70K!
Noice
just as a side note. You can find public design docs from google, for example around angular
Yooo, I clicked on the video so fast! Also for some reason I liked it before I even watched it! ;)
Thank you Clement, this was very informative and also entertaining. Turns out I was already kind of doing it, as I'm always writing down for myself before I start working on things, just to make sure I really know what I want, and to make sure I don't forget along the way why I even started.
Hello sir,my question is little bit different from software engineering. My question is "Do you really know magic or this coin trick is video editing? "
I am asking, just because I like watching your videos and it gives me right path to my career. Watching your videos is never a waste of time. I continuously learn new things after watching your videos.
Please don't mind sir.
The Best TH-cam channel with very good content.I love this channel soo soo much.Love your channel clement.
Now please make a video about 1) Backend Tech Stacks 2) What is the process you follow to build a feature from concept to backend, frontend to deployment?
Clement your videos are so informative,Amazing content.
The contentious part of the design and the comment about using PDF instead of an Email should have been addressed in the PRD if you were working at a big company like Google. But I totally understand that the engineers at startup usually take more responsibilities like defining the product.
Also, how do you configure your servers (e.g., location, CPU, memories) at AlgoExpert to have a better speed?
This is so helpful! Thank clem.
pretty interesting video...and important one video for frontend software developers
Thanks, it was informative
I think design doc is Important because there is always new developers join the company and others they leave, if you don't have design doc the new developers will struggle to understand the software features, i think it's not an option to build a software without documentations and it's a best practices to work and understand this Important part in software engineering life cycle.
Great insights and experience, Thanks for this.
Nice video content। Quite informative । Keep making these type of videos Sir
Thanks, Mr Lispy
Amazon design doc culture is exactly the same as at Google. It was interesting to know, as I thought the design doc for everything was only an Amazon thing.
at 3:54 i realized that u were the brilliant guy behind algo expert ads! lol
Really funny and nice intro, I played it quite a few times 👍
I also made a design doc before starting to work on an open source project for Mozilla under Google Summer of Code program this year. My mentor gave me a Project Requirements doc for this.
YESSSS THIS IS EXACTLY WHAT I NEED!!!
Yesssss!!
when you did that magic trick i knew this was gonna be a great video and subbed already. youre hilarious man digging the dad jokes and thank you for the information.
I would buy a DesignDocExpert
Useful video as always. One question, did you have to work overtime at google?
Thanks - this was very insightful! :)
so learning how to write a design doc is great, but where do you recommend keeping them?
Thanks for the video: really informative! I have a question: where are these design docs stored? How are they linked back to the source code that implements the feature? Thanks!
When it comes to develop some REST API within some micro-services, I suppose we can only have API spec (OpenAPI) as the design doc prior to start implementing the designed APIs ? how does this sound to you ?
Do we have lifetime access to algoexpert or it is on monthly basis
P.S. Love your work and magic
It can be accessed for one year after purchasing the course.
@@gari2209 so its for $85/yr
@@skshmpareek Yes.
this was VERY useful
Instead of writing abstract in view drawing rough flow diagram is much more visual and easily understandable
Hello Clement, can we please get a video about some hard/unexpected questions asked during the behavioral round in an one site interview with a big tech company (most notably google) and thanks :)
Clement,
I want to use AlgoExpert, but can you tell me how it is different from Leetcode? Why should I invest in AE rather than LC? Thanks.
Apart from the comprehensive video explanations, written solutions, and detailed complexity analysis that we provide for every question, AlgoExpert gives you everything in one platform in a very streamlined and guided format. This "all-in-one-place" aspect of the platform is something that our customers have valued a lot and that sets us apart.
@@clem Thank you. I will be making a purchase soon. I have benefited from your youtube content and I do believe that your work is authentic. Thank you and keep it up.
This seems very similar to our developers reviewing the work items in refinement. We discuss how it will be implemented and question the workflow in refinements.
Is a big goal of this design doc to have multiple teams have discussions asynchronously over contentious issues and a replacement of a refinement in a way or done before refinements?
Perhaps I'm questioning it's place because our work items are so high level already and not specific and our company is not a Google sized engineering group. Maybe we should do this for large features like you mentioned at the end of the video.
Great video :)
Is there a common template when writing design documents for software engineering projects?
*edit:
The key takeaways from your example, at least to me, is that it should have the name of the feature to be implemented (e.g. your example design doc is I believe about gamifying your company features); the abstract; and the brief description of that specific changes.
So I have a question. I'm currently a junior in CS. I'm been learning python. Better improving on data structures. Just what are things I should learn to better improve my chance of getting hired thank you. Great video.
Thanks bro! 👍
You don't have to unblur test cases since the tests are sent via a rest call lol :D
Are all design docs, this small? I am told to spec out a solution for one of the features at company.
I would be very reluctant to evaluate a design doc that did not include some sort of graphical representation. I find that when designs are presented too abstractly, as is the case with just a big wall of text, it is too hard to conceptualize the design and often leads to mistaken assumptions about the design's feasibility and appropriateness.
I think you should start with a strong point about the video topic instead of trying to do a scattered intro for it as it is distracting and might make people click away. But I personally like the core content you put out. Just offering my point of view
Always appreciate the feedback; thanks!
Very informative!
Hahahaha your mic catched the coin falling down 😂
Hi clement,
I was just curious to ask how i can become a world class engineer as yourself.
Am actually starting out with learning javascript ...using w3schools..etc.
But am not sure i have the right path to follow And i dont hav indepth knowledge of what it takes. I really would like to be exposed and mentored by you.
I would really love to know what steps you took when you were starting out and will be ok for me to follow and proberbly land a software engineering job .
More over i am a student(undergraduate) in africa (Nigeria).
I would really appreciate a feed back
Thanks.
Lol i got the secret behind your magic trick.
He dropped the coin just before transferring it to the other hand.
And if you listen closely, you can hear the coin smashing the floor.
On the topic of AlgoExpert certificate, how about letting users be able to add it to their LinkedIn profile? :)
Yes, we're planning on doing that!
Is there not a universal standard for design doc? Similar to PRINCE2 for projects, i.e. a project needs to have as a minimum
X and Y, otherwise it wouldn’t be considered or classed as a “PRINCE2 project”. Surely there’s something for design docs /
Software design? Great video !
This is high quality stuff
Glad you think so!
This content is soo helpful and informative . I want to see u as a billionaire someday
After seeing your project for applying at Google , I came up with my own little project , basically a meme website that's displays memes only from a few subreddits sorted by top,
@@reaperforever8478 Awesome, sounds fun and actually pretty useful! And I bet you learnt a lot from doing it.
Do you know for a fact that anyone actually read those docs? In my experience nobody actually reads them, but say they do. I find it better to get everyone in a room and draw them picture, and get a live discussion happening.
Are design docs recommended for small startups?
Hi Clement,
Recently I started a swe internship. Unfortunately, I am running into some serious imposter syndrome. Luckily the person I report to is very kind and has been teaching me some great skills but I feel as I am asking dumb questions and making myself look 'dumb'. As someone who managed and taught interns, do you have any feedback on how to get over/feel better about this?
P.S I posted this here because I am sure there are more people in my position (or eventually will be) and thank you for all the great content!
Hey! So first of all, the good news is that, as you probably know, you're far from the only person with impostor syndrome. Tons of people, especially in software engineering, have impostor syndrome (I guess if everyone's an impostor, then there's no such thing as actually being an impostor, is there 🤔#mind=blown). But more concretely, what I told all of my interns, repeatedly so, was that there really are no "dumb" questions; your job as a software engineer is to solve problems, and often times that involves asking questions, even ostensibly silly questions. Also, it's very much expected for engineers who are new to a team, project, or codebase to ask questions, and this is particularly true for SWE interns. So overall, I'd say that your mind is likely playing tricks on you. And finally, here's a video I made specifically on impostor syndrome (with actionable advice) that you might find useful: th-cam.com/video/JnZvhzAX9IE/w-d-xo.html
@@clem Awesome, thank you for that feedback Clement! I will keep it in my back pocket :)
great content, thanks
Are you 100% english? Your name is strange (roman? :D), and if you're not native, your accent is impeccable.
By Design Doc, do you mean overall "System Design Doc"? Or just a feature/problems "Solution Design Doc"?
Perhaps you should try watching the video
Hi Clem, I am trying to purchase your bundle offer but not able to process!! From India
Thanks man! Please tell us about development environment setups and tools at Google.
wait if you look really closely theres a coin at the beginning and then it suddenly disappears. did anybody else notice that
I was going to watch but then the magic trick made me like - I'm out...
I think you need a design document for your wall design. Oh and TDD.
Great video Climent, I am new to SE learning my first language, Python. Is there a way you can share this design doc as a download doc?
You can hear the coin fall lol
Case study in ui/ux design is similar to design doc in software engineering?
Like I always say, you are awesome bro :)
like button smashed
Are you talking about SRS document?
bro u are awesome
He dropped it (like it's hot lol) 0:03
who's techlead? But I know Clement Mihailescu
Video starts at 4:40
Nice callouses
0:03 you can hear the coin hit the floor 😂