kaushik pardhi

curious

[kaushik pardhi @pardhi88428]

@isha_singh06 Snowflake and oracle

[kaushik pardhi @pardhi88428]

@Im_IrushiK Pwf

[kaushik pardhi @pardhi88428]

@CricTalk29 Linux

[kaushik pardhi @pardhi88428]

@_adityaa21 Only govt job is alive

[kaushik pardhi @pardhi88428]

@Dhruvam987 @Its_Nova1012 Also for the SCD SK is required can't relay on the Primary key . Correct me if I am wrong

[kaushik pardhi @pardhi88428]

@DuruOzii IN

[kaushik pardhi @pardhi88428]

@cloclodma Don't know whether this is right space to ask but If any One guide me I appreciate. Stuck in decision making as I want to do the career switch. I am working as SQL alongwith BA in small scale company. Started to gets hands on ETL , Cloud and snowflake then AI is it worthy

[Edgex @SahilExec]

The irony is:

People are learning AI to stay employable.

But AI is evolving so fast,
keeping up with it starts to feel like a full-time job on its own.

[Kirtesh @AKirtesh]

The hardest time to be a fresher developer:

→ AI writes code faster than you
→ Companies hiring less, expecting more
→ 5 years experience required for entry level
→ Internships are now "enrol and pay"
→ Your degree is already outdated

And the 40+ crowd says:
"Just work hard like we did."

Different era. Different game.
Completely different rules.

[Splendor of SQL 🇬🇧🇩🇪💖 @iam_Uchenna]

Job descriptions for Data Analysts now list dbt, Airflow, and Python scripting. Data Engineer postings want stakeholder management and dashboard experience.

An Analytics Engineer exists somewhere in between, and "context engineering" just started showing up like it's been there all along. The lanes dissolved and nobody sent a memo.

[Dhanian 🗯️ @e_opore]

20 Git commands every developer should know :-

1. git init — initialize a new repository

2. git clone — copy a repository

3. git add — stage changes

4. git commit — save changes with a message

5. git status — check repository status

6. git log — view commit history

7. git diff — see file changes

8. git branch — list or create branches

9. git checkout — switch branches

10. git switch — switch branches (modern alternative)

11. git merge — merge branches

12. git pull — fetch and merge latest changes

13. git fetch — download changes without merging

14. git push — upload commits to remote

15. git stash — temporarily save changes

16. git reset — undo commits or changes

17. git revert — safely undo a commit

18. git remote — manage remote repositories

19. git tag — create version tags

20. git rebase — reapply commits on another base branch

[Minister of Jobs @emmanuelbasy]

I interviewed a candidate today for a Data Analyst role.

Everything was going well until I asked:

“How do you handle messy or incomplete data?”

He smiled confidently and said:
“I clean the data using Excel and remove errors.”

I followed up:
“Can you give a specific example?”

He paused… then said:
“I just make sure the data is clean before analysis.”

At that point, I realized he didn’t fully understand the question.

So I rephrased it:

“Let’s say you’re given a dataset with missing values, duplicates, or inconsistencies, what exact steps would you take?”

He paused again…

Still no clear answer.

I tried one more time.
I gave him practical scenarios:

I even broke it down for him…

And he still couldn’t explain his approach.

That was the turning point.

Because I wasn’t asking what tools you use.

I was asking: How do you think when the data is not perfect?

A strong candidate would have said:

“First, I assess the data to understand the level of issues.
Then I decide whether to drop, fill, or transform missing values.
I remove duplicates using SQL/Excel, standardize inconsistent entries, and validate the dataset before analysis.”

Most candidates don’t fail because they don’t know the tools…

They fail because they can’t apply or explain them in real situations.

[kaushik pardhi @pardhi88428]

@emmanuelbasy Thanks for sharing

[Akhilesh Mishra @livingdevops]

A few years back, I was 30 years old and stuck in an MNC doing Linux support work, wasting years on night shifts for a significantly lower salary than I deserved.

I had come from an NIT(reputed college) and was stuck in this level of work while my college mates climbed the success ladder.

Some worked in the US/UK, and others enjoyed senior-level positions at big companies and all the shiny glamour of a successful career.

I was working on a Platform support role, which people looked at with pity(including myself)

I was working the night shift and providing on-call support on weekends.

I had no work-life balance, and my health was getting worse due to lack of sleep.

I was stuck in a horrible comfort zone, scared of the change.

Imposter syndrome and a severe lack of self-worth were constant companions, and I had zero confidence in myself.

To make matters worse, I got married.

I was under a lot of presure financially and started getting panic attacks due to the fear of getting laid off, as I lacked the skills to do anything other than support work.

After many sleepless nights, I realized something.

If you change nothing, nothing will change.

I decided to make a career switch to Devops as it was something related to work I have been doing for years as a Linux and AIX support engineer.

I started researching online about the devops roadmap, and it was no help as all the posts talked about learning a plethora of tools, and learning all of them felt impossible.

So I turned to YouTube to find better guidance for devops and stumbled upon a channel, Techworld with Nana. It was good and gave me some confidence.

I decided to focus on essential tools for devops and mastering them.

One cloud platform: AWS
One infrastructure as code tool: Terraform
Version control tools: Git and GitHub
One CICD tool: GitHub Actions
Scripting: Python
Containers: Docker & Kubernetes

I started deep-diving into the above topics by watching YouTube videos and reading Medium blogs on all these topics.

I followed the resources and did a lot of hands-on work with these tools. I also went through AWS and Terraform documentation.

After one month of hard work, I started getting some confidence.

I realized that I needed to get some real-world working experience.

I spoke to a few of my friends who worked as devops engineers. I asked them about their day-to-day work and the kinds of work they do.

I cut all distractions and removed social media apps. I studied for two months straight until 6 AM daily(12 am to 6 am after work).

My newlywed wife supported me even though I was not giving her any time

I created real projects based on advice from DevOps friends:
- 3-tier architecture on AWS with Terraform
- Deployed Flask apps on ECS with Terraform and GitHub Action
- Some good Python automations
- Lambda functions and S3 management
- Kubernetes microservices deployments
- Kubernetes troubleshooting scenarios

After 3 months, I updated my resume and started interviewing. The first few were brutal, but I kept learning from each rejection.

I also understood that I cannot switch to devops without showing any relevant experience.

I added 2.5 years of devops experience and curated the devops experience using my friend's resumes.

I updated my LinkedIn and Naukri profiles.

After one week, I started getting a lot of calls for various roles around devops.

I crapped my pants in the first few interviews as they asked the question that only an experienced devops engineer would answer.

I did not let it discourage me, as I knew it would happen. I used the questions the interviewers asked and prepared for the topics around them in depth.

After three/four interviews, I started getting better.

Shortly, I received two offer letters from relatively small companies.

I continued giving more interviews and got three more offer letters from reputed companies.

It changed my life completely. I had everything.

A handsome salary with a bunch of great benefits.
Respected designation at a reputed company.

Day working hours, free weekends, and work-life balance.

Confidence, self-worth, and motivation to do more.
I am inspired to take my career to another level.

I used these offer letters and negotiated a good package(2.5x of my current CTC).

My life changed completely:
- Handsome salary with great benefits
- Respected designation at a reputed company
- Day working hours and work-life balance
- Improved health and confidence

If you're stuck in a career that drains your soul, remember: the first step is the hardest but also the most important.

And remember: If you change nothing, nothing will change

This was the start of what I am today.

[pulkit mittal @pulkit_mittal_]

My friend chose WFH and decided to stay in his village.

Salary -> 50 LPA
Cost of living -> almost 0 LPA

Everyone said he made the smartest decision.

Bangalore rent saved -> 2.5 LPA
Travel cost saved->1LPA
Home food every day.

On paper, he was saving lakhs every month.

But reality was different.

Tech meetups in Bangalore -> missed
Manager visibility -> low
Team bonding -> almost none

There was a startup meet in Banglore, but he couldn’t go.

Meanwhile village life had its own surprises.

Relatives dropping in anytime -> daily interruptions
Local functions -> “you must attend”
Random responsibilities -> unavoidable
Quiet focus time -> rare

Slowly something changed.

He was still working.

But he wasn’t really in the loop anymore.

Decisions happened without him.
Opportunities passed quietly.
His network stopped growing.

Money saved.

But career momentum slowed.

Sometimes the most expensive thing isn’t rent.

It’s distance from the room where things happen.

[yourclouddude @yourclouddude]

SQL interview challenge:

“Find the 2nd highest salary per department.”

If you can solve this using:
• window functions OR
• correlated subquery

You’re job-ready.

[Jaydeep @_jaydeepkarale]

System Design was hard until I watched these videos

[Leonard Rodman @RodmanAi]

Everything you need to know for coding interviews in one roadmap.

Coding Interviews
│
├── 1. Data Structures
│ ├── Arrays
│ ├── Strings
│ ├── Hashmaps
│ ├── Linked Lists
│ │ ├── Singly
│ │ └── Doubly
│ ├── Stacks
│ ├── Queues
│ ├── Deques
│ ├── Heaps / Priority Queues
│ ├── Trees
│ │ ├── Binary Tree
│ │ ├── Binary Search Tree
│ │ ├── AVL Tree
│ │ └── Red-Black Tree
│ ├── Tries
│ ├── Segment Trees
│ └── Fenwick Trees
│
├── 2. Core Problem Patterns
│ ├── Two Pointers
│ ├── Sliding Window
│ ├── Binary Search
│ ├── Recursion
│ ├── Backtracking
│ ├── Greedy Algorithms
│ ├── Divide & Conquer
│ └── Sorting
│ ├── Merge Sort
│ ├── Quick Sort
│ └── Heap Sort
│
├── 3. Dynamic Programming
│ ├── Memoization
│ └── Tabulation
│
├── 4. Graph Algorithms
│ ├── BFS
│ ├── DFS
│ ├── Topological Sort
│ ├── Dijkstra
│ ├── Bellman-Ford
│ ├── Floyd-Warshall
│ ├── Kruskal
│ ├── Prim
│ └── Union Find
│
├── 5. Advanced Techniques
│ ├── Bit Manipulation
│ ├── XOR Tricks
│ ├── Prefix Sums
│ ├── Difference Arrays
│ ├── Kadane’s Algorithm
│ ├── KMP
│ ├── Rabin-Karp
│ ├── Z Algorithm
│ └── Manacher’s Algorithm
│
├── 6. Object-Oriented Design
│ ├── SOLID Principles
│ └── Design Patterns
│ ├── Singleton
│ ├── Factory
│ ├── Builder
│ ├── Adapter
│ ├── Observer
│ ├── Strategy
│ └── Visitor
│
├── 7. System Design
│ ├── CAP Theorem
│ ├── Load Balancing
│ ├── Caching (LRU / LFU)
│ ├── SQL vs NoSQL
│ ├── Sharding
│ ├── Replication
│ ├── Message Queues
│ │ ├── Kafka
│ │ └── RabbitMQ
│ ├── Microservices
│ └── API Gateway
│
├── 8. Design Problems
│ ├── URL Shortener
│ ├─�� Twitter
│ ├── WhatsApp
│ ├── Netflix
│ ├── Google Drive
│ ├── Payment System
│ ├── Notification System
│ └── Live Streaming Platform
│
└── 9. Interview Survival Skills
├── Thinking Out Loud
├── Recovering from Bugs
├── Explaining Tradeoffs
└── Staying Calm Under Pressure

Save this before your next interview.

[Abhishek Singh @0xlelouch_]

Your application does `SELECT * FROM orders WHERE status = 'pending'` which returns 100K rows, but you only display 20 on the first page. Server runs out of memory.

How will you fix this?

[kaushik pardhi @pardhi88428]

@anushkacodess Okay