r/javascript • u/RedlightsOfCA • May 09 '20
I've created an educational page to teach students the structure of a URL
r/javascript • u/RedlightsOfCA • May 09 '20
r/javascript • u/Acrobatic-Pen-9949 • Nov 09 '21
r/javascript • u/bornforcode • Apr 01 '18
r/javascript • u/backFromTheBed • Apr 14 '19
r/javascript • u/theadammorganshow • Sep 03 '16
r/javascript • u/kenman • May 31 '18
In the context of the continued decline of medium.com as a publishing platform: if your blog on Medium utilizes the 'membership' program, it will not be allowed here.
Per our guidelines:
Posts must be inclusive to all -- e.g. no beta invites, "PM me for access", "free for first N users", etc.
We've already added one author to the spam list, and we ask that you report any further Medium posts that also fall into this category.
r/javascript • u/umaar • Dec 22 '15
r/javascript • u/kunalag129 • Feb 13 '19
r/javascript • u/vivirenremoto • May 22 '21
r/javascript • u/saadq_ • Feb 17 '18
r/javascript • u/[deleted] • May 26 '18
r/javascript • u/leonardomso • Dec 14 '18
Top Projects in 2018
https://blog.github.com/2018-12-13-new-open-source-projects/
I'm writing this just to thank all of you who helped with this project, I'd like to thanks all of the 44 contributors that have contributed to the project, and for all of those who have made some constructive feedback! Thanks y'all!
I'm really proud of this project and really glad of the huge feedback that I've been receiving for the last months.
If you don't know the project yet, I'd really recommend it for all of those who want to learn more about JavaScript. If you want to contribute to the project, or just give a feedback, please feel free to do:
33 concepts every JavaScript developer should know
https://github.com/leonardomso/33-js-concepts
r/javascript • u/[deleted] • Dec 28 '17
r/javascript • u/brimhaven • Sep 22 '17
r/javascript • u/zoltanszogyenyi95 • Jun 17 '20
r/javascript • u/magenta_placenta • May 20 '19
r/javascript • u/adilanchian • May 29 '18
Hi everyone!
I want to preface this post by stating that I am in no way trying to self promote something I have made. While I think it would be awesome for people here to check it out and use it, I wanted to post about my experience with creating an application in 28 days and hopefully motivate someone else to do the same.
As the title states, I streamed the entirety of my work for this project on Twitch. I have always been enthralled with the concept of Twitch and I really thought it could be an incredible place for programmers to showcase their work. This led me to start a stream that would encourage people to get involved with programming. I have almost three years of experience working with web development, mobile development, and I am mainly self taught. I still have much to learn and I believe the best way of doing that is through projects. This is where the format for my stream comes- start a project from start to launch in 28 days. This is how SimpleAlerts was born. SimpleAlerts is an open source project that is here to solve the problem of unreadable, disorganized stream events through Streamlabs. For much more detail on this feel free to head over to this repo as it has much more information about the project.
As someone who started off his programming career truly through internships and hackathons, I know how intimidating it is to begin your programming journey. This is why I think this style of project is a great way get a deep dive into something that you have been really wanting to try. I wanted to list the benefits I got from this no matter what level programmer you may be:
This is something I have been really wanting to get into as I have always struggled with it. The way you tackle massive projects/problems all comes down to the initial setup. Take as much time as you need in order to really understand how you will be doing each step of the application. It will save you tons of time in the long run.
I am a huge advocate of Github Issues (as you will see if you check out the repo). It is much easier for me to digest tasks if they are written out in bite sized concepts. I feel this is a practice many people lack. They feel as if they need to tackle huge problems at once. You donโt! Your code will be there tomorrow, I promise :)
It is much easier to do things when you have a drive to do it! I chose Angular 5 / Node / MongoDB as my stack as I wanted to get a better grasp on TypeScript, Promises, and interacting with the MongoDB, Node driver. After finishing SimpleAlerts I feel really good about JavaScript in general and really can't wait to write more promises ;).
This take away I think is really important. Many projects that are started are never finished. This could be the shear amount of features that you may want to implement or youโve simply lost your drive. I had two main motivating factors when building this project. First was the 28 day timeframe and second was the fact that I set a stream schedule 5 days a week for 2-3 hours a day. This kept me engaged with SimpleAlerts.
You are going to mess up and do things wrong. That's okay! As you start building more projects things will start to click. This could even lead you to refactor older projects with this new insight!
Itโs okay that your application doesnโt pop off-most donโt. Just take a look back at all the time you spent and how much you learned from building out an app from start to launch. These projects are always beneficial even if you donโt make millions of dollars ;)
I wanted to wrap up this post by saying that the programming community is a great one to be a part of. All the people I have interacted with during this project have been more than great. Everyone is willing to help each other out and want to see everyone succeed. If you are afraid to start something like this or even start programming, just remember people are here to support you. One of the reasons why I decided to make SimpleAlerts open source was to encourage beginners to come and add to the codebase. Consider contributing on Github @ this repo if you are interested!
Thanks for taking the time to read this and if you have any questions/concerns please feel free to reach out :)
-Alec
r/javascript • u/magenta_placenta • Jul 17 '20
r/javascript • u/b_n • Nov 03 '15
I've been interviewing for JS positions over the past few months and have noticed the same questions pop up in the technical parts of the interview. There have been similar posts to this but I really received a benefit from them and thought I'd echo my experience. Two of these "interviews" were online assessments, two were in person, and two were over Skype. The positions I've applied for are mainly at start ups and not for any specified Jr / Mid / Sr level.
I know that a lot of people disagree with this type of interview, like them or not, in my experience they've been a reality. When you're self-taught and haven't had your first job, I guess you have to prove yourself somehow. An assessment of Github / portfolio links would be a more ideal measure of progress but doesn't seem to count for everything.
Algorithmic*
Define a function that returns n lines of Pascalโs Triangle. (this question was the entire interview)
Define a function that takes an array of strings, and returns the most commonly occurring string that array (this question came with an execution time limit)
Use recursion to log a fibonacci sequence of n length.
Definitional
4. Explain the use cases for, and differences between โ bind, apply and call. 5. Explain event delegation and why it is useful. 6. What is the event loop? 7. How does hoisting work in JavaScript?
*Discussion*7. Walk us through the process of creation of an application or website you've built. 8. Which new JavaScript / browser features are you most excited about and why? 9. What are the differences between functional and imperative programming styles, and explain your preference, if any.
r/javascript • u/moklick • Mar 07 '20