Conference Youtube videos. They are a goldmine of useful tips and tricks. Go look for videos from the Node [1] and MongoDB
[2] conferences and you will find tons of war stories and what is actually working for people. Using this option arguably connects you directly with some of the best people in the world who are actually using this stuff.
ps. using the youtube 2x playback speed option can really help digest lots of video content quickly [3]. I use this almost exclusively on youtube now.
1) Sometimes it can be hard to find good YT vids, especially a series of vids that will deep dive into the topic you care about. Maybe sign up for an online course where there videos of the instructor coding in real-time and address things in detail.
That will definitely give you a place to start with someone who has actually professionally done things you’re doing according to some best practice.
2) After you’ve got an idea of what you think is best practice, even if you have lots of questions remaining, just keep moving ahead with your project with a focus on making sure your API successfully does what you plan for it to do.
it’s not possible for you to know all the best practices, especially in isolation, and still be productive. you have to get your work done, and some of it is just going to be terrible. It’s possible that you may end up with a lot of tech debt that requires time to go back over it to refactor, but what does your boss expect if you’re alone and making the whole thing by yourself?
Unfortunately, you have to meet your timelines, so compromises must inevitably be made. More could be said about this, but i’ll leave it there.
Also, overtime, you will start to see what the better way to implement things are, as you continue building out features and run into use-cases you might not have thought of previously. The videos and documentation you read later on will make more sense since you have a framework in your mind of how the patterns get used or implemented in code.
I would say do not look to conference videos for how to write production quality code... Most talks at conferences are shallow and at worst just the blind leading the blind.
Be very careful, I've even seen people from places like Microsoft showing code at conferences that would fail even a decent code review process.
I think for this reason conferences are a complete waste of time. Talks are too short to go into anything approaching useful detail, and s spend an hour talking about pointless demo quality code.. Or the talkers arent experts in what they are talking about. Waste of time.
I would say the same for the majority of blogs. Most are garbage and it can be difficult to tell the code is garbage if you're a beginner. I dont know a single development blog worth reading...
The blind leading the blind? Most conferences have lineups of well respected people involved in an ecosystem. From language authors to open source maintainers and such.
It seems you don't seem to understand the purpose of conferences and blogs. These talks are not to showcase the best quality production code that can pass any review process. They are to showcase new developments and new approaches to do things in a specific field. It's meant for people already in the field (or starting to get into it) trying to learn more.
If such talks have high quality production code in slides the message would get easily buried under stuff that isn't important for conveying the message they are trying to say.
This often happens when conferences and blogs are used as a marketing outlet. There is still plenty of gold, but you have to sift through all the garbage of people using it as a way to make themselves more visible.
It depends on which conference you are looking at, if Brian Goetz had a talk on concurrency best practices then it would definitely be something to think about.
It's true. The best way to learn is to do. Second best, look at production quality source code. Third best, buy a book written by an actual authority on the topic.
https://www.infoq.com/ is my favorite because they get talks from some of the most experienced software dev folks, and they cover almost every topic of software engineering
I'm glad to hear I'm not the only one who watches YouTube presentations on 1.5-2x speed. I mentioned that at work once and people looked at me like I was crazy.
A fantastic app. It saves your preferences across all embedded video formats too (bar a very select few - looking at you Crunchy Roll) which means which means you don't need to reset your speed to 2x every time you delete your cookies/cache, or visit a new website!
I watch all my videos at 2x speed now and I was shocked how much time I saved. It no longer takes me most of the night to work through my YouTube notifications, and has left me so much more time for project work during the week.
Because there are other options like switching off one tab when you start video in another tab, overlay if you scroll down, default quality (I have to be on 144p because of bandwidth constraints)
You can use console in browser to control playback rate:
1. select video element with: $('video')
2. than set playbackRate property on it
example write in console: $('video').playbackRate = 3; (and playback rate would be 3x) Works with rates between 0.0625 - 16.0(tested in Chrome and FF).
Two things:
1) Sometimes it can be hard to find good YT vids, especially a series of vids that will deep dive into the topic you care about. Maybe sign up for an online course where there videos of the instructor coding in real-time and address things in detail.
That will definitely give you a place to start with someone who has actually professionally done things you’re doing according to some best practice.
2) After you’ve got an idea of what you think is best practice, even if you have lots of questions remaining, just keep moving ahead with your project with a focus on making sure your API successfully does what you plan for it to do.
it’s not possible for you to know all the best practices, especially in isolation, and still be productive. you have to get your work done, and some of it is just going to be terrible. It’s possible that you may end up with a lot of tech debt that requires time to go back over it to refactor, but what does your boss expect if you’re alone and making the whole thing by yourself?
Unfortunately, you have to meet your timelines, so compromises must inevitably be made. More could be said about this, but i’ll leave it there.
Also, overtime, you will start to see what the better way to implement things are, as you continue building out features and run into use-cases you might not have thought of previously. The videos and documentation you read later on will make more sense since you have a framework in your mind of how the patterns get used or implemented in code.