Why Most Workshops suck?

Prateek Jain — Sun, 27 Oct 2019 19:08:10 +0000

So it's 1:40 at night, and I cannot sleep (as usual). But how about writing about my thoughts this time? Due to some
recent discussions with some people, this is the topic which I had in mind for a few days.

First I would like to highlight the word most here.

First, let's go back a year. We all heard the news that a three-month Internship would be compulsory for our batch
in order to complete our B.Tech. program. First thing that popped into my head:

Great !!! Now companies will start selling Trainings in the name of Internship.

And it wasn't much later that I saw all this coming true. Though it was not just the companies, it included some very
prestigious Universities as well. Well, no issue, maybe they will teach the students the right way and do justice to the
large amounts students are paying.

Why I think that it won't ever be true:

Leaving the case of Companies/Universities doing this just for money (no solution to that except that the students
should make smart decisions themselves), let me explain why workshops are no good even when the company/university
themselves want good for the students.

As we know, there is no screening process in such workshops/training. So, a curious student who wants to learn, and a
student with no interest in the topic are both in the same class, being taught from the same teacher. And we all know
that the amount of later type of students is much much more than the former.

The workshop organizers want you to learn, but they won't ever teach things which more than half the class cannot
understand. They would want to meet the level of everyone present in the class. All they do is give those students the
Hoax of knowledge (instead of telling them how much more there is to explore in that field)
leading to ignorance, which is enough to stop their learning process. What a waste of time for the student who was actually there to learn.

All Workshop organizers care about are positive reviews. They want more participation next time. Their goal is to leave
you with you feeling smart. So basically, workshops/training programs quality sucks, almost always.

Students attending such workshops should also know:

Some skills are too complex for short-term intensive training to be effective.

And coding is definitely one of those skills.

Workshops are a fad and a waste of time and money.

So all workshops/training programs suck?

I think mostly which are paid. Maybe I think so because I have used free resources to learn from the time I started
coding and things are much more clear and innocent when money is not the reason for transfer of knowledge, curiosity is.

But where to learn from then?

MOOCs MOOCs MOOCs !!!!!!!!!!

MOOCs are free, taught by world experts (not kidding). Some of the best teachers in the world are out there, writing
books, blogs, making MOOCs, for you, why would you opt for a training program dude?

Make your own portfolio using Jekyll and Github Developer Pack

Prateek Jain — Sat, 27 Jul 2019 03:01:39 +0000

In this blog we will be creating a portfolio using Github developer pack and Jekyll.
So, let's first talk about what is Github developer pack and what is jekyll.

NOTE: Where ever curly brackets {} are used, it has a variable inside it with actual value corresponding to the name of the variable.

What is Github developer pack?

It is a program under Github Education in which Github provides free tools and services to students.
To apply to Github Developer Pack, all you have to do is submit a proof that you are a student at the time
of applying to the program. And answer a small question: "How you are planning to use Github?". After filling the details, you will receive
a mail within five days when your application is approved.

Some important things which you get in Github Developer Pack:

Free credits in AWS Educate
A free license for Bootstrap Studio
$50 in platform credit in DigitalOcean for new users (In case you ever plan to learn SSH or sys-admin)
Unlimited Private Repositories on Github
A free subscription to all Jetbrains IDEs (I survive because of this.)
$100 credits free with Microsoft Azure
A free .me domain name with SSL certificate
Travis CI for private builds

and the list goes on. Now let's talk about Jekyll.

What is Jekyll?

Jekyll is a simple, blog aware, static site generator for personal, project, or organization sites.
In simple words, you won't require writing HTML, CSS or JS to build your static website, just simple Markdown. All you need to do is follow some basic instructions given in the docs.
But don't start just yet, we will be going through everything step by step. I will try to keep this blog self sufficient.

Now let's make a list of steps involved in making the portfolio, and after that go through those steps one by one.

Steps involved in making the website:

Choose a theme
Fork the theme, then clone it and run it locally
Make it personal and host it
Get a .me domain
Add CNAME
Further improvements

1. Choose a theme:

For those who are choosy, this is going to be the longest step. I myself took days searching for themes before finally settling on this one.
Here is the list of free themes by Jekyll. You can also find some extra on Github.
And some more here. These are all the resources I scrapped. All the best. May you find your theme.

2. Clone the theme and run it locally

After choosing a theme, fork it on Github, and then clone it so that the remote origin points to the directory on your Github Profile.
Most repositories of jekyll themes include the documentation for running the jekyll theme locally. If they don't, here are some steps you can follow:
cd into your blog directory and run the following commands:

foo@bar:~$  gem install jekyll bundler
foo@bar:~$  gem install github-pages
foo@bar:~$  bundle install
foo@bar:~$  bundle exec jekyll serve

Now in your browser go to: http://localhost:4000 and bam!!! Here's what your website will look like.

3. Make it personal and host it

Now, go to the _config.yml and fill the fields accordingly. Don't forget to edit the field named baseurl to "". It is used in
delivering your css and images. I faced an error where my hosted website didn't load it's css and images while everything was working
fine locally. It turns out baseurl was the culprit.

Now, push these changes using:

foo@bar:~$  git push origin master

Now go to the settings tab of your Repo and rename your Github Jekyll theme Repo to {your_username}.github.io and you will see that github will host
your website to the Url {your_username}.github.io.

4. Get a `.me` domain

Go to Github Developer Pack page, and from there, open Namecheap, and activate your Namecheap account using Github, and select a .me domain
of your choice. After selecting a Domain, purchase it for free (Thanks to Github Developer Pack).

5. Add CNAME

On your Domain Dashboard on Namecheap, then go to Advanced DNS
and add a CNAME record. Something like this:

In Target, replace prateekj117.github.io with {your_username}.github.io.
After that, in the root directory of your theme project, make a file named CNAME and enter the value {your_domain_name}.me in it.
Commit the change and again push the commit using:

foo@bar:~$  git push origin master

After that, you website is hosted on {your_domain_name}.me. Congratulations !!!

6. Further improvements

After all the above steps are done, now you can add an additional functionality of comments if not already integrated in your theme using Disqus.
And a subscribe button functionality as below which will send updates to the emails subscribed to your blogs using Mailchimp.
For the Mailchimp functionality, you will need to add a RSS feed to your blogs which you can add using jekyll-feed.
You should also add gem 'jekyll-compose', group: [:jekyll_plugins] to your Gemfile and run:

foo@bar:~$  bundle install

The use of jekyll-compose is that you can directly add a blog post using command:

foo@bar:~$  bundle exec jekyll post "My New Post"

As an example, you can also see the code of this website here.

For now, that's all. Do comment if you get any error or get stuck somewhere. Subscribe to the blogs. I will be posting a guide to
How to contribute to Open Source next.

DEV Community: Prateek Jain

Why Most Workshops suck?

Why I think that it won't ever be true:

So all workshops/training programs suck?

But where to learn from then?

Make your own portfolio using Jekyll and Github Developer Pack

What is Github developer pack?

Some important things which you get in Github Developer Pack:

What is Jekyll?

1. Choose a theme:

2. Clone the theme and run it locally

3. Make it personal and host it

4. Get a `.me` domain

5. Add CNAME

6. Further improvements

Happy Coding !!!

DEV Community: Prateek Jain

Why Most Workshops suck?

Why I think that it won't ever be true:

So all workshops/training programs suck?

But where to learn from then?

Make your own portfolio using Jekyll and Github Developer Pack

What is Github developer pack?

Some important things which you get in Github Developer Pack:

What is Jekyll?

1. Choose a theme:

2. Clone the theme and run it locally

3. Make it personal and host it

4. Get a .me domain

5. Add CNAME

6. Further improvements

Happy Coding !!!

4. Get a `.me` domain