If you think the same, then this thread is for you!

Before we jump into any conclusion let's dive straight into some survey reports came in 2022.

StackOverflow Most Popular Programming Language 2022:

- Java is @ 6th Position.

StackOverflow Most Used Framework & Libraries 2022:

- Spring (Java Framework) is @ 4th Position.

Github Survey Top Languages in 2022:

- Java is @ 3rd Position.

Google Trends for Last One Year:

- Java is @ 2nd Position.

- If we see carefully, then Java is almost in the top 5 spot.

- Yes, Java has a learning curve.

- Yes, Java is a strict language and bit verbose too.

- You hate it or love it but you can't ignore its capability.

- Running on billions of devices, being used extensively by top tier companies, platform independent, robustness, security are some of the positives of Java.

- List of Top Companies Using Java by @Career_Karma
(Source: https: //careerkarma. com/blog/who-uses-java/)


So, should you start/continue learning Java?

- Yes, 100%.

- It has a great tech community out there & plenty of support available.

- I'm sure after learning Java, other languages will be a cake walk.

How To get started with Java Fullstack journey?

- Read below roadmap which I've personally followed to lead a successful career:

https://twitter.com/vikasrajputin/status/1539413363989487616

Are you not sure about which resources to follow?

- Read below thread where I've shared free youtube videos which personally helped me in my Java Journey:

https://twitter.com/vikasrajputin/status/1543768560152895488

Conclusion:

- My agenda here is not to start a new language war, all programming languages are great so as Java.

- Treat them as a tool to solve a specific problem.

- Yes, Java's popularity has seen a bit dip in last 1-2 years but that doesn't mean its dying.

Hope you've got some clarity about Java's future.

Every Mon, Wed & Fri - I write a thread
on Fullstack Development.

Like and retweet the first tweet as it will encourage me to put on more Java-related helpful content.

Follow @vikasrajputin to read all my future threads.

Is Java Dead ?

3 SQL Games to Level up your SQL Knowledge...

🧵👇

1. SQL Island

- Theme:
You're lost on an island and you need to use your SQL knowledge to survive.

🔗https:// sql-island. informatik. uni-kl. de/

2. SQL Murder Mystery

- Theme:
A Murder has happened in the SQL city, you need to use your SQL knowledge to find the killer.


🔗https:// mystery. knightlab. com/

3. SQL Police Department

- Theme:
Use hints to solve cases in the Police Department.

🔗https:// sqlpd. com/

That's it for now!

If you liked this then you might also like this:
https://twitter.com/vikasrajputin/status/1542681144910422018?t=-ACe2d1InXM9wlV-kEJvpg&s=19

Namaste, I'm Vikas!

Every Mon, Wed & Fri - I write a thread
on Fullstack Development.

Follow @vikasrajputin to read all my future threads.

3 SQL Games to Level up your SQL Knowledge

SQL: Beginner Guide to Store Procedures

a thread...

(Part 1/2)

1. What is Store Procedure?

It's a group of SQL statements stored on the DB side, to perform some action (business logic) or perform any DB-related task.

SP may or may not return output and may or may not take arguments, they are optional.

2. How to Define It?

Below, we've created a store procedure with the name "GetEmp" which is simply querying an EMPLOYEE_TABLE and fetching all employees.

Between BEGIN and END, we've got the body where we write all SQL statements & business logic.

(snippets are for MySQL)

Eg:

3. How to Call it?

In order to call the above procedure, we use the "CALL" keyword.

(snippets are for MySQL)

Eg: The below snippet will call the above-created SP.

4. Types of Parameters in SP:

IN: Using it, caller can pass param.

OUT: Output sent by SP to caller.

INOUT: The caller can pass the value inside SP, and SP can modify it and give it back to the caller with an updated value.

(in part 2, we'll cover this in detail)

5. Benefits of SP?

- Gives good performance, as it's precompiled in nature.

- Gets updated instantly without any deployment/server restart very useful when fixing production issues without any downtime.

- Reusability, as it can be used by multiple users/clients and also it accepts parameters so the same code can be used for multiple purposes.

- Reduces network traffic, as several SQL operations can be performed with a single step and save network round trips.

6. Drawbacks of SP:

- Errors are detected at runtime.
- Difficult to debug an SP.
- Difficult to maintain especially if it carries business logic.

That's it for now!

In part 2, we will see how to create store procedures with different types of parameters.

If you liked this then you might also like my other thread on SQL:
https://twitter.com/vikasrajputin/status/1535072762288410624

I hope you learned something new!

Every Mon, Wed & Fri - I write a thread
on Fullstack Development.

Follow @vikasrajputin to read all my future threads.

SQL: Beginner Guide to Store Procedures (Part 1/2)

Free 350+ Handpicked Videos for Java Web Development

Save 100+ hours of research

a thread...

If you love videos then this is all you need to refer to become full fledged Java Web Developer.

No need to refer any other resources.

Most of this videos, personally helped me in my Java Web Development journey

Let's get started...

1. Core Java in-depth Learning

- Durga sir OCJP playlist (199 Videos) [Personally Used] https://www.youtube.com/watch?v=eTXd89t8ngI&list=PLd3UqWTnYXOnjGmyjD3zbIkyLXP15-6w0

- Core Java Interview Series (23 Videos) [Personally Used]
https://www.youtube.com/watch?v=Dxpdo9BUGss&list=PLYPjPMiw3_YsVockWfuuhoP86YPDUXp4f

1.1  In-depth Core Java Tip:

A few videos are too lengthy in Durga sir's playlist mentioned above.

Refer to my Core Java Roadmap, pick a topic and directly jump on those videos, to speed up your learning.

https://twitter.com/vikasrajputin/status/1541240150877159425

2. Core Java - Crash Course:

- Core Java in 2hrs by ApnaCollege
https://www.youtube.com/watch?v=UmnCZ7-9yDY

- Core Java in 1.5hrs by Anuj Bhaiya
https://www.youtube.com/watch?v=aQatrXw0njs

- Core Java in 7hrs by Telusko [Personally Used]
https://www.youtube.com/watch?v=8cm1x4bC610

3. JSP-Servlet

- JSP - Servlet Basics by JavaBrains (25 Videos) [Personally Used]
https://www.youtube.com/watch?v=b42CJ0r-1to&list=PLE0F6C1917A427E96

4. Spring

- Core Spring by JavaBrains (24 Videos) [Personally Used]
https://www.youtube.com/watch?v=GB8k2-Egfv0&list=PLC97BDEFDCDD169D7

- Spring REST & Spring DATA by Bharath Thipireddy (15 Videos)
https://www.youtube.com/watch?v=GwYUjzPrQTM&list=PLSg8jHkYTg9EZSG9x5Roe0A_ixnjCYiWN 

- Spring Security Basics by JavaBrains (15 Videos) [Personally Used]
https://www.youtube.com/watch?v=sm-8qfMWEV8&list=PLqq-6Pq4lTTYTEooakHchTGglSvkZAjnE

5. JPA/Hibernate

- Core Hibernate by JavaBrains (36 Videos) [Personally Used]
https://www.youtube.com/watch?v=Yv2xctJxE-w&list=PL4AFF701184976B25

- Hibernate/JPA Basics by Ranga aka in28minutes 
https://www.youtube.com/watch?v=MaI0_XdpdP8

6. Spring Boot

- Spring Boot by JavaBrains (34 Videos) [Personally Used]
https://www.youtube.com/watch?v=msXL2oDexqw&list=PLqq-6Pq4lTTbx8p2oCgcAQGQyqN8XeA1x

- Spring Boot Basics by Bharath Thipireddy (12 Videos)
https://www.youtube.com/watch?v=1GXNt3MR1AU&list=PLSg8jHkYTg9Eo994VmdSKDJs9ZhG5Wc57

7. Bonus Tip

For an in-depth guide on how to use these resources and in which sequence to go through these resources read my detailed blog:

https://vikasrajput.in/free-350-resources-to-start-java-web-development-journey

That's it for now!

Every Mon, Wed & Fri - I write a thread
on Fullstack Development.

Like and retweet the first tweet as it will encourage me to put on more Java-related helpful content.

Follow @vikasrajputin to read all my future threads.

Free 350+ Resources to Start Java Web Development Journey

SQL Roadmap for Fullstack/Backend Developer

a thread...

Often as Fullstack/BE Developer, we don't know how much SQL to learn. 

Due to this, few people waste time learning advanced concepts, while few ignore SQL totally.

As Fullstack/BE Developer, you're not expected to have mastery in SQL. 

Because every organisation has DBA Team.

Let's see how much SQL Knowledge is required, to have a successful career as Fullstack/BE Developer.

First come basics, afterwards you can straight dive into below-mentioned topics.

1. Normalisation and Relationships

You should know how to normalise a table.

How to add relationships between them using primary, foreign key.

Learn about different types of keys and constraints which help with data redundancy and validation.

2. Be Good with Queries

Learn DQL and DML, because most of the time you will be searching and managing data in DB, from your application.

Learn DDL, as it will help in defining and restructuring your DB objects like SP, View, Triggers, Functions, Tables, etc.

Have a good knowledge of:

- Joins(INNER, LEFT, RIGHT Joins, etc)
- Operators(AND, OR, etc)
- Datatypes
- Clause(Group by, Having, etc)
- Wildcards
- Aggregate functions(avg, count, etc)
- Different ways to filter/sort records

https://twitter.com/vikasrajputin/status/1517330102400344065

3. Store Procedure, Functions, Triggers, Views

Sometimes, business logic needs to be put on DB side.

Having good knowledge of these topics can easily helps you write complex business logic on DB.

You should know - how to use it, when to use it, and what problems they solve.

4. Basics of Indexing

No need to have advanced knowledge of Indexing.

But you should know how to apply it, and the problem it solves.

To know more about Indexing, check out this thread:
https://twitter.com/vikasrajputin/status/1535072762288410624

5. Improving Query Performance

This will help you in fixing critical performance issues in the production environment.

It is one of the common problems, and knowing about it can add extra stars to your profile.

Check out the below thread:
https://twitter.com/vikasrajputin/status/1538691104169525249?s=20&t=V8zixMyQJh7n_AjVKV3uVw

Conclusion:

Idea behind the thread is to make you aware of important area you should be focusing more on as Fullstack/BE Dev.

This much knowledge is more than enough to have successful career as Fullstack Dev.

Other imp concepts can be learnt as and when required.

Note:

In the exceptional cases, it might differ because few small organisations do not have a DBA team so you might need to learn other advanced concepts as and when required.

Don't follow this Roadmap, if you're DBA or any other Database professional.

That's it for now, hope you learned something new!

Every Mon, Wed & Fri - I write a thread
on Fullstack Development.

Follow @vikasrajputin to read all my future threads.

SQL Roadmap for Fullstack Developer

Become Java Fullstack Developer and Get Top Paid Jobs!

a roadmap...

"Why are you talking about Java?"
"Bro, Java is outdated!"
"Nobody on Tech Twitter is talking about Java hence proved Java has no future"

If this is what you're thinking, 
Hear me Out!!!

Java is there for 20 yrs, running on billions of devices, used by all the top tier companies to build the ultimate enterprise apps, with one of the biggest communities, checkout on any job portal for Java jobs you will find top results.

Java is still going to rule, Undoubtedly!

Now, let's see how can you become a Java Developer in 2022 and start your Fullstack Development Journey...

1. Core Java

Core Java forms the fundamentals of programming, it is based on Object-Oriented Programming.

Spend a reasonable amount of time learning it, as it will decide how good a Java programmer you will be in the future.

2. JDBC + SQL

As part of Core Java, you will learn JDBC which will help you understand how to connect your Java apps to Database.

Alongside you can also start learning the basics of SQL, learn different types of Joins, INSERT, UPDATE, DELETE, SELECT statements, etc.

2. JSP+Servlet

JSP+Servlet is the core concept of Java Web Development, it will help you understand the fundamentals of Java Web Development.

Before Jumping into any Java web based framework, it's important to know the core concepts, JSP+Servlet can help you get that.

3. Spring Framework

It's the most popular & trending framework used to build modern web apps.

All the modern Java Webapps are using it, every organization working in java is using it hence you cannot skip this.

4. JPA/Hibernate

Another framework helps you work with Databases easily in your Java application.

You can do almost everything in DB from your Java app using this framework, no advanced SQL knowledge is required. 90% of the time you never have to write any native SQL query.

5. HTML/CSS/Javascript

For building frontend, you can use HTML, CSS, and JS to build amazing web pages.

Nowadays, people are building REST APIs, so you can separate your backend and frontend.

This way you can use React, Angular, Vue, etc JS frameworks to build awesome UIs.

6. Servers

Tomcat is a very popular server to deploy Java-based applications. 

You can learn to make deployments in your local machine.

Basic knowledge of servers always helps, don't skip this part.

Package your Webapp as Jar or War, and deploy it on tomcat.

7. Backend Tips:

Learn Basic DevOps. 

Learn to deploy & host your apps on any cloud system

Use Git & Maven/Gradle.

Learn SQL.

Choose Eclipse/IntelliJ as your IDE for development on Java

8. Frontend Tips:

Use VS Code as IDE for Frontend Dev.

Learn npm, which can help you speed up your Frontend Dev.

Note:
I've mentioned the above specific tools because in my personal experience I've found them widely used by organizations for Java Fullstack Development.

That's it for now!

If you love this thread, please like and retweet the first tweet. 

It encourages me to put on more Java-related content on Twitter.

Read my previous thread on OOPs Concept to start learning Java today:
https://twitter.com/vikasrajputin/status/1510819869431779331

Small Announcement! 📢

I've opened my calendar for my audience and love to interact with you over 1:1 sessions on:

1. Career Guidance/Mentorship
2. Candid Talks
3. Content Creation
4. Java Career Path

For more details visit:
https://calendly.com/vikasrajputin/101

Namaste I'm Vikas,

I write a thread every Mon, Wed & Fri 
on Java, Javascript & Fullstack Development.

To read all my future threads follow @vikasrajputin

Become Java Fullstack Development and Get Top Paid Jobs

1. Definition

CI/CD stands for Continuous Integration - Continuous Delivery.

2. What is Continuous Integration?

In the Dev team, multiple developers work on different modules where daily code is committed. 

Dev tests their part of the code but many times they don't do integration testing.

For this, they need other's code as well this is where CI comes.

CI process, integrates code from all team members, builds the project and runs integrations tests and unit tests on the project.

It saves time, and informs of any bugs in the early stage.

This process is completely automated there's less chance of human errors.

CI process is always connected with a code repository.

The moment someone merge their code in the repository. It starts the build.

At any given time, it gives the latest status of the repository for any possible errors.

3. Continuous Deployment

After the source code is merged, build & unit tested, it is time to deploy it on a QA server for QA testing.

Again this is a continuous process, which means the moment code is merged it will be deployed on server via CI/CD pipeline.

QA tests and reports for any bug.

That bug is fixed by Dev.

Code gets merged & deployed Instantly on server.

Instantly available to QA for further testing. Thanks to CI/CD pipeline!

This full process is completely automated & super fast.

4. How does it work?

Popular tools like Jenkins, Bamboo,etc are used to create a CI/CD pipeline.

For deploying code on each server, there is a separate pipeline which is connected to there respective repository.

For, eg: Separate pipelines for QA, Stage, Prod env.

5. Benefits:

Fully automated system with fewer human errors.

Saves time, and increases the efficiency of the team.

Feedback loop is more frequent between end-customer and the software development team.

Blends well with Agile and DevOps culture.

6. Conclusion

Various organizations use if differently based on their requirement.

Some only uses CI. Some only uses CD and some both.

Some company only uses CI/CD for QA env only, due to limited access to prod env or due to someother reasons.

That's it for now!

I hope you learned something new.

If you loved this then you might also like my previous thread on DevOps:
https://twitter.com/vikasrajputin/status/1533618177459900417

Small Announcement! 📢

I've opened my calendar for my audience and love to interact with you over 1:1 sessions on:

1. Career Guidance/Mentorship
2. Candid Talks
3. Content Creation

For more details visit:
https://calendly.com/vikasrajputin/101

What is CI/CD?

Javascript: What is a Promise?

a thread...

1. Real-world Analogy:

In Real-world, when we promise, we guarantee to perform something in the future. 

When the right time comes, we either fulfil it or fail it.

2. Promise in Javascript:

Similarly, a promise is a special object that asynchronously performs an operation defined in it.

If this operation is completed successfully, we can say a promise is resolved successfully otherwise the promise is considered as rejected.

3. Status of Promise:

PENDING: 
When the promise is running and not yet finished.

RESOLVED: 
The promise has been finished or been resolved successfully.

REJECTED: 
The promise has finished with errors.

4. Two important steps when working with a promise

Defining a Promise:

Here we can add the operation we need to perform inside it and based on it we can pass success and error msg.

Calling the Promise:

Here we can chain the next function based on success & error scenario.

5. How to Define?

By using a Promise constructor with two params - resolve and reject.

If the operation performed inside promise is completed successfully then it calls resolve() method with a success message.

Otherwise, it calls the reject() method with an error message.

6. Calling the Promise:

When calling, we can specify what next function we need to run after a promise is completed (either with error or success).

For success scenario - use resolve() & then() methods.

For error scenario - use reject() & catch() methods.

7. resolve() and then():

The success message passed in the resolve() method can be obtained back using the then() method while calling the Promise.

As shown below: 
When a promise is resolved successfully, we can get msg in then()

8. reject() and catch():

Similarly, the error message passed using the reject() method can be obtained back using the catch() method when calling a promise.

As shown below:
When the promise has an error, an error msg can be obtained via the catch method:

9. Chaining next functions in Promise:

We can chain as many functions in promise using then(), which makes it call sequence of operations asynchronously.

Below we've chained multiple functions using the same example:

Thank for Reading!

If you like this, then you might also like my previous thread:

https://twitter.com/vikasrajputin/status/1518409469767548928

Namaste, I'm Vikas!

I write a thread every Mon, Wed & Fri on 
Java, Javascript & Fullstack Development.

To read all my future threads follow @vikasrajputin 

Javascript: What is a Promise?

1. Definition

It is a technique, using which we can improve search performance in our database.

Helps in quickly searching the records in the table.

2. Example:

You've mostly seen the books with an Index page,
where multiple pages are grouped into one chapter and list them.

This allows us to skip unnecessary pages/chapters and go to our favourite page/chapter quickly.

It's nothing but indexing.

Similarly,

When we search any record in DB, it goes to the index and finds the exact location of the record and skips the unnecessary records in between and quickly gives us the results.

Note:

Different DB vendors have introduced their own types of Index.

Many DB has even more than one type of Index. But more or less their purpose is the same.

The query syntax to define the index may also vary based on the DB vendor.

3. How to Define an Index (in Postgresql):

"CREATE INDEX <IndexName> ON <Table>(<Column>);"

Where,
Table = STUDENT
Column = ROLL_NO

Code Snippet:

4. When to use Indexing

Always remember Indexing should be only applied to the column which is frequently being used in the where clause.

Indexing works great on columns which contain numeric data.

Indexing on primary key columns is not required because most modern databases implicitly apply indexing to them.

5. When not to use Indexing

If DB has fewer records no need to use indexing. it will overkill the purpose of Indexing.

Try to avoid Indexing on a column containing long text-based data, in such case Indexing will be quite poor.

Don't apply it on every column, otherwise, this will degrade the write and update operation on DB. As every write and update operation also updates the Index.

That's it for now!

If you enjoy reading this thread then you might also like my previous thread:

https://twitter.com/vikasrajputin/status/1517330102400344065

Namaste, I'm Vikas!

I write a thread every Mon, Wed & Fri on 
Java, Javascript & Fullstack Development.

To read all my future threads follow @vikasrajputin

SQL: What is Indexing?

7 Pro Tips to Out-Perform an Online Interview

a thread...

1. Test the Interview Link Beforehand

Record yourself and see how you're looking?
Is your voice clear and confident?
If your background looks okay?
Is there a proper light on your face?
Is your internet stable?

Every single detail matters.
Take it seriously.

2. Background Matters

Work on your background. 
Keep it as Simple and Professional as possible.
Check the overall mood it is bringing to the video interaction.

The original background brings more vibe to the video interaction so first, try to play around with it.

If the original background is still not okay, then try to use some professional-looking background wallpaper and see how you're looking. 

Idea is to look natural and look more pro.

You need to do that hard work to look yourself the best with your background, do it beforehand.

3. Introduction

99% of the interview starts with this common question.
"Introduce Yourself"

Still, I've seen candidates giving lame replies.

"I'm XYZ, having so and so years of experience."
"Myself this, and I am X Programmer."

Yes, that's true. I've seen such candidates.

It's your moment to shine. 

Reflect on your confidence & expertise through your words.

Talk about:
Something which is not in your CV
Project details
Practical Skills
Highlights of your career

Narrate your story
Prepare it yourself
Keep it concise
Should be 3-4 mins long.

4. How to give answers

Give, answers like you're talking to a 6 yo.

Pick examples that a 6 yo can understand, and avoid complex examples, simple example saves time.

A simple example indicates that you've truly understood the basics.

End your answer with some other topic that you already know very well. 

Because interviewers mostly like to go with the flow and this is how you can direct your own interview. Try it you will love it!

Avoid too long/short answers. 

Keep it concise and to the point.

5. Wear your Smile

Yes, wear your smile, throughout the interview, it keeps the overall environment positive and light.

It is the most underrated skill, try it and you will see the difference.

6. What if you don't know the answer?

No problem! 

As a programmer, you're not expected to know everything.
So chill...

Try to guess the answer and explain to the interviewer, why you think that could be the possible answer, explain your logic loud and clear.

Avoid guessing, if your logic is incorrect and contradicts your other answer.

If you've no clue, just say - "As I've not worked in so and so area, I don't have much knowledge"

"It's been too long since I've not gone through that topic so I don't remember at the moment.

7. Ask Questions, at the End

99% of interviewers, ask a question to know your interest so show your interest by asking a deep and meaningful question.

Avoid asking silly questions and questions about your interview feedback.

Ask questions about your role, the tech stack you're going to work on, the team and their work culture, the kind of project the company works on, etc.

- You can also discuss any interesting question asked by the interviewer in the end, if you don't know the answer.

Thanks for Reading!

Hope you liked it, it was based on my 100+ Interview Experiences in 8 years of my career.

If you like these then you might also like this:
https://twitter.com/vikasrajputin/status/1531806740777291776

Namaste, I'm Vikas.

I write a thread every Mon, Wed & Friday on Java Javascript & Fullstack Development.

To read all my future threads follow @vikasrajputin

Take care!