Nikhil Pathak retweeted
People when they start their career they always have a hero growing up !!
For example : Virat Kohli idealized Sachin Tendulkar !!!
For a lot of Engineers: they could be Mark Zuckerberg or Bill Gates !!!
And They could be the most successful Man in the planet Earth, Elon Musk !!
But For me It always been Linus Torvalds !!!
@Linus__Torvalds
Please tag yours !!!
Nikhil Pathak retweeted
A DecaBillion $ Idea : Build a browser !!!
There are many pain points that none of the big guys are solving !!
For example:
- Brave is just offering ad blocker and lower latency and people are loving it.
- But it takes too much space too
Solve this problem and become next big thing in the Industry !!
Nikhil Pathak retweeted
Every Window's Update tagline should say :
"We have added some bugs to make your life more miserable."
Thank you we truly hate you !!!
Nikhil Pathak retweeted
Job Description : Freshers Software Developer
Skills : Claude Code, GPT, and AWS
this is what many new startups are demanding
Nikhil Pathak retweeted
Open for Gigs – Full Stack Developer Available
I can help with:
• Frontend & Backend Development
• Next.js
• React
• Vite
• Node.js
• MongoDB
• And related modern web technologies
Available at $39/hr
If you need reliable, scalable, and clean code — reply or DM me
Nikhil Pathak retweeted
Every revolution in technology has some essential factors:
- There would be a new guy
- The person would beat all the big companies
- The person is going to be the next big thing in the world.
- Example : @Google , @Apple , @facebook and all
So what the AI revolution is missing is:
- A new name
- a new company
- Every company is loosing that company
- And amazing big companies rise up with this revolution.
why do you think this is not happening in this AI revolution?
Nikhil Pathak retweeted
Ratio of my bugs in code :
1. 80% typo,
2. 10% auto import didn't work
3. else logic
what's your ratio ???
Nikhil Pathak retweeted
Authentication:
It verifies who the user is .
Authorization:
It checks what the user is allowed to do.
Nikhil Pathak retweeted
GET is used to retrieve data sends parameters in the URL, it is safe, idempotent, cacheable, and should not be used for sensitive information.
POST is used to send or create data, send parameters in the request body, is not idempotent, and is more secure for sensitive operation
Nikhil Pathak retweeted
Solving Problem : Simplify Path
It is one of the easiest problems i have solved.
Steps:
👉 split the path (input)
👉 initialize a stack
👉 iterate over parts
👉 If it is ' . ' continue
👉 If it is ' .. ' pop
👉 else append
👉 return the joined path by '/'
Have you solved this ?
#LeetCode #SoftwareDevelopment #DSA
Nikhil Pathak retweeted
✅ Day 13 — Effective Python Coding Series
🔥 Today’s focus: Closures & Properties 🐍
Closures are functions that remember variables from their enclosing scope, even after the outer function has returned.
✨ They enable reusable & modular code, maintain state across calls, and allow custom behavior without rewriting logic.
Properties let you define methods that look like attributes, while still giving you the flexibility of methods.
✨ Perfect for validating input, computing derived values on the fly, and keeping your code clean, readable, and maintainable.
Closures = functions with memory 🧠
Properties = methods in disguise 🎭
👉 Whether you’re a Developer, Data Scientist, ML/AI Engineer, or simply someone who loves Python 🐍 — these features are must-know tools to write cleaner, smarter, and more Pythonic code.
🚀 Follow me for daily Effective Python Coding posts and sharpen your Pythonic thinking every day!
#Python #100DaysOfCode #DataScience #ML #AI
Nikhil Pathak retweeted
What are you looking for in a post.??
What you see when you hit the like or follow the person. ??
I like software engineering and some nice tips and some work that people are doing then i hit the like and try to connect to people by following them.
Please mention yours👇
Nikhil Pathak retweeted
💡 Maximal Square Problem – Step by Step
Problem Statement:
Given a binary matrix of 0s and 1s, find the area of the largest square containing only 1s 🟦.
First Approach (Brute Force):
Check every possible square in the matrix to see if all cells are 1s.
✅ Works but slow → Time Complexity: O((m×n)²)
Optimal Approach (Dynamic Programming – Overlapping Subproblems):
We define dp[i][j] as the side length of the largest square ending at cell (i, j).
Base Case: First row & first column → dp[i][j] = matrix[i][j] 📝
Core Idea:
if matrix[i][j] == 1:
dp[i][j] = 1 + min(dp[i-1][j], dp[i][j-1], dp[i-1][j-1])
else:
dp[i][j] = 0
This ensures we only grow squares that are fully valid.
✅ Time Complexity: O(m×n)
✅ Space Complexity: O(m×n) (can be optimized to O(n))
Reflection:
Whether you are a software developer, data scientist, or student, solving such problems is not just coding—it’s sharpening your mind 🧠⚔️ for more complex challenges 🚀.
If you enjoy DSA and problem-solving, follow me for more challenging problems and insights.
👉 Join me on this journey and level up your coding and problem-solving skills!
#DSA #ProblemSolving #SoftwareDevelopment
Nikhil Pathak retweeted
Time zones can be a silent killer of web apps.
If you don't handle time zones correctly, bugs show up fast and create confusion. A user from Europe sends an order at 9 am CEST and the customer service in Singapore sees it as 4 pm instead of 3 pm.
How developers mishandle the timezone issue:
- Offsets hardcoded in code
- Manual DST adjustments
- Confusing "server vs browser" times
That's not timezone handling. That's chaos.
Here are the correct ways to handle time zones:
1. Store every timestamp in the database in UTC (no daylight savings, no offsets).
2. Convert only at input/output.
3. Let the frontend and backend libraries handle DST & offsets.
4. APIs should always return timestamps in ISO 8601 UTC (e.g. 2025-09-28T04:00:00Z).
5. Show time in the user’s local time zone with clear formatting.
Nikhil Pathak retweeted
🐍 Day 12 — Effective Python Coding Series
🔥 Today’s focus: Named Tuples
Python’s named tuples are a convenient and efficient way to create lightweight, immutable objects with named fields.
🔹 They’re essentially a subclass of tuples but with readable, self-documenting field names.
🔹 Great for representing simple data structures.
🔹 Can often replace dictionaries when keys are always strings.
✨ Why use them?
Enhances readability by giving fields meaningful names
Immutable by design → safer, less error-prone
Lightweight alternative to classes for structured data
Cleaner than dictionaries when you don’t need key flexibility
👉 Whether you’re building data models, working with APIs, or handling structured data, named tuples are a Pythonic way to keep your code organized and expressive.
👉 Whether you’re a Developer, Data Scientist, ML/AI Engineer, Data Analyst — or simply someone who loves Python 🐍 — named tuples are a must-know feature that can make your Python code more robust and elegant.
🚀 Follow along for daily Python tips and sharpen your coding skills every day!
#Python #SoftwareEngineer #DataScience #ML #AI #100DaysOfCode












