I Built a Website This Weekend. It Made Me Rethink Everything About Work.

I have lived in Bengaluru since the start of 2019. I have had some wild weekends in this city. The kind you half-remember, the kind that make good stories at dinner. But this past weekend was the best one I have had here, and I spent most of it staring at a screen.

I built my personal website. Bought a domain. Designed the pages. Published it on the internet. You can go visit it right now at adityaojha.site. It is live. It is real. It is mine.

And I felt something I genuinely did not expect to feel. Satisfaction. Not the fleeting kind you get from a good meal or a night out. The kind that sits in your chest and stays.

Here is what surprised me about it.

The problems were the point

I went into this thinking the hard part would be the design choices. Fonts, colours, layout. That stuff is hard, sure. But the real challenge was the hundred small problems I did not see coming.

Domain configuration. DNS propagation. Image compression breaking a layout. Hosting quirks. Deployment errors that made no sense until they suddenly did. You get the drift.

Some of these problems I anticipated. Most, I did not. And every single one of them required me to think, search, try, fail, adjust, and try again.

That loop is what made the weekend feel meaningful. Not the finished product. The process of running into a wall, figuring out which wall it actually was, and then finding a way around it.

I think we underestimate how much of human satisfaction comes from solving problems we chose for ourselves. Not problems assigned to us in a sprint planning meeting. Problems we picked up because we wanted to build something that did not exist before.

AI made this possible. That is the part worth thinking about.

Let me be honest about something. I am not a web developer. I have spent 7 years in tech support, not frontend engineering. Five years ago, building a personal website from scratch would have taken me weeks of learning, or I would have had to pay someone to do it.

This weekend, I used AI as a collaborator. Not in a hand-wavy, futuristic way. In a very practical, “I do not know how to fix this CSS issue and I need an answer in the next ten minutes” way.

And it worked. Not perfectly. AI does not eliminate problems, it just changes which problems you are solving. Instead of spending three hours learning flexbox from scratch, I spent that time on decisions that actually mattered. What should this site communicate about me? What is the hierarchy of information? What do I want someone to feel when they land on this page?

The tedious parts got compressed. The meaningful parts got expanded. That ratio shift is the thing nobody talks about when they talk about AI.

So I started thinking about jobs

Here is where the weekend took a philosophical turn.

If I, a person with zero web development experience, can build and deploy a personal website in a weekend, what does that mean for the people whose job it is to build websites?

I am not asking this to be provocative. I am asking because the question has real consequences for how we all think about our careers.

Jobs, as a concept, are remarkably recent. For most of human history, people did not have jobs. They had trades. They had crafts. They had skills they offered directly to people who needed those skills. The blacksmith did not work for a blacksmithing corporation. The weaver did not report to a Chief Weaving Officer.

The job, the stable salaried position within a large organisation, is roughly a 200-year-old invention. We treat it like it is a natural law. It is not. It is a product of the Industrial Revolution, a specific solution to a specific problem: how do you coordinate large numbers of people to operate complex machinery and systems?

AI is changing the nature of that problem. When one person with the right tools can do what used to require a team of five, the math that justifies large teams starts to break down.

I am not predicting mass unemployment. I am predicting a structural shift in how work gets organised. And I think the direction is backward, toward something older.

The specialist era is coming back

Before jobs existed, people were specialists. They were known in their communities for what they could do. The carpenter. The healer. The merchant. The storyteller.

Then industrialisation happened, and we traded specialisation-as-identity for specialisation-as-function. You were not the carpenter anymore. You were Employee #4,271 who happened to work in the woodworking division. Your identity was your role within someone else’s system.

I think AI is unwinding that trade.

When the tools become powerful enough that one person can handle the execution that used to require a department, the value shifts. It moves away from “can you do the thing” and toward “do you know which thing to do, and why.”

Judgment, taste and context. The ability to look at a problem and know which parts matter and which parts are noise. These are the skills that get more valuable as AI handles more of the mechanical work.

The person who can think clearly about what a website should communicate will be more valuable than the person who can write the code to make it load in under two seconds. Because the second skill is increasingly commoditised. The first one is not.

The question worth sitting with

So here is what I have been thinking about since this weekend.

If the future of work looks less like “apply for jobs and climb ladders” and more like “develop a skill, build a reputation, offer value directly,” then most of us are not prepared for it.

We have been trained for a world of jobs. Resumes, interviews, performance reviews, promotions. That entire infrastructure assumes a specific model of work, one where you are a component in someone else’s machine.

The alternative is not easy. Being a specialist, being self-employed, being the person who is known for what they can do, that requires a different set of skills entirely. You have to learn to find your own problems to solve. You have to learn to communicate your value without a job title doing it for you. You have to learn to build in public, to let people see your work before it is polished.

I am not saying everyone should quit their job tomorrow. I have a job. I like my job. But I am building something on the side because I think the smartest thing you can do right now is develop the ability to create value independently of any single employer.

Not because jobs are going away overnight. But because the skills that make you good at independent work, clear thinking, self-direction, the ability to learn and build quickly, those are the same skills that make you valuable everywhere. In a job or outside of one.

The weekend, in retrospect

I started Saturday morning wanting to build a website. By Sunday night, I had a website and a completely reorganised mental model of where work is heading.

All because I sat down and tried to make something.

The website is not perfect. Some of the spacing is off. There is a mobile view issue I have not fixed yet. The content sections are placeholders waiting for real essays.

But it is live. It exists. I made it.

And the fact that I could make it, with no formal training, in two days, using tools that did not exist three years ago, that tells me more about the future of work than any think-piece or trend report ever could.

The future is not about what you know how to do. It is about what you are willing to figure out.

I figured out a website this weekend. I am going to keep figuring things out. Publicly, imperfectly, and on my own terms.

---

I write about clear thinking, AI-enabled work, and building in public. If this resonated, you will probably like what comes next.