Portfolio Preparation: Building a Postman Clone Course
ฝัง
- เผยแพร่เมื่อ 15 ก.ย. 2024
- In this lesson, we are going to turn our project into a portfolio item. We are going to do this by upgrading our readme, adding screenshots and explanations, and by publishing a working version of our application. This will then be something we could show off to others and include in our portfolio.
Full Training Courses: IAmTimCorey.com
Amazing! Nobody teaches this subject, everyone just tells how to code, glad you made it.
I am glad it was helpful.
You are truly a great teacher Tim.
Not everyone teaches like this. Thanks for making an effort to make such content.
Thank You!
Tip: Alt+Print Screen will capture just the window so you don't have to worry about what else is showing on your desktop
Thanks for sharing. I prefer to have more control over the screenshot so I use the Win+Shift+S method.
Thanks for these videos, Tim. As someone who was fortunate to get a job before worrying about having a portfolio, I find this series very helpful now that I want to start one the right way.
You are welcome.
If you're familiar with HTML you can actually use the tag in markdown instead of the standard markdown way of adding pics. This will allow you to set width and height on the tag. I wouldn't go overboard, though. You don't want to see the pics load in inch by inch for a UI with just a button and some text fields and I'd say a width over 1000px isn't going to look great in an .md file.
Yep, you can. I'm not a huge fan of mixing HTML and markdown, but it works in a pinch.
@@IAmTimCorey I'm usually a purist myself but I'm convinced markdown was never supposed to include images. It was designed to make better looking .txt files with clickable links with hardly any formatting. Images need formatting.
I wouldn't consider adding an image to an .md file anywhere else but a GitHub repository readme. Also, the implementation feels so tacked on (link that's not a link -> ![link]) that I can forgive myself.
😂 "...let's zoom in. There we go! You can actually read the f text now."
This little hint of "I'm just an human to" made me smile.
😂 Yep, I'm definitely just a normal human.
Awesome tutorial. So many useful tips I'm taking away from this one. Thanks Tim.
You are welcome.
Great Video!
29:17 my answer was unit tests, and maybe some sort of CI/CD pipeline,
Thanks for sharing.
Thank you again, Tim
You are welcome.
Wow, this is very useful
Great!
Looking forward for next episode ❤
Great!
Thanks 👍
You are welcome.
I love this series, I have some C# portfolio pieces I want to show off at their best so this is great. I am very worried about the 150mb executable though.
Will an employer think "that's a big file size for a small app" I know you said in the vid it didn't bother you but will others? Is that a thing to put in the readme? Won't that invite the interview question why is this so big for what it does?
You could clarify in the Readme if you wanted to. It shouldn't bother anyone, especially when you say that it is a stand-alone app. If it does invite questions in the interview, that would be a great opportunity. You could talk about wanting to make it as easy as possible on users, so you included .NET as a part of the application so that it could run on any Windows machine. You could also talk about not wanting to shrink the file to only the parts of .NET that it uses because it was a frequently updated exe as you expand the app and you don't want to debug it each time to be sure nothing was missed from .NET. You could talk about your cost/benefit analysis of your time adding new features vs your time validating the shrinking feature was working properly for each build. These are excellent conversations to have with an interviewer.
Don't forget that you actually want to give an interviewer something to talk about. If there is something obvious that they might want to talk about, you can plan for it and be ready to have a great conversation. If you eliminate all of these that you can find, the conversation can go anywhere and you might not be prepared for every eventuality.
@@IAmTimCorey Thank you very much!