Rohit Kalyania

Rohit Kalyania


YouTube Coding Bootcamp 2021!

Just bring your laptop!

Hello everyone and welcome to this online Coding Bootcamp. This Bootcamp has been designed specifically to make your coding journey easier by utilising all of @YouTube functionalities such as the Timestamps and Cards.

We will be using the Timestamps to break up our Bootcamp into sections, so that you can easily navigate to and from each one using the description below. I will also be using Cards in order to direct you to an external project you can try, based on where we are in our Coding Journey.

I have also provided Code Sandboxes at the bottom for those stuck on code setup for the learning sections. I would advise to always type out the code to each exercise yourself, but as a safety net, they are provided as well.

This 12hr+ Bootcamp is unsponsored and free and will always be free, so if you enjoy it please do give a big thumbs up and Subscribe!


  • 00:00 Introduction
  • 03:34 Code Editors
    – HTML –
  • 06:05 HTML Introduction
  • 08:22 HTML Boilerplate setup
  • 10:55 HTML Elements
  • 17:53 Online Portfolio Project
    – CSS –
  • 20:05 Check-in
  • 21:02 CSS Introduction
  • 23:37 File set up
  • 27:42 Class names and Id’s
  • 30:48 Pop Quiz
  • 37:52 Box Model
  • 39:56 Colours
  • 44:12 Unordered and Ordered Lists
  • 49:33 Images
  • 54:22 Styling classes as id’s
  • 57:07 The Data property
  • 59:00 Flexbox
  • 01:01:45 Pop Quiz
  • 01:03:41 Flexbox website layout
  • 01:09:43 Commenting out Code
  • 01:13:37 Gradients in CSS
  • 01:15:53 Box Shadows in CSS
  • 01:17:18 Button Styling in CSS
  • 01:25:51 Fonts
  • 01:29:25 Generic Website Layout
  • 01:34:28 making a NavBar
  • 01:46:54 Anchor Links
  • 01:50:17 Creating Sections
  • 02:13:50 Forms in CSS and HTML
  • 02:26:55 Font Awesome
  • 02:32:12 Break points
  • 02:38:35 Z-index
  • 02:49:24 Check-in
  • 02:51:07 Introduction to JavaScript
  • 02:52:12 JavaScript file setup
  • 02:58:39 Variables
  • 03:16:15 Control Flow
  • 03:16:40 If Statements
  • 03:26:09 Operators
  • 03:55:39 Fizz Buzz Exercise
  • 04:00:59 for loops
  • 04:07:58 Arrays
  • 04:14:42 Objects
  • 04:24:50 Functions
  • 04:37:51 A Progress Exercise
  • 04:48:20 Arrow Functions
  • 04:52:21 While loop
  • 04:55:23 Built-in-Objects Introduction
  • 04:56:02 .length()
  • 05:01:29 .concat()
  • 05:06:41 .join()
  • 05:12:06 .pop()
  • 05:18:46 .shift()
  • 05:22:13 .unshift()
  • 05:25:32 .push()
  • 05:29:02 .slice()
  • 05:35:51 .splice()
  • 05:41:47 .forEach()
  • 05:50:25 .some()
  • 05:59:49 .map()
  • 06:07:19 .filter()
  • 06:17:06 .reduce()
  • 06:22:27 .every()
  • 06:28:25 .split()
  • 06:34:25 Array work - Exercises to practise
  • 07:18:06 .addEventListener()
  • 07:26:09 .removeEventListener()
  • 07:33:57 querySelector()
  • 07:39:59 Check-in and Project suggestion
  • 07:40:51 Math.random()
  • 07:53:08 Let’s make a Responsive Burger NavBar
  • 08:10:12 Date
  • 08:19:29 setTimeout()
  • 08:29:00 setInterval()
  • 08:44:11 Classes in JavaScript
  • 08:52:16 Check-in and Project suggestion
  • 08:52:58 Keys
  • 09:01:46 switch case
  • 09:22:51 .sort()
  • 09:24:52 Introduction to Algorithms
  • 09:25:16 .includes()
  • 09:27:34 .contains()
  • 09:29:52 .createElement()
  • 09:38:22 Check-in and Project Introduction
  • 10:27:07 Check-in and Project suggestions
  • 10:28:16 Introduction to HTTP
  • 10:36:55 fetch(). GET POST PUT DELETE
  • 11:07:24 Check-in and video suggestion
  • 11:07:53 Storing Projects on GitHub
  • 11:15:58 Where to go next

Code Sandboxes:

Generic Sandbox Setup: Use your coding skills to change the HTML and CSS to whatever you need for the exercise using this as a template:

Memory Game final code:

#html #css #javascript #web-development #developer

What is GEEK

Buddha Community

YouTube Coding Bootcamp 2021!
Tyrique  Littel

Tyrique Littel


Static Code Analysis: What It Is? How to Use It?

Static code analysis refers to the technique of approximating the runtime behavior of a program. In other words, it is the process of predicting the output of a program without actually executing it.

Lately, however, the term “Static Code Analysis” is more commonly used to refer to one of the applications of this technique rather than the technique itself — program comprehension — understanding the program and detecting issues in it (anything from syntax errors to type mismatches, performance hogs likely bugs, security loopholes, etc.). This is the usage we’d be referring to throughout this post.

“The refinement of techniques for the prompt discovery of error serves as well as any other as a hallmark of what we mean by science.”

  • J. Robert Oppenheimer


We cover a lot of ground in this post. The aim is to build an understanding of static code analysis and to equip you with the basic theory, and the right tools so that you can write analyzers on your own.

We start our journey with laying down the essential parts of the pipeline which a compiler follows to understand what a piece of code does. We learn where to tap points in this pipeline to plug in our analyzers and extract meaningful information. In the latter half, we get our feet wet, and write four such static analyzers, completely from scratch, in Python.

Note that although the ideas here are discussed in light of Python, static code analyzers across all programming languages are carved out along similar lines. We chose Python because of the availability of an easy to use ast module, and wide adoption of the language itself.

How does it all work?

Before a computer can finally “understand” and execute a piece of code, it goes through a series of complicated transformations:

static analysis workflow

As you can see in the diagram (go ahead, zoom it!), the static analyzers feed on the output of these stages. To be able to better understand the static analysis techniques, let’s look at each of these steps in some more detail:


The first thing that a compiler does when trying to understand a piece of code is to break it down into smaller chunks, also known as tokens. Tokens are akin to what words are in a language.

A token might consist of either a single character, like (, or literals (like integers, strings, e.g., 7Bob, etc.), or reserved keywords of that language (e.g, def in Python). Characters which do not contribute towards the semantics of a program, like trailing whitespace, comments, etc. are often discarded by the scanner.

Python provides the tokenize module in its standard library to let you play around with tokens:



import io


import tokenize



code = b"color = input('Enter your favourite color: ')"



for token in tokenize.tokenize(io.BytesIO(code).readline):





TokenInfo(type=62 (ENCODING),  string='utf-8')


TokenInfo(type=1  (NAME),      string='color')


TokenInfo(type=54 (OP),        string='=')


TokenInfo(type=1  (NAME),      string='input')


TokenInfo(type=54 (OP),        string='(')


TokenInfo(type=3  (STRING),    string="'Enter your favourite color: '")


TokenInfo(type=54 (OP),        string=')')


TokenInfo(type=4  (NEWLINE),   string='')


TokenInfo(type=0  (ENDMARKER), string='')

(Note that for the sake of readability, I’ve omitted a few columns from the result above — metadata like starting index, ending index, a copy of the line on which a token occurs, etc.)

#code quality #code review #static analysis #static code analysis #code analysis #static analysis tools #code review tips #static code analyzer #static code analysis tool #static analyzer

Brain  Crist

Brain Crist


YouTube Live Coding Channel Contents [Chilling & Coding]

This blog post will have the all the resources about the YouTube stream I do.

Youtube Link** – How to become a web devleoper 2020? – **PDF Drive Link

Youtube Link** – How to become a web devleoper 2020? – **PDF Drive Link

Do you want to join a discord server where we talk about programming all day? If yes

Link to join discord server

I’ve some free pdf’s for you

-> Javascript in 30 days

-> Node js 30 days

If you want to learn more from me, I can give one to one mentorship.

#programming #chilling and coding #coding and chilling #coding stream #live coding #youtube channel

Samanta  Moore

Samanta Moore


Guidelines for Java Code Reviews

Get a jump-start on your next code review session with this list.

Having another pair of eyes scan your code is always useful and helps you spot mistakes before you break production. You need not be an expert to review someone’s code. Some experience with the programming language and a review checklist should help you get started. We’ve put together a list of things you should keep in mind when you’re reviewing Java code. Read on!

1. Follow Java Code Conventions

2. Replace Imperative Code With Lambdas and Streams

3. Beware of the NullPointerException

4. Directly Assigning References From Client Code to a Field

5. Handle Exceptions With Care

#java #code quality #java tutorial #code analysis #code reviews #code review tips #code analysis tools #java tutorial for beginners #java code review

Houston  Sipes

Houston Sipes


How to Find the Stinky Parts of Your Code (Part II)

There are more code smells. Let’s keep changing the aromas. We see several symptoms and situations that make us doubt the quality of our development. Let’s look at some possible solutions.

Most of these smells are just hints of something that might be wrong. They are not rigid rules.

This is part II. Part I can be found here.

Code Smell 06 - Too Clever Programmer

The code is difficult to read, there are tricky with names without semantics. Sometimes using language’s accidental complexity.

_Image Source: NeONBRAND on _Unsplash


  • Readability
  • Maintainability
  • Code Quality
  • Premature Optimization


  1. Refactor the code
  2. Use better names


  • Optimized loops


  • Optimized code for low-level operations.

Sample Code


function primeFactors(n){
	  var f = [],  i = 0, d = 2;  

	  for (i = 0; n >= 2; ) {
	     if(n % d == 0){
	       n /= d;
	  return f;


function primeFactors(numberToFactor){
	  var factors = [], 
	      divisor = 2,
	      remainder = numberToFactor;

	    if(remainder % divisor === 0){
	       remainder = remainder/ divisor;
	  return factors;


Automatic detection is possible in some languages. Watch some warnings related to complexity, bad names, post increment variables, etc.

#pixel-face #code-smells #clean-code #stinky-code-parts #refactor-legacy-code #refactoring #stinky-code #common-code-smells

Fannie  Zemlak

Fannie Zemlak


Softagram - Making Code Reviews Humane

The story of Softagram is a long one and has many twists. Everything started in a small company long time ago, from the area of static analysis tools development. After many phases, Softagram is focusing on helping developers to get visual feedback on the code change: how is the software design evolving in the pull request under review.

Benefits of code change visualization and dependency checks

While it is trivial to write 20 KLOC apps without help of tooling, usually things start getting complicated when the system grows over 100 KLOC.

The risk of god class anti-pattern, and the risk of mixing up with the responsibilities are increasing exponentially while the software grows larger.

To help with that, software evolution can be tracked safely with explicit dependency change reports provided automatically to each pull request. Blocking bad PR becomes easy, and having visual reports also has a democratizing effect on code review.

Example visualization

Basic building blocks of Softagram

  • Architectural analysis of the code, identifying how delta is impacting to the code base. Language specific analyzers are able to extract the essential internal/external dependency structures from each of the mainstream programming languages.

  • Checking for rule violations or anomalies in the delta, e.g. finding out cyclical dependencies. Graph theory comes to big help when finding out unwanted or weird dependencies.

  • Building visualization for humans. Complex structures such as software is not easy to represent without help of graph visualization. Here comes the vital role of change graph visualization technology developed within the last few years.

#automated-code-review #code-review-automation #code-reviews #devsecops #software-development #code-review #coding #good-company