In my 20+ years coding professionally, I wish I would have known more the emphasize of "Don't be so strict". This is so important. It won't be perfect and refactoring is a term that people tend to forget. You can write code in a way that you prepare for easier refactoring, but don't have to spend so much time on getting everything "perfect". Great video!
1. Draw out how you want the project (website, app, etc) to look [3:09] 2. Do some research to get a better understanding of the project details [3:54] 3. Leave minor or less important details (colors, fonts, etc.) for later [4:16] 4. Decide which technologies to use (frontend, backend, frameworks, database, etc..) [4:28] 5. Figure out what you should be doing first [4:56] 6. Time to code!! [7:28] 7. Build a schedule, but don't set deadlines [9:36] 8. GOLDEN TIP: Always leave yourself with something to do the next day! [11:17]
Dude you're just saving me from myself, because I'm kinda overwhelmed by all these "Industrial Standards" created everyday by tons of programming teams. I like to think that programming is more an art than just a science, it helps me to enjoy more the process and charge me less. Thanks for that, Forrest!
I constantly get frustrated when people expect every program I write and every project I take on to be a complete, enterprise-level application or retail software product with every imaginable feature set and configuration, and they tend to have this idea in their head about how the interface should look based more on 1950s sci fi movie theatrical computers with flashing lights and beeping and buzzing sounds But most of my programming involves quick one to perhaps a few hundred lines of code to complete a specific task. And even when I take on more complex projects, I'm just one guy. I can't create a robust enterprise application in a week all by myself. I can give you a minimally viable product that reliably produces whatever out out you wanted, using whatever input you gave me. I can't build in New features you didn't know about until the delivery date, and I can't make it fix your mistakes until I have some samples of them after you've made a few.
Great content! I consider myself a hobby level programmer, though I do have a CS Bachelors. One of the hardest things I always found when starting a new project is figuring out HOW to get started. I 100% subscribe to the minimum viable product idea. Just get the basics working, and if you’ve managed to write extensible code it’s MUCH easier to add features as needed.
Most of the time I plan out the project before writing any codes; it makes me see the big picture and its fun. I ask a lot of questions from the business before starting any development and depending on the project scope. This is programming.
I was taught programming in the 1980s in high school, the old school way. We even had to buy a plastic flowchart template so we could first draw out the logic and flow of the program before we ever sat down at a keyboard. We started every programming project by drawing an oval at the top of a graph paper that said START with an arrow, then we built out each step, each branch, every loop or condition, etc until the last box was the desired result, or END condition. But my professional programming was as a web developer for a finance publisher. Everything I ever wrote professionally was a wing it, minimally viable product type of project. I even once built a entire content management system with file sharing and group calendar for an editorial team simply by starting at
Bro... I found this video trying to figure out how to use Jira to help me structure myself to finish projects. I'm glad that I did because I feel like I'm already getting board with the project I started on this with. We have a similar way of looking at coding and your video helped me to remember why I started this in the first place. I have gotten so wrapped up in the ever changing "Industry Standards" and "Best Practices" that I forgot to enjoy myself. I guess we all get that sometimes but I appreciate you bro! You earned a Sub!
Have not written code for a job in almost 20 years it was daunting thinking about the first steps I took all those years ago. I have a medium sized project in mind and it was refreshing to learn, again, that I really just need to download visual studio and start.. if I need diagrams later to figure stuff out then that's when I'll reacclimate myself with dia or whatever.. no more video research. Here I go.. already started the install.. thank you for the inspiration..
I laughed when he ended with the tip “always leave yourself with something to do the next day”, cause I always leave myself with a skull crushing bug to fix 😂😂 so maybe that advice shouldn’t be “taken as you will”
"skull crushing bug" Bwahaha! That description is so good! xD When this happens my sleep is always troubled. Sometimes I'll realize the solution in my dreams and it will wake me right the fuck up xD Then I hurry to type, test or sketch the solution and go back to perfect sleep.
@@ironbard4901 lol you're not alone, I'll even be thinking about that bug mid-conversation sometimes 😂 It's fascinating when you're not thinking about it and an idea for a potential solution suddenly pops into your head
80% of all the bugs i ever get stuck on, i solve instantly the next morning after some good sleep. at this point i just do it intentionally and try not to get stuck on something for more than an hour or two before just moving on
If you spend the whole day researching, spend the whole day researching. If you get a lot done, you get a lot done. Just focus that time slot no distractions on your project on a consistent basis and you're already ahead of most other individuals trying to do the same thing -Forrest Knight (TH-cam channel)
When you said don't set deadlines, I couldn't agree more. Everyone always says how important deadlines are to stick to. Then you see what they completed & find that with a slight bit more attention to detail, it could have turned average work into great work. Thanks for a good video!
i've abandoned so many projects because i wasted way too much time on Figma to make hifi mockups for projects for which i had a very very clear image in my head - and therefore didn't actually need a mockup for - is kinda insane. haven't done that for the one i'm currently working and it made a world of a difference in my motivation. i'm actually working on the project and achieving things instead of just giving up lol. insane
You are my favorite coder..screw that you are my favorite TH-camr!I like your approach how you discuss things your thinking about.I have literally just started learning to code.I have been working on Html and once i feel comfortable enough to make a webpage without constantly looking at a book or video i will move on.I try to work an hour a day but sometimes life gets in the way.But i am still gonna keep pushing.Basically what i am saying is thanks for being you and doing what you do for us!
get rid of that mentality of making something without looking at a book or a video, research and finding answers are the greatest skills of programmers. Oh and add stealing to that.
This makes me feel a lot better about my "Meh - I'll just wing it" attitude towards personal projects. I'll definitely do things like creating a database schema since planning that out properly will save me time later but there's a lot of things I'm just rolling with, haha.
Having a consistent time to sit down and work on your project, even if it's 15-30 minutes, is huge for making progress. That's really the only structure that I've found valuable.
This video is gold. I'm currently working on a project and everywhere I go I see people saying to do this or that, 100 steps just to set things up before code and most of it won't be that useful and really unmotivates us. Glad to hear I'm not the only one
Im also a disciple of first sketching the UI's before coding, such an elegant method 😎😎. I used to just start coding, like that and trying to figure out next step later but using a piece of paper to first figure out your general plan is such a gem.
In general (not just in IT) you should plan your project from the desired end state backwards. I boiled this down to the maxim: “destination drives design”.
At work I use miro to make clickable Lo-fi wireframes to interpret client requirements. It’s amazing how much easier the process flows when you start with something simple you can visualise
By accident I stumbled over your video. I basically do all my personal and professional projects as you say. And I enjoy programming! I was a professional software engineer and lost my passion for programming, with all the rules and restrictions modern organizations demand and moved to product management. There my programs helps me to get my or others, jobs to be done more efficently. The last 2 hints I found very useful, plan a dedicated timeslot regularly and set a new task every time to keep the privat project going on.
I definitely did try to do the whole user stories, domain model, mockup, and deadline route with a project I actually liked but then, like you said, I missed a deadline and I haven't touched it for months now. You were right lol
It's funny, after trying to set deadlines and stressing out (exactly as Forrest described) I ended up just going with the flow after getting a basic idea of what I need. I still stress about getting things perfect and I tend to refactor a lot to try and get things perfect (so it takes a long time for me to get shit done tbh). Probably a bad trait to have... but I'm trying to build these projects for my Portfolio so I hold them to a high standard.
I’m not far into my career, but I do a lot of this in the same way. Go with the flow and structure things in whatever way the work progresses forward. Don’t get too bogged down as long as you understand and can explain what you did.
Hi Forrest, I'm 28 and from Guatemala, and I don't know why nor How I started to have some interest on codying, and I'm so grateful that I found this excelent channel. Just Keep it like now. Your videos are so great.
I was worried about starting to work on a personal project with a potentially high rate of return in the near future. I was scared to start working on the MVP and was lost in these "industry standards". Your video has proven alot of assumptions I had wrong. I am setting up a schedule to work on this consistently and go easy on it and have fun coding it out. I will treat it more like an art than science. Thank you for the valuable insights.
I recommend Rich Hickey's approach of "Hammock Driven Design". The TLDR; is that the cheapest place to fix a bug is on the whiteboard. Spend less time on the keyboard and more time in design (with the team and the client). Planning is such an underrated tool in the industry. Most clients I work with want bums in chairs and hands on keyboards. A year later they wonder why the software is unmaintainable.
Love your vids and overall down to earth personality. I’ve been a developer for a while now and I definitely wing it on personal stuff. If I spend much time trying to plan I end up never starting. Better to try, see room for improvement, refactor and move along. That’s also the best way for me to remember things. Like you said, just dedicate the time to it.
I was f-ed up for so long by unrealistic personal deadlines that piled up, never actually getting done. Turns out it's a perfect way to ruin motivation (and will to live, frankly speaking). So yeah, the finesse advice is right on point, thank you for the video!
I agree with your overall message for doing solo coding projects, as using industry-standard workflows and tools at all times is definitely overwhelming and a lot of extra unnecessary work (as you mentioned, for collaboration/communicating your work to others.. since you are the only one on the project) That being said though, if you are serious about getting a job in the industry and are in a situation where you still don't have a foot in the door, I highly recommend against this, and instead recommend that you use all of these tools and workflows as getting used to it ahead of time will make you more desirable from a job-market point of view. Saying that you have experience from private projects making simple UI mockups and UML diagrams for your planned features, and also going through the motions of then making issues and storing that documentation within JIRA/Confluence (or another industry standard equivalent) before... this is a huge plus for hiring you over other inexperienced workers from a hiring manager's point of view. It shows you're dedicated and doing everything you can to build yourself up without yet getting an official opportunity to do so yet as well! Anyhow, for those solo-projects you do on the side while working an industry-standard job, then I totally get ForrestKnight's suggestions and agree, but just keep ↑ in mind as well if that advice is applicable to you in your situation! :)
This is really awesome content. Love how you emphasize throughout the video that there's no rigid way on how to do things (as it should be). though I'm not really that interested in web development this was still really helpful
Software development is an art not science only, well said. I wish more people think in this way the organization can build a lot better products, in my opinion.
It's videos like this is the reason why i am subscribed to this channel thank you for making programming so much easier and comforting Forrest. I have to ask an advice i am looking to get my first devops job in IT i have no experience the field but am finishing my bachelors in computer systems technology i have 3 certs in aws any tips for interviews, etc anything would be greatly appreciated thank you Forrest and keep up the great work :)
My advice would be: 1. sometimes go broad and shallow (basically the MVP) to get a rough idea and get something running to enjoy. 2. Sometimes take a small part of it and go deep, deep down and make the details perfect to explore complexity and pitfalls of _difficult_ tasks, especially when you are new to a technology, language, framework. 2b: Hot tip: from time to time aim to intentionally try something new, a new algorithm, some new commands, some other way to do _even when you could do it the usual way_ . You will always learn something, and be it that the fancy shiny stuff was a dead end, but now you have experienced _why_ by yourself. 3. Sometimes develop and debug critical subsystems in a separate sandbox or simulator to get these straight without the weight and the dependencies of the whole project. That also helps to get interfaces right (testing...). And yeah, I totally support the idea to be relaxed and switch between these subjects by gut feeling and day performance. Don't be the "The steak is perfectly grilled, now let's start peeling the potatoes" guy...
My biggest takeaway: as a solo developer, consider approaching projects favoring the advantages of myself as an individual as opposed to a team of individual talents. Very helpful looking forward, thanks for the perspective!
You got my like when you said an mvp doesnt need all the stuff that causes barriers and gets in your way. Iv been saying this for years. Just because a tool exists, doesnt mean you need to use it.
00:00 Planning coding projects can vary from professional to personal projects 01:26 Tab 9 is a good code completion tool 02:58 Discussion on creating a personal website using HTML, CSS, and JavaScript 04:22 Research and planning are crucial before starting development. 05:58 Create a simple MVP for Social Leader leaderboard 07:17 Start building your personal project without worrying about professional practices. 08:46 Start coding with boilerplate and figure things out as you go. 10:12 Treat coding like an art, not a science
This is great advice, Forrest! 😊 Im a newbie coder here although I have a background in art and design, one thing i like to do especially when Im learning a new programming language, ill learn some basics first enough to get started on a project, but then some days ill take what Ive learnt and combine that with my love of making art. Ive been making visual art for most of my life and code to me can be another medium the same way that paint and brushes are. Its the act of removing the pressure of having to get to a specific outcome ALL of the time and allowing myself to have fun with and experiment with code, that furthers the learning process for me. Any other code artists out there? 😊
@@lameprotagonist4275 No, I got some more kinda important things to do ASAP... Some test tasks to try to become an intern... University exam, the last one... That isn't an excuse. I did not start yet
This video is fantastic and is on point. I am a hobbyist python programmer and love the coding experience based on the views you have just mentioned. The best part for me is to ensure I leave a piece of the meal for the next day, and so on. There is always the eagerness for me to complete the project. The only tool I use is the free Trello Board. Thanks for the Video, and I will be watching out for more content.
I literally just paused the video to get the Tabnine extension. I might end up buying depending on how much I like it. This sounds like Kite without the creepy monitoring that Kite did. I might end up purchasing a license.
I saw a video in which he was giving advice on tech stuffs , a guy in comment said same thing "if Jesus himself telling me this then who I am to deny it "
I recently wrote my first "program" a month into a Python course. I started by opening an MS Excel document, performing some excel operations with code, and then saving the file. The mystery of coding has been solved. Do some useful stuff and save your work.
I have been creating many apps in my whole programming journey and I really enjoyed the ladder experience, I don't have anxiety of thinking if can do it or not I just enjoy the road, but now I feel I need to learn how to plan things before hopping to my text editor hahaha and it's gives me anxiety haha I hope I overcome it .
In my 20+ years coding professionally, I wish I would have known more the emphasize of "Don't be so strict". This is so important. It won't be perfect and refactoring is a term that people tend to forget. You can write code in a way that you prepare for easier refactoring, but don't have to spend so much time on getting everything "perfect".
Great video!
now you have 22+ years of experience of coding
Just when I’m starting a project!
Forgetting about deadlines is a huge tip and a very accurate take on it.
1. Draw out how you want the project (website, app, etc) to look [3:09]
2. Do some research to get a better understanding of the project details [3:54]
3. Leave minor or less important details (colors, fonts, etc.) for later
[4:16]
4. Decide which technologies to use (frontend, backend, frameworks, database, etc..) [4:28]
5. Figure out what you should be doing first [4:56]
6. Time to code!! [7:28]
7. Build a schedule, but don't set deadlines [9:36]
8. GOLDEN TIP: Always leave yourself with something to do the next day! [11:17]
Noice
Hero without the cape!
Dude you're just saving me from myself, because I'm kinda overwhelmed by all these "Industrial Standards" created everyday by tons of programming teams. I like to think that programming is more an art than just a science, it helps me to enjoy more the process and charge me less. Thanks for that, Forrest!
I constantly get frustrated when people expect every program I write and every project I take on to be a complete, enterprise-level application or retail software product with every imaginable feature set and configuration, and they tend to have this idea in their head about how the interface should look based more on 1950s sci fi movie theatrical computers with flashing lights and beeping and buzzing sounds
But most of my programming involves quick one to perhaps a few hundred lines of code to complete a specific task. And even when I take on more complex projects, I'm just one guy. I can't create a robust enterprise application in a week all by myself. I can give you a minimally viable product that reliably produces whatever out out you wanted, using whatever input you gave me. I can't build in New features you didn't know about until the delivery date, and I can't make it fix your mistakes until I have some samples of them after you've made a few.
It’s art
Hi can I have your number, I need your assistance
So to the point , this are my current thoughts...wondering if you still think the same after all it beens 2 years of this comment
@@jagrutibiswal5185 Yes, I do.
Great content! I consider myself a hobby level programmer, though I do have a CS Bachelors. One of the hardest things I always found when starting a new project is figuring out HOW to get started. I 100% subscribe to the minimum viable product idea. Just get the basics working, and if you’ve managed to write extensible code it’s MUCH easier to add features as needed.
Something like: build the house first and THEN you mess around with the furniture places hahah
Most of the time I plan out the project before writing any codes; it makes me see the big picture and its fun. I ask a lot of questions from the business before starting any development and depending on the project scope. This is programming.
I was taught programming in the 1980s in high school, the old school way. We even had to buy a plastic flowchart template so we could first draw out the logic and flow of the program before we ever sat down at a keyboard. We started every programming project by drawing an oval at the top of a graph paper that said START with an arrow, then we built out each step, each branch, every loop or condition, etc until the last box was the desired result, or END condition.
But my professional programming was as a web developer for a finance publisher. Everything I ever wrote professionally was a wing it, minimally viable product type of project. I even once built a entire content management system with file sharing and group calendar for an editorial team simply by starting at
Bro... I found this video trying to figure out how to use Jira to help me structure myself to finish projects. I'm glad that I did because I feel like I'm already getting board with the project I started on this with. We have a similar way of looking at coding and your video helped me to remember why I started this in the first place. I have gotten so wrapped up in the ever changing "Industry Standards" and "Best Practices" that I forgot to enjoy myself. I guess we all get that sometimes but I appreciate you bro! You earned a Sub!
Have not written code for a job in almost 20 years it was daunting thinking about the first steps I took all those years ago. I have a medium sized project in mind and it was refreshing to learn, again, that I really just need to download visual studio and start.. if I need diagrams later to figure stuff out then that's when I'll reacclimate myself with dia or whatever.. no more video research. Here I go.. already started the install.. thank you for the inspiration..
I'm trying to build a prototype chemistry simulator.....wish me luck
Luck is upon you.
You got this
I bless you to succeed
How did it go?
Best of luck (if you haven't already completed it) 😁👍
I laughed when he ended with the tip “always leave yourself with something to do the next day”, cause I always leave myself with a skull crushing bug to fix 😂😂 so maybe that advice shouldn’t be “taken as you will”
"skull crushing bug" Bwahaha! That description is so good! xD When this happens my sleep is always troubled.
Sometimes I'll realize the solution in my dreams and it will wake me right the fuck up xD Then I hurry to type, test or sketch the solution and go back to perfect sleep.
@@ironbard4901 lol you're not alone, I'll even be thinking about that bug mid-conversation sometimes 😂 It's fascinating when you're not thinking about it and an idea for a potential solution suddenly pops into your head
lmao
80% of all the bugs i ever get stuck on, i solve instantly the next morning after some good sleep. at this point i just do it intentionally and try not to get stuck on something for more than an hour or two before just moving on
🤣
If you spend the whole day researching, spend the whole day researching.
If you get a lot done,
you get a lot done.
Just focus that time slot no distractions on your project on a consistent basis and you're already ahead of most other individuals trying to do the same thing
-Forrest Knight (TH-cam channel)
When you said don't set deadlines, I couldn't agree more. Everyone always says how important deadlines are to stick to. Then you see what they completed & find that with a slight bit more attention to detail, it could have turned average work into great work. Thanks for a good video!
i've abandoned so many projects because i wasted way too much time on Figma to make hifi mockups for projects for which i had a very very clear image in my head - and therefore didn't actually need a mockup for - is kinda insane. haven't done that for the one i'm currently working and it made a world of a difference in my motivation. i'm actually working on the project and achieving things instead of just giving up lol. insane
You are my favorite coder..screw that you are my favorite TH-camr!I like your approach how you discuss things your thinking about.I have literally just started learning to code.I have been working on Html and once i feel comfortable enough to make a webpage without constantly looking at a book or video i will move on.I try to work an hour a day but sometimes life gets in the way.But i am still gonna keep pushing.Basically what i am saying is thanks for being you and doing what you do for us!
get rid of that mentality of making something without looking at a book or a video, research and finding answers are the greatest skills of programmers. Oh and add stealing to that.
I really like the way you go about your project. I'm also exited for your future projects keep up the great content.
Since I barely have time code now, I just come here and get my dose of code 😬 Love the videos dude!
Much appreciated, Andres! Keep up the good work on your channel.
This makes me feel a lot better about my "Meh - I'll just wing it" attitude towards personal projects. I'll definitely do things like creating a database schema since planning that out properly will save me time later but there's a lot of things I'm just rolling with, haha.
Having a consistent time to sit down and work on your project, even if it's 15-30 minutes, is huge for making progress. That's really the only structure that I've found valuable.
This video is gold. I'm currently working on a project and everywhere I go I see people saying to do this or that, 100 steps just to set things up before code and most of it won't be that useful and really unmotivates us. Glad to hear I'm not the only one
did you finish your project and if yes what is it about?
9:39 Yes having a schedule is a major key factor for staying consistent I've learnt this first hand this week.
Im also a disciple of first sketching the UI's before coding, such an elegant method 😎😎. I used to just start coding, like that and trying to figure out next step later but using a piece of paper to first figure out your general plan is such a gem.
In general (not just in IT) you should plan your project from the desired end state backwards. I boiled this down to the maxim: “destination drives design”.
At work I use miro to make clickable Lo-fi wireframes to interpret client requirements. It’s amazing how much easier the process flows when you start with something simple you can visualise
I'm gonna be honest... I got distracted by the keyboard...
Knight in shining armour, awesome content dude 🔥 👨💻
By accident I stumbled over your video. I basically do all my personal and professional projects as you say. And I enjoy programming! I was a professional software engineer and lost my passion for programming, with all the rules and restrictions modern organizations demand and moved to product management. There my programs helps me to get my or others, jobs to be done more efficently.
The last 2 hints I found very useful, plan a dedicated timeslot regularly and set a new task every time to keep the privat project going on.
I definitely did try to do the whole user stories, domain model, mockup, and deadline route with a project I actually liked but then, like you said, I missed a deadline and I haven't touched it for months now. You were right lol
It's funny, after trying to set deadlines and stressing out (exactly as Forrest described) I ended up just going with the flow after getting a basic idea of what I need. I still stress about getting things perfect and I tend to refactor a lot to try and get things perfect (so it takes a long time for me to get shit done tbh). Probably a bad trait to have... but I'm trying to build these projects for my Portfolio so I hold them to a high standard.
I’m not far into my career, but I do a lot of this in the same way. Go with the flow and structure things in whatever way the work progresses forward. Don’t get too bogged down as long as you understand and can explain what you did.
Hi Forrest, I'm 28 and from Guatemala, and I don't know why nor How I started to have some interest on codying, and I'm so grateful that I found this excelent channel. Just Keep it like now. Your videos are so great.
I was worried about starting to work on a personal project with a potentially high rate of return in the near future. I was scared to start working on the MVP and was lost in these "industry standards". Your video has proven alot of assumptions I had wrong. I am setting up a schedule to work on this consistently and go easy on it and have fun coding it out. I will treat it more like an art than science. Thank you for the valuable insights.
I recommend Rich Hickey's approach of "Hammock Driven Design". The TLDR; is that the cheapest place to fix a bug is on the whiteboard. Spend less time on the keyboard and more time in design (with the team and the client). Planning is such an underrated tool in the industry. Most clients I work with want bums in chairs and hands on keyboards. A year later they wonder why the software is unmaintainable.
I love it!!! Awesome content Forrest. You are really on top of it, even with the new baby. I hope there aren't to many sleepless nights. 😁
Love your vids and overall down to earth personality. I’ve been a developer for a while now and I definitely wing it on personal stuff. If I spend much time trying to plan I end up never starting. Better to try, see room for improvement, refactor and move along. That’s also the best way for me to remember things. Like you said, just dedicate the time to it.
I was f-ed up for so long by unrealistic personal deadlines that piled up, never actually getting done. Turns out it's a perfect way to ruin motivation (and will to live, frankly speaking). So yeah, the finesse advice is right on point, thank you for the video!
10:05 9:39 The part with schedule and consistency, but no deadlines. i like it. 👍
'Always leave yourself with something to do for the next day'
That pretty much sums up the whole video
I agree with your overall message for doing solo coding projects, as using industry-standard workflows and tools at all times is definitely overwhelming and a lot of extra unnecessary work (as you mentioned, for collaboration/communicating your work to others.. since you are the only one on the project)
That being said though, if you are serious about getting a job in the industry and are in a situation where you still don't have a foot in the door, I highly recommend against this, and instead recommend that you use all of these tools and workflows as getting used to it ahead of time will make you more desirable from a job-market point of view. Saying that you have experience from private projects making simple UI mockups and UML diagrams for your planned features, and also going through the motions of then making issues and storing that documentation within JIRA/Confluence (or another industry standard equivalent) before... this is a huge plus for hiring you over other inexperienced workers from a hiring manager's point of view. It shows you're dedicated and doing everything you can to build yourself up without yet getting an official opportunity to do so yet as well!
Anyhow, for those solo-projects you do on the side while working an industry-standard job, then I totally get ForrestKnight's suggestions and agree, but just keep ↑ in mind as well if that advice is applicable to you in your situation! :)
You inspired me sir. Thank you so much
RIP Dyrus
This is really awesome content. Love how you emphasize throughout the video that there's no rigid way on how to do things (as it should be). though I'm not really that interested in web development this was still really helpful
Software development is an art not science only, well said. I wish more people think in this way the organization can build a lot better products, in my opinion.
Conclusion: "How do I plan My Coding Projects? I do it in my head or write things down on my note book thats it." well this is what I do too.
Finesses, I really loved that word you used.
Really making your code and UI have some finesses. just like an Art project.
Thank you very much for this video! Exactly what I needed!
Just found this channel ! As a new starter within the industry, this channel has boosted my confidence alot ! Thanks Forrest :)
Thanks gilfoyle
well yup I did enjoy tab9....... it's actually good and i have an exam tomorrow but FK's(forrestknight's) video is actually more important...
It's videos like this is the reason why i am subscribed to this channel thank you for making programming so much easier and comforting Forrest. I have to ask an advice i am looking to get my first devops job in IT i have no experience the field but am finishing my bachelors in computer systems technology i have 3 certs in aws any tips for interviews, etc anything would be greatly appreciated thank you Forrest and keep up the great work :)
Loving the pace of these videos...learning a lot from you!
insanely helpful video, reminded me how how less I need to overthink and how more I should over do. Thank you!
My advice would be:
1. sometimes go broad and shallow (basically the MVP) to get a rough idea and get something running to enjoy.
2. Sometimes take a small part of it and go deep, deep down and make the details perfect to explore complexity and pitfalls of _difficult_ tasks, especially when you are new to a technology, language, framework.
2b: Hot tip: from time to time aim to intentionally try something new, a new algorithm, some new commands, some other way to do _even when you could do it the usual way_ . You will always learn something, and be it that the fancy shiny stuff was a dead end, but now you have experienced _why_ by yourself.
3. Sometimes develop and debug critical subsystems in a separate sandbox or simulator to get these straight without the weight and the dependencies of the whole project. That also helps to get interfaces right (testing...).
And yeah, I totally support the idea to be relaxed and switch between these subjects by gut feeling and day performance. Don't be the "The steak is perfectly grilled, now let's start peeling the potatoes" guy...
Homie is lefty ! That’s how you know he is a beast at Computer Science :D.
@@morceegao WTF. I am right handed and I don't feel like shit and statistically speaking there's more right handed programmers than left handed ones.
what
@@asandax6
Yes, that's because statistically, there are more right handed than left handed people, period
@@morceegao you sound like someone who will think up anything to be your own buzzkill. Good luck with that
Perfect!
Thanks a lot for giving us perfect advise for finding our way in coding life.❤
I think this is the best subject to make a tutorial on
i liked the last piece of advice of leaving yourself something to do a next day so that you have no hesitation starting again
My biggest takeaway: as a solo developer, consider approaching projects favoring the advantages of myself as an individual as opposed to a team of individual talents. Very helpful looking forward, thanks for the perspective!
You got my like when you said an mvp doesnt need all the stuff that causes barriers and gets in your way. Iv been saying this for years. Just because a tool exists, doesnt mean you need to use it.
one of the best videos i saw on the topic of programming. thanks a lot man
00:00 Planning coding projects can vary from professional to personal projects
01:26 Tab 9 is a good code completion tool
02:58 Discussion on creating a personal website using HTML, CSS, and JavaScript
04:22 Research and planning are crucial before starting development.
05:58 Create a simple MVP for Social Leader leaderboard
07:17 Start building your personal project without worrying about professional practices.
08:46 Start coding with boilerplate and figure things out as you go.
10:12 Treat coding like an art, not a science
Trying out the Tabnine Pro. Thanks for the discount!
Set flexible time slots for project work and always leave your self something to-do the next day.
😄
Starting a project now and this video popped up!
This is great advice, Forrest! 😊 Im a newbie coder here although I have a background in art and design, one thing i like to do especially when Im learning a new programming language, ill learn some basics first enough to get started on a project, but then some days ill take what Ive learnt and combine that with my love of making art. Ive been making visual art for most of my life and code to me can be another medium the same way that paint and brushes are. Its the act of removing the pressure of having to get to a specific outcome ALL of the time and allowing myself to have fun with and experiment with code, that furthers the learning process for me. Any other code artists out there? 😊
This came right on time haha. I agree with every word whole-heartedly! Appreciate your content and knowledge.
Blessings fam!
Wow I needed this
Thanks for sharing your word on this. I'm kinda revisiting some personal projects I pushed off because of missed deadlines.
my first time watching you and I subscribed, I love your video
Nice video. May I know what's the notebook that you use here? Looks very handy.
Tabnine sponsor is so cool! Great video
Great video. Was very good to hear how you go about your personal projects👍🏽
Thanks man) Will start my portfolio webpage. Tomorrow. I hope so :)
Did you start?
@@lameprotagonist4275 No, I got some more kinda important things to do ASAP... Some test tasks to try to become an intern... University exam, the last one... That isn't an excuse. I did not start yet
@@Mikro4elix Don't worry, sometimes life can get in the way. Good luck with your exam 💪🏾. You can do the webpage when all is done
Coding as an Art !! Absolutely
The only way you can create a flawless code is
by not coding at all.
No code = no bugs = efficiency 100%
one man can change the world
i've just discovered your channel, the content is really good man keep it up !
This video is fantastic and is on point.
I am a hobbyist python programmer and love the coding experience based on the views you have just mentioned.
The best part for me is to ensure I leave a piece of the meal for the next day, and so on.
There is always the eagerness for me to complete the project.
The only tool I use is the free Trello Board.
Thanks for the Video, and I will be watching out for more content.
Last second tip was 🔥
Always great content!!!
That last one was gold 🥇
I literally just paused the video to get the Tabnine extension. I might end up buying depending on how much I like it. This sounds like Kite without the creepy monitoring that Kite did. I might end up purchasing a license.
This guy is my inspiration 🙏
Fuck, best advice ever. For code and for life! thanks
Thanks for the headsup,,,I'm definitely gonna check it out bro
i feel extra chill after watching this vid
Thanks for the advice!
1 minute information stretched into 12 minutes video 👏🏻
Yep. Screw the industy.
Do what thou wilt.
I saw Jesus today
😂 came to mind soon as vid appeared
Me too
I saw a video in which he was giving advice on tech stuffs , a guy in comment said same thing "if Jesus himself telling me this then who I am to deny it "
Lmao, I literally started the comment section to see if this was a comment lol
Dude 😂😂.. not fair
Cool, thanks for making this video!
Amazing content sir, I love it
Thank you, great video😊
Thanks. Inspiring
wow perfect timing rec!!
I recently wrote my first "program" a month into a Python course. I started by opening an MS Excel document, performing some excel operations with code, and then saving the file. The mystery of coding has been solved. Do some useful stuff and save your work.
Ty for the improvement advices
nice.. as an old person, i remember when this was easy.. just do it
This was fairly helpful to me!
I work off of the principal “if I fuck up I can fix it”
A thousand thank you’s holy cow
nice clean monitor same as mine
The front-heavy explainer was a pain to even skip, but I know why you do it
I have been creating many apps in my whole programming journey and I really enjoyed the ladder experience, I don't have anxiety of thinking if can do it or not I just enjoy the road, but now I feel I need to learn how to plan things before hopping to my text editor hahaha and it's gives me anxiety haha I hope I overcome it .
Helpline📲📥⬆️
Questions can come in⬆️