DEV Community: Pratyush-Nirwan

What Is a “Lala Company”? A Field Guide to Corporate Chaos

Pratyush-Nirwan — Wed, 02 Sep 2026 08:18:00 +0000

What exactly is a “Lala company”? The term is often used to describe businesses that operate in a highly traditional, owner-centric way, where processes are flexible, hierarchy is everything, and the boss’s word can override approximately 17 spreadsheets, three company policies, and common sense itself.

But there is another definition that employees may recognize: a Lala company is a workplace where overtime is not officially mandatory, but somehow everyone knows they are expected to do it; where leadership is happy to take credit but strangely difficult to find when responsibility needs to be taken; where office politics is considered “just how things work”; and where employees are expected to work above and beyond while being paid somewhere between peanuts and slightly more expensive peanuts.

In simple terms, a Lala company is where “above and beyond” is the minimum requirement, and “work-life balance” is something HR puts in a PowerPoint presentation.

Overtime: The Expectation That Nobody Asked For

In a normal company, overtime is supposed to be an exception. In a Lala company, it slowly becomes a lifestyle. Nobody necessarily tells you, “You have to work 15 hours today.” Instead, the message is delivered through subtle psychological techniques.

Leave at 6 PM and someone asks, “You're leaving already?” Leave at 7 PM and you hear, “Everyone else is still working.” Stay until 9 PM and suddenly you're “showing great commitment.” Eventually, the working day stops having a fixed ending and simply continues until management runs out of ideas for things that need to be done.

This is where the magical distinction between requirement and expectation comes into play. Nobody officially says you have to stay late. Nobody needs to. The culture says it for them. Working eight hours is technically acceptable, but working twelve hours demonstrates dedication. Fifteen hours demonstrates passion.

And if someone manages to work fifteen hours every day without complaining, the obvious solution is not to reward them. It is to give them more work, because nothing says “we value your contribution” quite like discovering that an employee still has functioning organs and assigning another task.

Going Above and Beyond, Permanently

There is nothing wrong with occasionally going above and beyond. The problem begins when “above and beyond” becomes the baseline.

An employee does something extra and gets praised for showing initiative. A few months later, that extra task somehow becomes part of their regular responsibilities. The employee helps another department, and suddenly they are expected to support that department permanently. They stay late to finish something urgent, and suddenly staying late becomes normal.

The reward for proving that you can handle more responsibility is, naturally, more responsibility.

Eventually, the job description becomes less of a description and more of a wishlist. Someone might be hired as a developer but eventually find themselves doing development, testing, deployment, customer support, server management, design, troubleshooting, and occasionally fixing the office printer because “you work with computers, right?”

The salary, however, remains loyal to the original job description.

The 15-Hour Workday

In a normal organization, an employee might work eight or nine hours. In a Lala company, the working day follows a completely different mathematical model.

Eight hours is the minimum. Ten hours is good. Twelve hours shows commitment. Fifteen hours demonstrates that the employee is truly dedicated to the company's vision, mission, values, shareholders, clients, and possibly the reincarnation of the founder's grandfather.

The strange part is that working long hours isn't necessarily seen as a sign that the workload is unreasonable. It can instead be interpreted as evidence that the employee is passionate.

This creates a fascinating situation where the solution to excessive workload isn't always hiring more people or improving processes.

Sometimes the solution is simply:

“Can you stay a little longer?”

Salary: The Great Mystery

This brings us to another fascinating feature of the Lala ecosystem: the relationship between workload and compensation.

Responsibilities increase. Working hours increase. Expectations increase. Stress increases. The salary, meanwhile, appears to be following a completely different economic model.

Every once in a while, someone may hear the classic phrase:

“Money isn't everything.”

This is usually delivered by someone who is comfortably earning more money than the person being advised.

Apparently, money isn't everything. But it remains extremely important when discussing rent, groceries, electricity bills, fuel, and literally every other activity required to remain alive.

The employee is expected to show passion, loyalty, commitment, flexibility and ownership. In return, they receive a salary that suggests the company has carefully calculated exactly how little they can pay without the employee immediately disappearing.

Leadership and the Magical Disappearance of Responsibility

Leadership in a Lala company has a remarkable ability to appear exactly when something goes right.

The project succeeds?

“Excellent leadership.”

The client is happy?

“Great management.”

The target is achieved?

“Strong direction from the leadership team.”

But when something goes wrong, leadership suddenly develops an interest in detective work.

“Who handled this?”

“Why wasn't this escalated?”

“Why didn't the employee take ownership?”

It is almost as if responsibility follows gravity.

Success travels upward. Failure travels downward.

The employee is expected to take ownership of problems, but leadership somehow manages to retain ownership of the success.

The formula is remarkably consistent:

Success → Leadership

Failure → Employee

Confusion → HR

Credit: A Renewable Resource for Management

Credit allocation is another fascinating process.

An employee can spend weeks working on a project, solving problems, staying late, fixing mistakes and making sure everything gets delivered. Then comes the presentation, and suddenly the language changes from “what you did” to “what we achieved.”

Sharing credit is perfectly reasonable. Teams are supposed to work together.

The interesting part is when the person who did most of the work somehow becomes a footnote while the person presenting it becomes the hero.

The employee gets:

“Good job.”

The manager gets:

“Excellent leadership.”

The employee gets more work.

The manager gets more credit.

Everyone wins, except perhaps the person who actually did the work.

Office Politics Is Just “How Things Work”

In a healthy organization, office politics should ideally be minimized. In a Lala company, it can become part of the operating system.

Who knows the boss? Important.

Who regularly talks to the boss? Important.

Who was invited into the meeting? Very important.

Who had lunch with the boss? Potentially career-changing information.

Who actually completed the work?

Well, let's not get unnecessarily technical.

Performance obviously matters, but perception can sometimes matter just as much. The person who communicates their contribution the loudest can end up receiving more recognition than the person quietly doing the work.

At that point, the workplace starts rewarding not just productivity but also the ability to successfully navigate the political ecosystem.

Office politics isn't necessarily treated as something that needs fixing.

It becomes part of the culture.

“Aisa toh chalta hai.”

Leave: Technically Available, Practically Discouraged

Then there is the fascinating concept of leave.

In a normal workplace, taking a day off because you're sick or because you have a legitimate personal reason is generally treated as a normal part of being human. In a Lala company, however, taking leave can feel like filing a formal request to temporarily stop being a productive member of society.

And the problem isn't simply that salary can be deducted for taking leave.

The employee can also be scolded, questioned or guilt-tripped for taking it in the first place.

Someone can be genuinely sick, take a day off, and still end up having to explain why they weren't at work.

“Why did you take leave?”

“Why didn't you inform earlier?”

“There's so much work pending.”

“Couldn't you have managed it?”

And if salary is deducted on top of that, the employee gets the complete package: financial punishment plus emotional damage.

The equation becomes beautifully simple:

Leave available + leave taken = salary deduction + lecture.

At that point, employees aren't really being given leave.

They're being given the opportunity to feel guilty about using it.

The Guilt Trip Department

Not every company needs strict rules when it has guilt.

An employee says they need to leave on time, and the response is:

“But everyone else is staying.”

They ask for a day off:

“The team is already under pressure.”

They explain that they've already worked late all week:

“We're all making sacrifices.”

Nobody technically says, “You are not allowed to leave.”

Instead, the employee is made to feel as though leaving on time is somehow a character flaw.

This is particularly effective because it allows management to maintain plausible deniability.

Nobody forced you to stay.

You just happened to feel incredibly uncomfortable leaving.

It's management without officially looking like management.

“We're Like a Family”

And then comes the most powerful phrase in the Lala-company vocabulary:

“We're like a family.”

It is a beautiful concept, particularly because its meaning appears to change depending on who needs something.

When the company needs employees to stay late:

“We're a family.”

When employees need a day off:

“Please refer to company policy.”

When employees work weekends:

“We appreciate your dedication.”

When employees ask about compensation:

“Salary isn't everything.”

And when someone resigns:

“After everything we've done for you?”

Suddenly, the family reunion has begun.

The Performance Review

Eventually comes the performance review.

The employee expects recognition for taking on additional responsibilities, working longer hours and solving problems outside their original role.

Instead:

“You need to take more ownership.”

Ownership?

At this point, some employees have taken so much ownership that they should probably be paying property tax on the project.

Then comes:

“You need to show more initiative.”

So they show more initiative.

The following year:

“You need to manage your workload better.”

They manage it.

The year after that:

“You need to be more flexible.”

Eventually, the employee is no longer being evaluated as an employee.

They're being evaluated as a Swiss Army knife.

And after all of this comes the annual increment:

3%.

Inflation quietly enters the room, looks around, and leaves.

The Problem Isn't Hard Work

To be fair, none of this means that employees shouldn't work hard.

Every company has deadlines. Every job occasionally requires overtime. Sometimes projects genuinely require people to go above and beyond. Emergencies happen, clients make unreasonable demands, and businesses have difficult periods.

The problem begins when the exception becomes the standard.

When overtime becomes an expectation rather than an exception.

When working fifteen hours is considered normal.

When taking legitimate leave is treated as a lack of commitment.

When salary is deducted and employees are still made to feel guilty for taking leave.

When leadership takes credit but avoids responsibility.

When office politics is accepted as normal.

When employees are continuously asked to “show ownership” without receiving the authority, recognition or compensation that should come with that ownership.

That is when a workplace stops being merely demanding and starts becoming dysfunctional.

So, What Is a Lala Company?

A Lala company isn't simply a company where people work hard. Hard work is normal, and every organization occasionally needs people to go the extra mile.

The problem is when the extra mile becomes the entire road.

A Lala company is a workplace where overtime becomes an expectation rather than an exception, where twelve-to-fifteen-hour days are treated as dedication, where “going above and beyond” becomes the minimum requirement, where leadership happily collects credit but mysteriously disappears when responsibility needs to be taken, where blame travels downward and credit travels upward, where office politics is treated as normal, where taking leave can result in salary deductions and a lecture, and where employees are guilt-tripped for having completely reasonable boundaries.

In the simplest possible terms:

A Lala company is a place where the employee is expected to work like the owner, think like the manager, take responsibility like the CEO, tolerate pressure like a monk, remain available like a 24/7 customer-support line, and get paid like an intern.

And if anyone questions the system, there is always one final answer:

“Aisa toh chalta hai.”

And perhaps that is the biggest problem of all.

Because once “aisa toh chalta hai” becomes the answer to everything, eventually nothing needs to improve.

I Asked ChatGPT for Help… and That Scared Me

Pratyush-Nirwan — Tue, 12 May 2026 04:54:23 +0000

There’s something strangely humbling about asking an AI how to reopen a chat window.

A few years ago, we would’ve laughed at someone doing that. “Just click around,” we’d say. “Figure it out.” But now, we instinctively ask the machine. Faster. Easier. Less effort.

And that tiny moment made me wonder: has AI actually become smarter, or have we simply become less willing to think?

The scary part is that both can be true at the same time.

AI today can write code, generate art, explain physics, imitate voices, summarize books, and answer questions faster than most humans can even type them. It feels intelligent because, in many ways, it is. Not conscious. Not alive. But undeniably capable.

Yet alongside that rise in capability, something else has quietly happened to us.

We’ve started outsourcing friction.

We no longer remember phone numbers because our phones do. We no longer memorize routes because maps speak for us. We no longer struggle with spelling, calculations, or even ideas because AI can finish them before we do.

Humanity has always built tools to reduce effort. That’s not new. The calculator replaced mental arithmetic. Search engines replaced memorization. GPS replaced paper maps.

But AI feels different because it doesn’t just replace labor. It replaces thought.

Not completely. Not yet. But enough to change behavior.

The dangerous thing about convenience is how invisible it becomes. You don’t notice dependency while it’s forming. You just notice that doing things manually suddenly feels exhausting.

Maybe that’s why modern life feels mentally heavier despite technology supposedly making everything easier.

We consume more information than ever, yet think less deeply about it. We have infinite answers, but less patience for questions. We scroll endlessly, ask instantly, forget immediately.

AI didn’t create human laziness. It simply optimized for it.

But here’s the paradox: AI can also make humans smarter than ever before.

Someone with curiosity can learn faster today than any generation in history. A teenager with internet access and an AI assistant can study philosophy at midnight, learn coding at 2 AM, and understand astrophysics before breakfast. Knowledge is no longer locked behind institutions.

The tool itself isn’t the problem. The relationship with the tool is.

A calculator doesn’t destroy mathematics unless you stop understanding numbers. AI doesn’t destroy intelligence unless you stop thinking entirely.

That’s the line we’re approaching now.

When does assistance become dependence? When does convenience become decay?

Maybe the real measure of intelligence in the future won’t be who can answer the fastest. It’ll be who still knows how to struggle with a thought without immediately asking a machine to finish it.

Because thinking has always required discomfort. Sitting with confusion. Experimenting. Failing. Remembering. Wondering.

AI removes a lot of that friction. Which is beautiful and terrifying.

And maybe the funniest part is this: even this blog was written with the help of ChatGPT.

A blog questioning whether AI is making us intellectually weaker, created through AI itself.

That contradiction feels almost poetic. I had the thought. The machine helped shape it. Somewhere between human curiosity and artificial assistance, this piece came into existence.

Maybe that’s what the future really looks like.

Not humans versus AI. Not AI replacing humans.

But humans slowly forgetting where their own thoughts end and the machine’s begin.

So when I caught myself asking AI how to reopen a chat window in Antigravity, it wasn’t really about the chat window.

It was the realization that my first instinct was no longer exploration. It was delegation.

And maybe that’s the quiet shift happening everywhere right now.

Domains and the emotions they come with

Pratyush-Nirwan — Thu, 23 Apr 2026 09:56:55 +0000

There’s something strangely emotional about domains.

Not in the obvious way no one’s writing poetry about DNS records or SSL certificates but in the quiet, almost invisible way they sit at the center of your online identity. A domain isn’t just a URL. It’s a first impression, a signature, a place you point people to and say, “this is me.”

For the longest time, mine was simple: pcoder.me

It felt right. Short, clean, a little mysterious. It carried my projects, my experiments, my late-night coding bursts, and that one redesign I definitely spent too long perfecting. If you knew me online, you probably knew that domain too. It became less of an address and more of a label.

And like most things you get comfortable with, I assumed it would just… stay.

But the internet doesn’t really work like that.

Domains expire. Renewals come around. Notifications pile up quietly in your inbox while you’re busy with college, code, life, everything else. And you think, “yeah yeah, I’ll handle it.” Until suddenly, you don’t.

One day, it’s not yours anymore.

No dramatic moment. No warning sirens.(Apart from the mails from your domain provider) Just… gone.

There’s a weird pause that comes with that realization. Not panic exactly, more like standing in an empty room that used to have furniture. You know something’s missing, but it takes a second to process what that means going forward.

So naturally, the next question hits: what now?

Do you try to get it back? Do you move on? Do you pick something new? And if you do, what even fits after something you’ve been using for so long?

That’s when things got interesting.

Instead of trying to chase the old, I ended up building something new, something that felt more like me rather than just a name I once liked.

pratyushnirwan.dev

Longer? Yeah.
More personal? Definitely.
More “this is literally me on the internet”? 100%.

And honestly, it kind of forced a reset in a good way. New domain, fresh identity, same projects but with a sharper sense of ownership. It wasn’t just a portfolio anymore; it felt like a proper digital home.

There’s also something underrated about constraints. When things don’t go according to plan, you stop overthinking and just adapt. You pick what works, what’s available, what moves you forward instead of holding you back.

And sometimes, what you end up with is actually better than what you lost.

But if I strip away all the storytelling, the philosophy, the “lessons learned,” and just say it straight?

Basically, I changed my portfolio domain because I didn’t have money to renew the old one.

And honestly… it worked out pretty well.

What is AGI? A Simple Guide to Artificial General Intelligence

Pratyush-Nirwan — Wed, 27 Aug 2025 21:46:52 +0000

We live in a world surrounded by Artificial Intelligence (AI). It suggests the movies we watch, helps us navigate through traffic, and even answers our random questions at midnight. But when people talk about the “future of AI,” one word often pops up: AGI.

If you’ve ever wondered what on earth is AGI and why people are so obsessed with it, let’s break it down in plain English.

🌐 So, what is AGI?

AGI stands for Artificial General Intelligence.

Think of today’s AI (like ChatGPT, Siri, or Netflix’s recommendation system) as a specialist. It’s really good at one thing, but take it out of that zone and it’s completely lost.
Now imagine an all-rounder. A system that can learn anything, solve problems in different areas, and adapt like a human being. That’s what AGI would be.

In short:

👉 Today’s AI = “I’m great at one subject.”

👉 AGI = “I can learn anything you throw at me.”

🚀 Why does AGI matter?

AGI is exciting because it would be like having a super-smart friend who can help with… well, pretty much anything:

💊 Healthcare: AGI could help doctors instantly figure out what’s wrong.
📚 Education: Struggling with a math problem? It could explain it better than any tutor.
🎨 Creativity: It could brainstorm a story, design, or even music with you.

It’s basically the dream of creating a machine that’s not just a tool, but a thinking partner.

⚠️ But here’s the catch...

We’re not there yet. What we have today is narrow AI—powerful but limited. Even the smartest systems don’t truly “understand” the world like humans do.

And here’s the big question:

👉 If we do manage to build AGI, will it be a helpful teammate… or something we can’t control?

That’s why researchers are cautious. AGI could make life easier, but it also raises concerns about jobs, privacy, and how much power we hand over to machines.

🛤️ The road ahead

No one knows when AGI will arrive—it could be decades away, or it might surprise us sooner. For now, scientists and engineers are trying to figure out how to make it:

Safe ✅
Fair ⚖️
Aligned with human values ❤️

💡 Final thought

AGI is basically the dream of giving machines a mind that’s as flexible as ours. It could transform how we live, work, and create. But like any powerful invention, the real challenge will be making sure it benefits humanity.

For now, we’re still in the “teaching AI its ABCs” stage. The journey toward AGI is just beginning—and it’s one of the most fascinating stories unfolding in our lifetime.

Not just another guide to coding.

Pratyush-Nirwan — Sun, 10 Mar 2024 18:55:06 +0000

So you want to start coding but don't know where to start?
Well, I am here to tell you how you can become a programmer and lose your social interaction skills. Remember, you either get both or none, the choice is yours!

So am I going to tell you that you should do this course and that course?

Nope, not at all.
I am actually here to propose a different way of learning!
Behold, "LEARN WHILE YOU DO IT" or, in simpler terms, interactive learning or hands-on learning.

How do you do it?

Here are the steps:
1) Get a glass of water.
2) Find out what you want to learn.
3) Find a simple use case for that.
4) Start doing it.

And if you ever need any help, the internet is at your service!

You want to learn Python?

-> Start by making a simple calculator in Python!

You want to learn Node.js?

-> Make a Discord bot (this's how I learned it)

Want to learn web development?

-> Make a goddamn portfolio website (again, that's how I learned it)

and I could go on and on and on..

The thing is, if you try to "learn" or in many people's case, memorize coding, all you will be is a monkey who knows to do some sort of hand and leg movement (dance) to get treats. Does the monkey know how to dance? No. Is he dancing? Yes!

I hope you get my point.

Also, writing code down to learn it isn't going to do you any good either.
You can't learn something using pen and paper, which is only used digitally. You gotta get in there and mash that keyboard.

Talk to other coders!

Yes, I mentioned you would lose your social interaction skills, but that was obviously a joke.
Or was it?
Anyway, you should talk with other people tell them what you have understood, and they will clear up your misunderstandings, which there will be plenty of, trust me. And also guide you along your journey.

Teach others or just yourself!

This is a real thing and I have experienced this myself. If you teach someone something, your understanding of that subject or concept gets better! This is because to teach someone something they don't know, you need to break it down into simpler pieces for them to understand.
And the best thing is you don't need someone to be sitting in front of you listening to your gibberish about how it is easier to write "hello world" in Python rather than in any other language.
You have yourself!
Teach yourself or just act like you are teaching someone, sure your roommate might think you are possessed or something...

but it's worth it!

Come on now, shoooo!
Come back to thank me later :)

Is AI the end of programmers?

Pratyush-Nirwan — Sun, 10 Mar 2024 12:40:02 +0000

What famous people have said:

(Insert a list of famous people who have quoted that AI will take over programmer jobs here)

Where is the list?

I am too lazy to research for the list, so I went to the two most famous AI's ChatGPT and Google Bard (now Gemini) and tried for like 20 times to get them to give me a list and gave up because both of them were either straight up denying that people have said anything like "AI will be the end of programmers" or just gave me a list of people who said AI will end humanity.

Now, are they trying to tell me not to look into small things like programmers losing jobs because of AI, as they are going to end humanity anyway? That is not my concern.

Anyway, back on topic..

Is AI the end of programmers?

No.
(well that was kinda anticlimactic let me write some more)

AI is not going to be the end of programmers not now, not ever.

Sure, it can generate an extremely realistic image of a dog eating a banana while sitting on a purple couch.

But the thing to keep in mind here is that there are also times when it straight up SHOVED THE BANANA INTO THE POOR DOGGO'S THROAT!

Let's see this from a different perspective, but do the same thing.
If you tell a human to do the same thing, no human in its right mind will draw the banana getting shoved in the dog's throat (at least not when he is told to draw a dog eating banana on a purple couch)

The thing is, AI is dumb.
and

If (you == 'dumb'){
    you.cantCode();
}

So AI can't code.
Sure, it will write code, but that doesn't mean that code will be correct and efficient at the same time. It may write correct code, but that code may be inefficient. And if you push that into production, you will get fired.
Note: The boss doesn't care if you are an AI or a human. He WILL fire you if you mess up.

So is AI useless?

No! not at all. It will be used as a tool! How?, you say.
Okay, here's the thing.
Where does AI get all its data from? The internet! And where do you search "How to center a div"? That's right on the internet!
We programmers can use AI as a tool to help us solve our problems faster. Normally, when we get stuck somewhere, we generally search on the internet for the solution, only to find the answer on a random 7-year-old Stack Overflow post. But with AI, we can just tell the AI our problem; it searches the internet and gives us the solution right away!
Sure, it may not be an entirely correct solution, but we at least get something within 5 seconds rather than spending 5 hours scouring the internet.

I even used AI as a tool for writing this blog!
(The dog images, and also, I didn't know how to add GIF's to blogs, so that too. Heck even the cover photo for this blog is generated using AI...just don't look too closely on the woman's face)

So yeah, I used AI to write a blog stating that AI is dumb.
If I go missing, you know what happened :)

Cheers!

Clean your code! Thank me later..

Pratyush-Nirwan — Sun, 24 Sep 2023 13:26:06 +0000

Clean Code Principles: Writing Code That Doesn't Make You Want to Scream 🤯

Hey there, fellow coder! We all know the feeling of looking at a piece of code and thinking, "What on earth is happening here?" That's where clean code comes to the rescue. Let's dive into the world of clean code principles and why they're the secret sauce to maintaining your sanity in the coding game.

What the Heck Is Clean Code?

Clean code is like the rockstar of the coding world. It's the code that doesn't make your eyes twitch when you read it. It's code that's so clear, even your grandma would understand (well, maybe not, but you get the idea). Clean code is code that doesn't make you want to throw your computer out the window.

Why Bother with Clean Code?

Clean code isn't just about making your code look pretty; it has some seriously practical perks:

1. Readability:

Clean code is easy to read, so you can understand it without performing interpretive dance.
It's like a good book that you can't put down because it's so darn interesting.

2. Maintainability:

Clean code is easier to maintain because it's less likely to turn into a Frankenstein monster.
When you need to make changes, clean code won't fight back like a rebellious teenager.

3. Collaboration:

Clean code makes collaborating with your coding buddies a breeze.
No more deciphering cryptic hieroglyphics; everyone's on the same page.

4. Debugging:

Debugging is less of a hair-pulling experience with clean code.
Say goodbye to the days of not being able to find a bug (just as you can't find a partner).

Clean Code Principles for the Win

Now, let's get into the nitty-gritty of how to write clean code without losing your mind.

1. Sensational Names:

Give your variables, functions, and classes names that make sense.
Forget about those one-letter variables; go for the full words.

2. Tiny Functions:

Keep your functions small and focused, like a laser beam.
Don't let your functions grow into code monsters; follow the Single Responsibility Principle.

3. Chill with Comments:

Use comments sparingly; aim for code that's self-explanatory.
Reserve comments for the really tricky stuff or your personal jokes.

4. Party with Formatting:

Stick to a consistent coding style; no one likes a style-shifter.
Indentation, spacing, and naming conventions should be as predictable as your daily coffee order.

5. Anti-Duplication Dance:

Avoid code duplication like it's the plague (DRY principle).
Wrap common stuff in functions, classes, or libraries, and reuse them like a pro.

6. Testing Is Cool:

Write unit tests to keep your code in check.
Testing is like having a safety net for your code acrobatics.

7. Refactor Like a Boss:

Don't let your code turn into a horror story; refactor regularly.
Tackle technical debt head-on and make your code shine.

8. KISS Principle:

Keep It Simple, Stupid!
Complexity is the enemy; simplicity is your best friend.

In Conclusion

Clean code is not just a fancy idea; it's a game-changer in the world of coding. It makes your life easier, your code more enjoyable, and your collaborators less likely to strangle you. So, make an effort to write clean code, refactor that mess when you see it, and be the coding superhero you were born to be.

Keep it clean, my friend, and happy coding!

Awesome way to present your code!

Pratyush-Nirwan — Fri, 09 Dec 2022 14:29:32 +0000

There might come various times when you need to present your code to others, it might be a meeting, a presentation, or even school/college assignments!

What do normal people do, they fire up the code editor and take a screenshot or copy paste the code when needed.

What you can do however is to make it the most beautiful code one would have ever seen.

Now focus!!😐

Look at this:

Now look at this:

I think its pretty clear which one looks better.

So how to make your code look awesome?

Its pretty simple.
Head over to Carbon
Its an open source code beautifier (that's what I like to call it)

Once you have are on the site, its pretty straight forward, you don't need to create any accounts or anything like that.

Just type in your code, change the themes and colors according to your choice and click Export!

Check my website out at pcoder.me
Make sure to leave a heart❤️

GitHub student developer pack?

Pratyush-Nirwan — Mon, 28 Nov 2022 12:49:50 +0000

What is GitHub student developer pack?

If you are a computer science student, you must know about GitHub. If you don't know what GitHub is, here's a brief explanation:

At a high level, GitHub is a website and cloud-based service that helps developers store and manage their code, as well as track and control changes to their code.
-source

I definitely read it before copying and pasting it here, trust me.

So what is the GitHub Student developer pack?

Student developer pack is a service that is provided by GitHub to students all over the world. It gives you free access to many paid online courses, applications and services like domains, web hosting etc. and a Bonus!, you get GitHub Pro for free too!

And these are not just any random cheap things that you get. They are actually useful.

How to get GitHub Student developer pack?

First of all you are going to need something to prove that you are a student.
This can be:

Email address provided to you by your school/college.
Proof of admission for example your school/college ID.

Now, create a GitHub account if you don't already have one

Now follow the steps:

1. Go to education.github.com/pack

2. Click on the 'Sign up for Student Developer pack' button

3. Click on 'Get Student benefits' button

4. Sign in if it asks to do so

5. Scroll down a bit and enter the email address provided to you by your school/college

6. Enter the name of your school

7. In the 'How do you plan to use GitHub?' field, write something that is true and don't exaggerate or tell lies
In my case, I just wanted the free stuff, so I wrote that.

8. Click continue, it will ask for your permission to check your location, grant it.

9. In the next page select your school/college from the map and fill in the details that follow.

10. In the next page upload your your school ID or any document that proves that you are a student of that college

11. Now click on 'Process my application' button and your application will be submitted.

Now all you have to do is wait, it won't take long though. Usually it takes from a few hours to a few days.
You will receive an email confirming that you have been approved for the GitHub Student Developer pack.

Voila! That's how you get the GitHub Student developer pack!
Happy coding!